# Bank Upload Stuck in QuickBooks Online? Try This - Author: SimpleBankConvert (https://simplebankconvert.com) - Published: 2026-10-17 - Category: Import errors - Canonical: https://simplebankconvert.com/blog/bank-upload-stuck-in-quickbooks-online > What to do when a bank upload is stuck in QuickBooks Online: browser and file size checks, a cleared cache and splitting the upload into smaller files. A bank upload stuck in QuickBooks Online is usually waiting on one of three things: a bank feed update already running, a browser that has lost the session, or a file over the 350 KB and 1,000-line limits. Wait a few minutes, retry in a private window, and split any large file into smaller dated files. ## What a bank upload stuck in QuickBooks Online is telling you A stuck upload has usually already failed, even if the screen still shows a spinner. Intuit's article on [fixing bank upload errors in QuickBooks Online](https://quickbooks.intuit.com/learn-support/en-us/help-article/bank-transactions/fix-bank-upload-errors-quickbooks-online/L6FBh3zDC_US_en_US) says one of its messages means the upload timed out. That message reads "We were unable to upload the file. Please start over and re-select the file you want to upload." If you see it, the upload is over and nothing more will happen on that screen. If you see only a spinner after several minutes, treat it the same way. Leaving the tab open overnight will not finish it. ### Which kind of stuck are you looking at? Note where it stopped, because each stopping point hints at a different cause: - **Stuck after choosing the file**, before the account screen: usually the browser or the file size. - **Stuck on the mapping screen** for a CSV: often a file whose columns QuickBooks cannot read, such as a spreadsheet saved under a .csv name. - **Stuck after the final confirm**: often a server-side pause or a feed update running at the same time. - **Stuck with a message**: read it, because it names the cause. Intuit's article lists them, and the guide to the [QuickBooks Online bank upload error](/blog/quickbooks-online-bank-upload-error) sorts them by cause. ### The order of checks Work through the fixes in this order. Each one costs less than the next: 1. Wait five minutes and try once more with the same file. 2. Check whether a bank feed update is running. 3. Try a private window, then a different browser. 4. Check the file size and line count. 5. Split the file into smaller dated files. The sections below take each step in turn. ## Is a bank feed update holding up the QuickBooks Online upload? QuickBooks Online runs a daily download from connected banks, and an upload that collides with it can hang. Intuit's upload error article lists the message "An Online Banking update is currently in progress" and says to wait until the update finishes. The same article describes a temporary server problem that clears after a few minutes. You will not always see the in-progress message. If any account in the company is connected to a bank feed, look at the Bank transactions page. An account tile that shows it is updating means the download is still running. Wait for it, then start the upload again from the Upload from file button. Do not press Update yourself just before an upload. That starts the same download you are trying to avoid. If a connected account shows its own error, such as a script error on the feed, fix that separately. The post on [QuickBooks error 9999](/blog/quickbooks-error-9999) covers that feed fault, which is a different problem from a stuck upload. ## Browser fixes for a stalled QuickBooks Online file upload The browser is the first thing to check when the upload freezes right after you pick the file. QuickBooks Online runs entirely in the browser, so a stale session, an extension that blocks pop-ups or scripts, or cached files from an older version of the page can stop the upload without an error message. Try these in order, testing the upload after each one: 1. **Sign out and back in.** A session that expired while you were preparing the file can leave the upload button looking live while nothing is sent. 2. **Open a private window.** In Chrome it is an Incognito window, in Firefox a Private Window, in Safari a Private Window, and in Edge an InPrivate window. A private window starts without your saved site data and, by default, without most extensions. If the upload works there, the cause is something stored in your normal browser. 3. **Clear the cache for QuickBooks.** If the private window worked, clear cached images and files in your normal browser's settings, then sign in again. 4. **Turn off extensions one at a time.** Ad blockers, password managers and privacy tools are the usual suspects. 5. **Try a different browser.** This rules out a problem with the browser version itself. Keep one tab of QuickBooks open while uploading. Two tabs in the same company can each hold a different session, and an action in one can quietly break the other. ## Does the file size freeze the QuickBooks Online bank upload? Size is a real limit, not a guideline. Intuit's guide to [manually uploading transactions into QuickBooks Online](https://quickbooks.intuit.com/learn-support/en-us/help-article/import-transactions/manually-upload-transactions-quickbooks-online/L0rE9OXBz_US_en_US) says the upload file must be 350 KB or less, with up to 1,000 lines per upload. A file over either limit can fail or hang rather than finish. ### How to check both limits For size, look at the file's properties: right-click and choose Properties on Windows, or Get Info on a Mac. For lines, open a CSV in a spreadsheet and look at the last row number, minus the header. A QBO file is harder to count by eye. Open it in a text editor and search for the tag that starts each transaction, which in most files is ``, and count the matches. ### Why bank files grow past the limit Three things push a file over: - **A long date range.** A year of a busy account can pass 1,000 lines easily. - **Long descriptions.** Each line carries the bank's full text, and some banks write a lot. - **Extra columns.** A running balance, a reference number or an empty column adds bytes to every row of a CSV. The CSV rules also apply to card accounts, with one more trap: the sign of charges. The guide to a [credit card upload error in QuickBooks Online](/blog/credit-card-upload-error-in-quickbooks-online) covers card files. ## Splitting a stuck bank upload into smaller files Splitting is the fix for a file over either limit. Cut the file by date, not by line count, so each part covers a clean range with no gaps or overlaps. Each part should stay well under both limits. Then upload the parts oldest first, checking each one before the next. ### A worked example Here is an example. The business, counts and ranges are made up. A year of an example checking account has 1,450 lines and the CSV is 410 KB, over both limits. | Part | Date range | Lines | Approx. size | | --- | --- | --- | --- | | 1 | Jan 1 to Apr 30 | 470 | 135 KB | | 2 | May 1 to Aug 31 | 495 | 140 KB | | 3 | Sep 1 to Dec 31 | 485 | 135 KB | Each part sits under 500 lines and 150 KB, which leaves room for a header and long descriptions. ### How to split a CSV 1. Open the CSV in a spreadsheet and sort by date, oldest first. 2. Save a copy for each part. 3. In each copy, keep the header row and delete every row outside that part's range. 4. Save each copy as CSV, with the range in the name, such as `checking-2026-01-01-to-2026-04-30.csv`. 5. Count the rows across all parts. They must add up to the original count. For a QBO file, splitting by hand is fiddly, because the header holds a start date, an end date and a closing balance that must match the transactions inside. It is usually easier to download shorter ranges from the bank, or to rebuild the file from the statement for each period. SimpleBankConvert is being built to turn a PDF statement into a CSV or QBO file for QuickBooks Online, one statement at a time. Accounts are not open yet, and the [get started page](/get-started) takes your email. ## Retrying a stuck upload without doubling transactions A frozen upload sometimes lets part of the file through before it stalls. Upload the whole file again and those lines arrive twice. So before any retry, open the For review tab for the account and check whether anything from the file is already sitting there. Look for three things: - **Lines dated inside the file's range** that were not there before the upload. - **The newest date** among those lines. This is where the partial upload stopped. - **The bank's original text** on a sample line. The Bank Detail field keeps the original description text, so you can compare a line with the matching row in your file. The post on [Bank Detail in QuickBooks Online](/blog/bank-detail-in-quickbooks-online) explains what that field holds. If part of the file went in, cut the file so it starts the day after the newest date that arrived, and upload only the rest. If you are not sure whether a whole day made it, include that day and exclude any duplicates in the For review tab before you add or match anything. If nothing from the file is there, the upload failed cleanly. Retry with the same file after the earlier checks, or with the split parts. The one mistake to avoid is accepting lines from a half-finished upload in bulk. Once added, a duplicate becomes a real transaction in the register, and removing it means finding and deleting each one later.