QuickBooks CSV Import Limit: The 350 KB and 1,000 Row Caps Explained
No account needed for your first conversions. We never store your bank login.
Short answer: QuickBooks Online limits every manual bank upload to a file of 350 KB or less, and a CSV can carry at most 1,000 rows (one transaction per row). The file must be in English, use one consistent date format, and be arranged as either 3 columns (Date, Description, Amount) or 4 columns (Date, Description, Credit, Debit). Bigger dataset? Split the export into smaller date ranges and upload each piece, or convert the file and let the bank feed's duplicate detection guard the seams. QuickBooks Desktop is stricter still: it has no CSV import at all for bank data, only .qbo Web Connect files.
Last updated July 2026. These limits are easy to hit the moment you do anything beyond routine monthly bookkeeping: a year of catch-up, a busy e-commerce checking account, or a migration from another accounting system will blow past 1,000 rows without trying.
What are the QuickBooks Online CSV import limits?
| Limit | The rule | What happens if you exceed it | The fix |
|---|---|---|---|
| File size | 350 KB maximum per upload | QuickBooks rejects the file outright | Export a shorter date range, or strip unneeded columns to shrink the file |
| Row count | 1,000 rows maximum per CSV | Upload fails or truncates at the cap | Split into files of under 1,000 transactions each |
| Columns | 3 columns (Date, Description, Amount) or 4 (Date, Description, Credit, Debit) | Mapping errors or a rejected file | Delete extra columns (balance, category, reference) before uploading |
| Language and dates | English text, one consistent date format | Rows silently misread or rejected | Normalize the date column before upload |
How many transactions can I import into QuickBooks Online at once?
Practically, plan on 1,000 per upload, because the row cap almost always binds before the size cap does. A plain 3-column bank CSV runs roughly 40 to 60 bytes per row, so a 1,000-row file weighs in around 50 KB, nowhere near 350 KB. The size cap only becomes the binding constraint when the export carries long memo fields or a pile of extra columns, which is one more reason to trim the file down to the columns QuickBooks actually reads.
How do I import more than 1,000 transactions?
Split the export by date range and upload the pieces in order. Monthly slices are the natural cut for most accounts; a very busy account might need weekly. Three rules keep the seams clean. Keep the header row in every file, since the uploader maps columns per file. Do not overlap the ranges; if the same transaction appears in two files, QuickBooks' CSV upload will happily import it twice, because CSV rows carry no unique transaction IDs for the duplicate checker to work with. And import chronologically, which keeps running balances sensible when you review. Our guide to importing multiple CSV files into QuickBooks walks the batch workflow end to end.
Does converting to a QBO file get around the limit?
Partly, and it fixes a nastier problem at the same time. Honest answer first: QuickBooks Online's uploader applies the same 350 KB size cap to .qbo, .qfx and .ofx files, and OFX markup is more verbose per transaction than CSV, so a converted file does not smuggle unlimited rows into QuickBooks Online. What conversion does change is duplicate safety: a .qbo file assigns each transaction a unique FITID, which is what QuickBooks' duplicate detection actually keys on. Split a dataset into .qbo files and an accidental overlap gets caught at import instead of becoming a cleanup job. On QuickBooks Desktop the calculus is simpler, because .qbo is the only format the bank feed accepts at all, and large multi-month Web Connect imports are routine there. For a big backfill, converting each slice at the bulk CSV to QBO converter is the workflow built for exactly this.
Why does QuickBooks have these limits?
The upload pipeline validates, parses and stages every row interactively before anything posts, and Intuit sized the caps to keep that review screen responsive rather than to accommodate migrations. The limits date back years and have survived every interface redesign, so the safe assumption is that they are permanent. Build your workflow around them instead of waiting for them to lift.
Common errors when a file is near the limit
Three failure modes cluster around big files. A hard rejection at upload usually means the 350 KB cap, so shorten the range. An upload that seems to succeed but shows fewer transactions than the file contains usually means the row cap truncated it, so count your rows before assuming QuickBooks lost data. And a file that fails with a vague formatting complaint usually has a mixed date format or stray columns, which our QuickBooks CSV import template guide diagnoses error by error, including exactly how to arrange the 3-column and 4-column layouts.
Catch-up bookkeeping: a year of transactions in one sitting
The limits sting most during catch-up work, when a shoebox client or a long-neglected company file needs twelve months of bank activity imported before anyone can reconcile or file the year's taxes. The month-by-month rhythm is your friend here: export each statement period as its own file, convert or upload it, and reconcile that month before moving to the next. It feels slower than one giant import, but every seam lands on a statement boundary, which is exactly where you want to verify balances anyway. The full sequence, including where opening balances go wrong, is in our guide to importing older transactions into QuickBooks.
Does QuickBooks Desktop have a CSV import limit?
Desktop's limit is absolute: it does not import bank CSVs at all, in any version or year. Its bank feed accepts only .qbo Web Connect files, imported under Banking, Bank Feeds, Import Web Connect File. The upside is that Desktop handles large Web Connect files gracefully, so a converted multi-month .qbo usually goes in as one import rather than twelve. The route is covered start to finish in CSV to QuickBooks Desktop.
The bottom line: 350 KB and 1,000 rows per upload in QuickBooks Online, no CSV at all in Desktop. Split by statement month, never overlap ranges, and use .qbo files when you want duplicate detection watching the seams. The converter at the top of this page reads CSV, Excel and text exports and produces QuickBooks-ready files, three conversions free, no account required.