Quick answer
Is your QuickBooks company file too large, or just slower than it used to be? Large files do slow opening, reports, backups, and multi-user work, but size alone is rarely the whole story. Check the real numbers first: press F2 (or Ctrl + 1) for file size, total targets, and DB file fragments. Condensing is irreversible, so measure and back up before you archive anything.
How to check your QuickBooks company file size and target count
QuickBooks reports everything you need in one window. Open the company file, press F2 or Ctrl + 1, and read the File Information section of the Product Information window:
- File Size — the physical size of the
.QBWfile in megabytes. - Total Targets — the number of records QuickBooks tracks, which is the number that matters for import limits and database work.
- DB File Fragments — how many pieces of the file Windows has scattered across the drive. More than 100 usually affects performance.
- List Information — counts for customers, vendors, items, accounts, and other lists, so you can see how close you are to a list limit.
Size and target count are different measures. Intuit's migration guidance uses targets: a file with more than 750,000 targets can take noticeably longer to process, and QuickBooks Online import stops at 4,000,000 targets. On Windows, Pro and Premier cap total names and items at 14,500 each, so list growth can force decisions before size becomes a problem.
| List | QuickBooks Desktop Pro, Premier | QuickBooks Desktop Enterprise |
|---|---|---|
| Chart of Accounts | 10,000 | 100,000 |
| Names (employees, customers, vendors, other names combined) | 14,500 | 100,000+ |
| Items, including inventory items | 14,500 | 1,000,000+ in newer versions |
What file size does to performance, in realistic ranges
Intuit states there is no hard size limit, but performance decreases as the file grows, and a network that cannot handle a large file becomes the bottleneck. The bands below are practical support guidance, not an Intuit specification, and assume a healthy file on a local SSD.
| File size (practical guidance) | What users typically notice | What to do |
|---|---|---|
| Under 100 MB | Opens and reports quickly; nothing points to file size | Keep up normal maintenance |
| 100–500 MB | Fine for most single-user and small multi-user setups | Verify and rebuild twice a year |
| 500 MB–1 GB | Rebuilds and backups take several minutes; checkouts slow with multiple users | Maintenance plus list cleanup; review the transaction log and fragments |
| 1–2 GB | Slow opens, slow large reports, long backups, frequent complaints in multi-user mode | Plan a condense and archive review with your accountant |
| Over 2 GB | Multi-user work lags even on a wired network; verify and rebuild can run a long time | Condense or split history, check hardware, and consider Enterprise or a consultant |
Two files of the same size can perform very differently. A 1 GB file with 400 DB fragments on a server with 2 GB of RAM feels much worse than the same file on a modern SSD with adequate memory. Fix the environment before blaming the file.
When size is actually the problem
These signals point at the file rather than the network or the computer:
- DB file fragments above 100. Windows has scattered the file across many locations, so QuickBooks reads multiple blocks for one record.
- A large, growing transaction log. The
.TLGfile records changes since the last full backup. A manual backup with full verification resets it, which alone can restore responsiveness. - Thousands of zero-value detail lines. Lines with zero price and quantity slow reports and can distort cash basis reports with inventory.
- A bloated search index. The
.qbw.SearchIndexfile grows with the file and drags automatic search behind it. - List counts pressing the published limits. Approaching 14,500 names or items on Pro or Premier slows lookups and eventually blocks new entries.
- Slow performance even on a fast local machine. If a local copy of the company file runs quickly, the network, NAS, or server is the bottleneck, not the file's size.
Before you condense or archive: protect the books
Condensing cannot be undone. The Condense Data utility removes transaction detail from the live file and replaces it with monthly summary entries. Reports change as a result: cash basis reports for the condensed period, item-based reports, class-based reports, and sales tax liability reports will no longer match the originals. Make a full backup, copy the entire company-file folder, and get your accountant's agreement on the cutoff date before you begin.
Plan on 30 to 90 minutes, plus backup time, in single-user mode when nobody needs the file. Intuit's guidance is to reconcile all accounts first and save the reconciliation and discrepancy reports as PDFs, because the underlying checks and deposits no longer exist in detail after condensing.
How to reduce a large QuickBooks company file
Record a baseline from the F2 window
Write down the current file size, total targets, DB file fragments, and list counts, then time the file open and your heaviest report. Without a baseline you cannot prove whether cleanup helped.
Create a full backup and a folder copy
Switch to single-user mode, then go to File → Back up Company → Create Local Backup and save the .QBB file to an external drive or another computer. Then copy the whole company-file folder — .QBW, .ND, .TLG, and .DSN together — to a second location.
That backup is also your permanent archive. Intuit describes the pre-condense local backup as the unedited historical record, so label it with the date and store it somewhere safe.
Reconcile accounts, then clean up lists
Reconcile every bank and credit card account and save the reports. Then remove unused list entries. QuickBooks will not delete an entry used in a transaction, so make those inactive instead. Merge duplicates, clear old memorized transactions and To-Do notes, and use Add/Edit Multiple List Entries for bulk work instead of deleting records one at a time.
Run Verify and Rebuild, then reset the transaction log
Go to File → Utilities → Verify Data. If QuickBooks reports lost integrity, run Rebuild Data and verify again — two or three rebuilds in a row is normal. Then create a manual backup with full verification; that backup resets the transaction log and clears a common cause of creeping slowness.
If F2 shows more than 100 DB fragments and the file is on a traditional hard drive, defragment the drive. Never defragment a solid-state drive.
Rebuild a bloated search index
Go to Edit → Preferences → Search → Company Preferences and clear Update Automatically. Rename the company.qbw.SearchIndex file in the company-file folder, reopen QuickBooks, and let it rebuild the index. Turn automatic updates back on if search speed was acceptable before.
Condense old transactions with an accountant-approved cutoff
In single-user mode, open File → Utilities → Condense Data. For a safe first pass, choose Keep all transactions, but remove audit trail info to date. To shrink the file, choose Remove the transactions you select from your company file, pick the date range, review list entries QuickBooks offers to remove, then select Begin Condense. QuickBooks saves an archived copy before removing anything.
Expect limits: open transactions and entries linked across the cutoff date are not condensed, and the utility will not run if it detects no significant size change. With inventory, set the cutoff to the last day of a monthly reporting period to keep average cost accurate.
Archiving old data without losing history
Condensing does not delete history; it moves detail out of the live file and replaces it with monthly summaries. The detailed record is the backup you made first, so keep that pre-condense .QBB on two drives, labeled by fiscal year, where your accountant can pull prior-period detail.
A workable rhythm for most small businesses is to keep three to five years of detail live and condense anything older, keeping the summary entries for balances. Your accountant sets the exact cutoff based on tax, audit, and lending requirements.
If you plan to move to QuickBooks Online, condense first. An import fails above 4,000,000 targets, and files over 750,000 targets process slowly and can produce data discrepancies, especially with inventory.
What not to delete manually
- Never delete the
.QBWor its support files to save space. The.TLGis needed for recovery, the.NDis a 1 KB configuration file, and the rest are rebuilt only through QuickBooks. - Never delete transactions or list entries with history to shrink the file. Balances, reports, and the audit trail break, and the damage may not surface until reconciliation.
- Never run condense as a repair. If Verify Data reports damage, fix the file first or the condense can fail partway.
- Never defragment an SSD and never compress or encrypt the company-file folder through Windows properties.
- Never restore an old backup as a size fix. You lose every transaction entered since, and condensing is the controlled alternative.
Verify the improvement
- Open the company file and press F2. Compare size, total targets, list counts, and DB fragments against your baseline, and re-time the open and heavy report.
- Run File → Utilities → Verify Data and confirm QuickBooks reports no problems.
- Create a fresh backup after the maintenance and store it off the machine.
- Ask your accountant to confirm the trial balance and a prior-period reconciliation report still match expectations.
If QuickBooks is still slow after cleanup
The file may not be the cause. Intuit's memory guideline multiplies file size in gigabytes by the number of users: a 500 MB file with six users calls for roughly 3 GB of RAM on the server. Store the file on a wired disk rather than Wi-Fi or a NAS device, and confirm only one computer hosts multi-user access.
If lists are pressing the published limits, cleanup will not add headroom on Pro or Premier — that is an Enterprise capacity decision. If the file also shows lock errors or failed opens, work through data damage checks before condensing, and if rebuilds fail, company-file repair is the safer next step. For a full triage, start with the slow performance checklist and keep a current backup routine in place.
Frequently asked questions
How big is too big for a QuickBooks company file?
Intuit sets no hard size limit, so no official number means "too big." In practice, complaints become common above roughly 1 GB, and multi-user setups feel size sooner. Measure file size, targets, fragments, and hardware together before blaming the file.
Does condensing delete my transactions?
It replaces transaction detail with monthly summary entries. Balances stay correct, but the individual checks, invoices, and bills for the condensed period leave the file. The backup QuickBooks creates first is your detailed archive, and condensing cannot be reversed.
Can I just delete old transactions instead of condensing?
No. Manually deleting transactions breaks account balances, the audit trail, and report accuracy. Condense Data summarizes entries in a controlled way and preserves balances.
Will condensing fix slow QuickBooks performance?
Only if file size is the cause. Check DB fragments, the transaction log, RAM, drive type, and the network first. If a local copy runs quickly, condensing will not help.
Does a large file cause data damage or error 6000?
Size itself does not damage a file. Larger files do take longer to verify, back up, and rebuild, which stretches the window in which a power loss or dropped connection can interrupt maintenance. Keep backups current and run Verify Data regularly regardless of size.