How to Check Your QuickBooks Desktop Company File Size with F2

Last reviewed 2026-07-08 4 min read

QuickBooks Desktop running slow? Learn how to check your company file size using the F2 Product Information screen and what that number means for performance.

A company file that has grown large enough can turn QuickBooks Desktop sluggish — forms take longer to open, reports crawl, and the Verify routine starts to feel like a coffee break. The first number our engineers ask for in any performance investigation is the company file size, and the fastest way to find it is the Product Information screen built into QuickBooks itself.

Opening the Product Information Screen

With your company file open in QuickBooks Desktop, press the F2 key on your keyboard. On most keyboards that is the single key, not a combination. If you are on a laptop or a compact keyboard where F2 is tied to a system function (brightness, volume), hold the Fn key as well — for example, Fn + F2.

A window titled Product Information appears. It is a read-only summary — nothing here changes your data. The screen lists your QuickBooks edition and version, license number, and several file-level statistics.

Locating the File Size

In the File Information block — usually the upper-left quadrant of the window — you will see three fields:

File Size — displayed in either megabytes (MB) or gigabytes (GB), depending on how large the file is.
Location — the full folder path where the .qbw file lives on disk.
Transactions — the total transaction count stored in the file.

Write down or screenshot the File Size value. If you are reporting a performance issue or planning a condense, the exact number matters more than a rough estimate. While you are here, note the transaction count as well — a file with a high transaction count but a modest file size can still be slow if list entries have ballooned.

What the Number Means

General thresholds our engineers use when assessing QuickBooks Desktop performance:

Under 500 MB — file size is unlikely to be the cause of slowness. Look elsewhere: network speed, the workstation's available memory, or a damaged transaction triggering repeated rebuilds.
500 MB to 1 GB — you are entering the range where file size starts to matter. List-based screens (Customer Center, Vendor Center, Item List) may lag, and multi-user mode can feel noticeably slower.
Over 1 GB — the file is large enough that routine operations — saving invoices, running profit-and-loss reports, switching between company files — will be measurably slower than they were when the file was smaller.
Over 1.5 GB — QuickBooks Desktop is operating near the edge of what the database engine handles gracefully. Unexpected crashes, lock-ups during Verify/Rebuild, and failed backups become more common at this size.

These thresholds are guidelines, not hard limits. A 900 MB file on a fast workstation with an SSD can still feel acceptable; the same file on an older machine over a network share can be painful.

When to Consider Condensing

If the file size is over 1 GB and performance is degrading, condensing is worth evaluating. QuickBooks has a built-in Condense Data utility, but it has limitations — it removes transactions only up to a cutoff date you choose, and it does not always shrink the file as much as expected.

A more aggressive option is a SuperCondense service, which can target inactive items — parts, assemblies, and groups — along with transactions before a cutoff date. List entries such as accounts, customers, vendors, classes, and other names are preserved by default and can optionally be cleaned up if they carry no remaining activity.

If you are also planning a move to QuickBooks Online, file size matters even more: the target for a smooth import is under 1 GB, with 500 MB being ideal. Condensing before migration is often the difference between a clean import and a failed one.

Before You Act on the Number

One reading is a data point, not a diagnosis. If you have not already, run Verify Data (File → Utilities → Verify Data) to rule out structural damage as the cause of slowness. A file that is merely large behaves slowly but predictably; a file with internal damage behaves erratically — and no amount of condensing will fix that. Where damage is present, our engineers recommend addressing file repair before condensing, since condensing a damaged file can compound the problem.