Your Access database has hit the 2 GB limit

Every figure below is quoted from Microsoft’s own specifications · checked 21 August 2026

This is not a bug, a corrupt file, or something your IT person can raise. It is a published property of the file format, and the number is smaller than the one people quote. Most of what you will find tells you to run Compact and Repair. That is worth doing and it is not an answer — it reclaims space you already own rather than giving you more.

Before you read further, the thing to know before you install. You run Access, so you are on Windows — and the Windows desktop app is a download now, offline and data-on-your-own-machine included. It is not code-signed yet: the first time you run it Windows shows a blue “Windows protected your PC” box, and you get past it with More info then Run anyway. Some antivirus flags it for the same reason. A certificate is bought, not written, and we would rather ship the app and say this plainly than keep you waiting. If clicking through that is a no for you or your IT policy, the browser app works on Windows with nothing to install — and the rest of this page is still true about hit the 2 GB ceiling, and every figure in it is quoted from Microsoft.

The number, and the part of it you do not get

Microsoft’s published Access specifications give the maximum size of an Access database as:

“2 gigabytes, minus the space needed for system objects.”

That trailing clause is the part worth reading twice. The ceiling is not 2 GB of your data. It is 2 GB of file, and Access’s own internal bookkeeping is inside it, so the amount of room you actually have for records is some unstated figure below the number everybody quotes. This is why databases start misbehaving before the file reaches 2,147,483,648 bytes rather than politely stopping at it.

Two other published ceilings from the same page matter once you start planning around this one:

• 255 concurrent users. A maximum, not a working figure — a shared database over a busy network gets unpleasant a long way below it.
• 255 fields in a table. The one people meet when they try to solve a size problem by widening a table instead of adding a related one.

Why Compact and Repair feels like the answer

When you delete records, Access does not immediately hand the space back — the file keeps the room. Compact and Repair returns it, which is why the file can drop dramatically and the problem appears to go away.

Nothing about the ceiling changed. You recovered space that was already yours, and you will recover a bit less each time as the genuinely-in-use portion grows. If compacting has gone from an annual chore to a monthly one, that trend is your actual warning, and it is more informative than the current file size.

Splitting buys you one more ceiling, not headroom

Splitting an Access database separates the data tables (the back end, on the share) from the forms, queries and reports (the front end, one copy per person). Microsoft recommends it for anything several people share, and if your database is not split you should split it regardless of size — we wrote about why an unsplit shared database keeps corrupting separately, and about the lock-file error splitting does not remove.

What it does for size is narrower than people hope. The limit is per file, so a split back end gets its own 2 GB and the front end is no longer competing for the same space. That is real, and it is one step, not a new tier. A back end that grew to 2 GB will grow to 2 GB again.

The same arithmetic is why “move the attachments and images out” works so well when it works: binary files consume the ceiling far faster than rows do, and a database that is mostly scanned documents is not really a 2 GB database problem, it is a file-storage problem living in the wrong place.

What actually removes the ceiling

Only one category of answer changes the limit rather than postponing it: putting the data somewhere that does not have it.

1. Keep Access, move the tables. Point the Access front end at SQL Server (the Express edition is free) so the forms, reports and VBA you have trained people on stay exactly as they are, and the size ceiling goes away with the .accdb back end. If your database is a real application — years of VBA, reports the business depends on — this is usually the right answer and you should not let anyone talk you out of it.
2. Leave Access. Reasonable when what you have is not really an Access application: some tables, a few forms, and people who each need to update their own records, increasingly from places that are not the office. That case is on a file share because that is where Access put it, not because a shared file was ever the right home for it.
3. Archive. Move closed years into a separate database. Genuinely useful, and it is the same move as compacting on a longer timescale: it resets the clock rather than removing the clock.

What Microsoft does not publish here

Worth stating plainly, because pages like this one tend to fill gaps with confident guesses. The specifications page does not give a maximum number of tables in a database. It lists a figure for open tables, which is a different thing — a runtime limit on how many can be in use at once, not a cap on how many can exist. If you have read a specific “maximum tables” number somewhere, it did not come from that page, and we are not going to repeat it as though it did.

Why we wrote this

We build Bionic Forms and we would like Access owners in the second case above to consider it, so this is not neutral. What we offer instead of neutrality is that every figure here is Microsoft’s own published specification rather than our characterisation, and that we will say where we do not fit.

Where we help: there is no single file to outgrow. Records live in a real database with per-person permissions and their own revision history, so the questions that follow a 2 GB scare — who changed this, what did it say before, can this person see it — have answers. Files attach to records without eating a shared ceiling. People outside your organisation can fill in a form without an account.

Our own limits, since that is what this page is about: we do have them, and they are published numbers rather than a file format running out of room. On the free plan each app holds up to 10,000 entries, you can have as many apps as you like, and your account has 10 GB for attached files. Business is $29 a month flat with unlimited users, and raises that to 1,000,000 entries per app and 250 GB. When an app is full it stops taking new entries and says so; everything already in it can still be opened, edited and deleted, and deleting frees the room again.

Where we do not: we do not run VBA, and we will not pretend a decade of Access macros ports across — if that logic is the product, moving is a rewrite and you should price it as one. SQL Server behind your existing front end is the better answer for that case and we will tell you so. We also do not read an .accdb directly: the route in is a CSV export, so relationships are rebuilt from the key columns you exported. Our loader does rebuild them, and refuses rather than guesses when a value is ambiguous, but it cannot recover a link you never exported.

Sourcing, plainly: the size, concurrent-user and field figures are quoted from Microsoft’s Access specifications, checked on 21 August 2026. The description of how deleted space is reclaimed, and of binary files consuming the ceiling faster than rows, is ordinary file behaviour rather than a quotation, and we say so rather than dressing it up as a citation.

Being straight about where we are: Bionic Forms is pre-launch. There is no iOS or Android app; the macOS, Windows and Linux desktop builds and the web app are what exist today, and the Windows build is not code-signed yet, so Windows warns the first time you run it, and we have no external customers to point at.