The QuickBooks Online upload limit: 1,000 transactions and 350 KB
You are catching up a year of bookkeeping, you have the whole statement in one file, and Upload from file will not take it. There is nothing wrong with your file. QuickBooks Online caps every manual upload at 1,000 transactions and 350 KB, and Intuit's advice is to go back to your bank and download the year again in shorter pieces. You do not have to.
🔒 Drop your statement into the converter — it splits anything over the limits into numbered files QuickBooks will accept, free, in your browser, never uploaded.
The two limits, in Intuit's own words
From Intuit's current help article on manually uploading transactions:
"Your upload file must be in English and 350 KB or less. We suggest a QuickBooks Online data (QBO) file. You can also upload (Quicken) QFX, or Comma-separated values (CSV) files."
"You can include up to 1,000 lines per upload. Each line contains one transaction."
"For larger uploads, shorten the date range and download transactions in smaller batches."
Three things worth pulling out of that:
- Both limits apply to the file, not to the account. There is no cap on how many uploads you do, so a year goes in perfectly well as several files, one after another.
- The limits do not depend on the format. A QBO, a QFX and a CSV are all judged the same way. Converting a CSV to QBO is a good idea for other reasons, but it does not buy you more rows.
- Intuit recommends a QBO file over a CSV for the upload. That is their wording, not ours.
Which limit do you actually hit first?
Nearly always the 1,000-line one. We measured it, rather than estimating, by writing real files from the same 1,000 transactions at different description lengths:
| Average description | 1,000 rows as QBO | 1,000 rows as QuickBooks CSV |
|---|---|---|
| 24 characters | 131 KB | 46 KB |
| 40 characters | 187 KB | 62 KB |
| 80 characters | 227 KB | 102 KB |
| 160 characters | 307 KB | 182 KB |
So a QBO costs roughly 130–310 bytes per transaction and a CSV roughly 45–180. At 1,000 rows a CSV is nowhere near 350 KB, and even a QBO only breaches it once descriptions average about 200 characters — the kind of thing you see on card statements that pack the merchant, city, country and a reference into one line. The practical reading: count your rows, not your kilobytes. And if a 900-row QBO is somehow refused for size, the same transactions as a QuickBooks CSV will be about a third as big.
The slow way, which is what Intuit tells you to do
Log back into your bank, set a shorter date range, download, upload, repeat. For a year of a current account that is twelve round trips, and some banks make you re-authenticate every time. It also leaves you guessing where to cut: pick a quarter with heavy card use and you will be back doing it again in halves.
The quick way: split the file you already have
Every transaction is already in the file on your disk. Nothing needs re-downloading — it needs cutting into pieces of the right size, and that is arithmetic.
- Drop your CSV, Excel file or PDF statement into the converter. It runs as JavaScript on your own machine; the statement is never uploaded.
- Pick your output format. If the result is over either limit, a note appears telling you how many files it will produce before you commit to anything.
- Convert. You get
transactions-1-of-3.qbo,transactions-2-of-3.qboand so on — each one inside both limits, split by date, oldest first. - Upload them one after another through Transactions → Bank transactions → Upload from file, in number order.
Each part is a complete, standalone file with its own date range in the header, not a fragment: QuickBooks reads part 3 exactly as happily as it reads part 1.
Will splitting duplicate anything?
No, and this is the part worth understanding, because it is also what protects you if you lose track of which parts you have already uploaded.
Every transaction in a QBO or OFX file carries a FITID, a unique identifier, and QuickBooks remembers the ones it has already imported. The parts are disjoint slices of one sorted list, and each row keeps exactly the id it would have had in a single unsplit file. So uploading the same part twice imports nothing the second time — QuickBooks recognises the ids and skips them. The one case where that protection gets in your way is when you want a second import after deleting a bad one, which needs its own trick: re-importing a Web Connect file QuickBooks has already seen.
A CSV carries no ids, so there QuickBooks has nothing to match on and a part uploaded twice will appear twice. Another reason to take Intuit's suggestion and use the QBO.
Does the same limit apply to QuickBooks Desktop?
Not as far as we can tell, and we are not going to invent a restriction. Intuit publishes the 1,000-line and 350 KB figures for the Online upload flow. Desktop's File → Utilities → Import → Web Connect Files is a different route and these numbers are not documented for it. If you are on Desktop, convert to QBO and import the whole statement; if it is refused, the cause is almost certainly the institution codes rather than the size.
Split my statement into uploads QuickBooks will take — free
Want to see it work before you use your own statement? Try the sample.
Sources
- Manually upload transactions into QuickBooks Online — Intuit, for the 350 KB limit, the 1,000-line limit, the accepted formats and the advice to download in smaller batches.
- Re-import Web Connect file issue — QuickBooks Community, on the unique identifier that makes a second upload of the same transactions a no-op.
- The file sizes in the table were produced by this site's own converter from 1,000 generated transactions, and you can reproduce them with any statement of your own.