QCFUM CSV Size and Row Limits

QCFUM applies two independent limits before a CSV import can run: a hard 2 MB input limit and an administrator-controlled maximum number of data rows. Both are enforced server-side.

The row limit can be configured from 1 through 5000. A new 2.0.4 installation defaults to 250 rows per import.

The 2 MB Limit

QCFUM defines the CSV byte ceiling as 2,097,152 bytes. It checks pasted CSV text, uploaded files, and the hidden Preview payload against that limit. Oversized input is refused before normal row processing continues.

The Administrator Row Limit

Settings → CSV Import & Approval Settings → Maximum rows per import accepts 1–5000. The parser counts data rows after the header and ignores blank lines. If the CSV contains more than the configured maximum, QCFUM rejects the import and asks the user to split the file or have an administrator raise the limit.

Why Both Limits Matter

LimitProtects against
2 MB byte capVery large uploaded/pasted payloads before complete processing.
Configured row capImports with more records than the site administrator intends staff to process at once.

Practical Import Strategy

  1. Start with the generated QCFUM sample.
  2. Keep the first production run small enough to review row-by-row.
  3. Preview and correct invalid/duplicate rows before committing.
  4. For large onboarding jobs, split the source into manageable files rather than immediately setting the row maximum to 5000.

Remember Other Gates

A file that is below both limits can still fail because of missing headers, forbidden password columns, invalid rows, disabled Direct/Invite modes, duplicates, unavailable Profiles/Packs, frontend ACL, or current entitlement.


Community Discussion

Want to compare Joomla user-onboarding workflows, share practical QCFUM tips, or discuss how other administrators use this feature? Visit the QC Frontend User Manager Community. For private support, bug reports, account-specific entitlement problems, or feature requests, use the QuantaCade support system.