Access recovery you can check

Don’t pay blind.

See exactly what your Access database can recover — and how many rows it couldn’t — before you pay.

Corrupted .mdb or .accdb? Drop the file in. The engine runs in your browser and reads it there: table by table, the count the database itself declares, how many rows came back, and how many it couldn’t read. Nothing is uploaded, so there’s nothing you have to take on trust.

Check My Database — FreeSee a sample report

Free to check. No signup, and nothing to install — not even Access.

Example readout — your own file generates its own numbers.

MDB & ACCDB
Runs in your browser
Row counts before you pay
No subscription
The problem

Your database won’t open.

First, find out what’s actually wrong.

Most recovery tools ask you to trust them before you know what you’ll get. Access Rescue does the opposite.

  1. 01

    First, we inspect your database.

    Locally, in your browser.

  2. 02

    Then we show you the evidence.

    Per table, with real row counts.

  3. 03

    Only pay when you know the data is worth recovering.

    Nothing to unlock until you’ve seen it.

Page chain

Power loss or a forced shutdown

A write was interrupted partway through. Access usually reports an unrecognized database format even though most of the pages are still intact.

Index vs. table data

Several people sharing one file

A network hiccup during a concurrent write leaves indexes pointing at rows that have moved. The file opens but the numbers don’t add up.

Allocation map

A file pushing against the 2 GB limit

Access caps a single database at 2 GB. Writes that pass the cap fail, and the failure can spread into pages that were already on disk.

Readable page count

Bad sectors or a failing disk

Whole pages come back unreadable. What survives depends on how far the physical damage reached — which is exactly why you measure before you commit.

Recovery evidence

What came back, and what didn’t.

  • We don’t hide missing rows behind a better-looking percentage.
  • If part of your database could not be reached, we’ll show you.
  • When there’s no count to check against, we say so — we don’t fill the gap with a guess.

Counts from your file, not a recovery rate.

Select tables3 of 4 readable
  • Orders0 / 0recovered
  • Customers0 / 0recovered
  • Products0 / 0recovered
  • Old_ArchiveUnable to verify

Illustrative example — your own file produces these figures.

Table-level recovery

You don’t always need the whole database.

Need one table? Select the table that actually matters.

Every table is reported on its own, with the rows we recovered next to the rows the database said it had. If a table can’t be verified, it says so instead of quietly averaging into everything else.

Recover what matters. Not everything.

Local privacy

Your database stays on your device.

Your Access file is processed locally in your browser. It isn’t uploaded to our servers for analysis.

That matters when your database contains:

  • customer information
  • financial records
  • internal business data
  • confidential operational records

Private by design.

Nothing is uploaded

The file is read into local memory. The page never sends it anywhere.

No copy is kept

There’s no account and no server-side file. Close the tab and it’s gone.

Works offline

The tool loads the engine into your browser and runs it on this device. Once it reports ready, you can turn off your Wi-Fi — the scan and the exports still work.

The one exception — expert reviewYou send it, I never pull it

Your database never leaves your computer. If you want my review, you send me a report — 200 KB of page structure and error codes, with no values and no names in it.

  • No data values
  • No file hash
  • No table names
  • ≈200 KB
Pricing

Check it free. Unlock it for $29. Or hand me the report.

Three ways to use it, in the order people usually need them. Each one stands on its own — nothing here forces an upgrade.

Free — information$29 — the result$299 — a person
Step 1By the engine

Inspect

$0free

Find out what’s still in there.

Drop in your MDB or ACCDB. The engine reads it on your machine and shows you the row counts before any money changes hands.

  • Object inventory and Jet/ACE version
  • Per-table page health
  • Row counts per table: declared, read back, unreadable
  • 10 real rows you can check yourself
  • Corruption signature summary

A healthy database can be exported right here — SQLite, CSV, JSON or SQL, no volume cap.

Nothing to pay and nothing to sign up for — use the drop zone at the top of this page.

Step 2By the engine

Rescue

$29one-time

Take the readable data with you.

Once you’ve seen what’s there, unlock the export. Everything is written into new files — we build a new Access database from what could be read, and your original is never touched.

  • A new .mdb, written from what could be read
  • SQLite, CSV, JSON and SQL exports
  • Recovery report and corruption log
  • Schema and inventory

If the engine can’t produce usable data, you get your money back.

Unlock the export — $29
Step 3Me

Expert Review

$299one-time

Have me read your report.

A second opinion on your database, from the person who built the engine.

  • A technical report generated in your browser — no values, no file name, no table names
  • You email that report to me. You never send the database
  • Within one business day (Mon–Fri, GMT+8): my verdict on what’s wrong and whether it can be saved
  • If it can: a repair profile written for your database — I write it, you run it
  • If it can’t: I refund you in full, the same day
  • Includes everything in the $29 rescue

Your database never leaves your computer. If you want my review, you send me a report — 200 KB of page structure and error codes, with no values and no names in it.

Email me about a review

admin@mdbrescue.com · attach the report, not the database

No subscriptionOne-time per databaseRefunded if it can’t be done

Already bought the $29 rescue? I’ll credit it toward Expert Review — just reply to your receipt.

Rescue package

Your rescue package includes

$29 once, per database. Everything below is yours to download — and it stays on your machine.

A new .mdb

Your readable rows, written into a new Access database file. Your original is never modified.

Data files

The same recovered data as SQLite, CSV, JSON and SQL.

Schema

Keep the table structure with the data you recovered.

Recovery report

What was recovered, what was unreadable, and what could not be reached.

Corruption log

Where the damage sits, page by page, in a file you can read or hand to someone else.

Inventory

Understand what’s inside your legacy database — objects, tables, counts.

Everything we produce is written to new files. We export into a new Access database — we don’t repair your original in place, and the report lists anything that couldn’t be carried over.

Honest recovery

Sometimes the answer is bad. We’ll still tell you.

A badly damaged database may not come back whole. So the report keeps four things apart:

Recovered

Rows we could read back, against the count the database declares.

Unreadable

Data we encountered but could not safely parse.

Not reached

Data that was never reached because the database structure was damaged.

Unknown

When a table’s definition page can’t be read, so there’s no count to check against.

We’d rather give you an honest bad result than a misleading good one.

We can count the rows we read back, and the rows we couldn’t.

We can’t promise every value inside a recovered row survived unchanged.

Some damage leaves no trace we can detect.

So we show you real rows to check — before you pay.

Legacy databases

Old Access database? Start here.

Don’t know what’s inside an old Access database anymore?

Access Rescue gives you a local, read-only view of your database structure, version, tables, queries, VBA modules, and potential risks.

Understand what you have before you decide what to do next.

What the free check reports
  • structure
  • version
  • tables
  • queries
  • VBA modules
  • potential risks
Risks found (2)Reported free, not fixed
  • Access 2016 support ended 2025-10
  • 3 broken indexes

Illustrative example. The free check reports risks; it doesn’t fix them.

Use cases

This usually starts one of four ways.

Whichever one brought you here, the first move is the same: see what came back, then decide what it’s worth.

01

My Access database won’t open.

The check reads the file directly, so you see what’s still in it even when Access can’t open it.

02

I only need the data from one table.

Every table is reported on its own — see which one is worth paying for before you unlock anything.

03

I’ve already tried recovery software.

The report lists what was recovered, what couldn’t be read, and what was never reached. A partial result is never passed off as a complete one.

04

Nobody knows how this old database works anymore.

Inventory the objects, the version and the structure first — then decide whether to migrate, keep or retire it.

When the database matters, start with evidence.

Find out what can still be saved.

Don’t pay for a recovery tool before you know what’s in your file.

Free to check — your file never leaves your machine.

Rows you can count
How many the database declared, how many came back, how many were never reached.
Rows you can read
10 real rows from your own tables, on screen, before any payment.
An honest verdict
Including the answer nobody wants — sometimes the right move is to restore from a backup.

No account needed. Nothing to install.

FAQ

Questions people ask before they pay

Preview tools show you what they found. Most never show you a denominator — so you can't tell whether "recovered" means 100% or 5%. We report the row count your database claims for every table, then how many we actually got back, and then the rows we couldn't read. If a table's definition page is unreadable, we say there's no count to check against instead of leaving that table out.

No. The engine runs in your browser and the file is only read into local memory. The page never sends it to a server, and you can disconnect from the network once it has loaded.

Both .mdb and .accdb, from Access 95 through 2021 and Microsoft 365.

No — the engine is a WebAssembly build that runs in your browser, so it works on Windows, macOS and Linux with nothing else installed. That also sidesteps the usual catch: desktop recovery tools that will only save the result if Access is installed on the machine, and online services that want your file uploaded first. This is neither.

The recovery assessment: for every table, the rows the database declares, the rows we read back, the rows we hit but could not safely parse, and the rows we never reached — plus page health, the object list, and 10 real rows you can read before unlocking anything. None of those counts is an estimate; they are what the engine read out of your file. If the database turns out to be healthy, you can export it here as SQLite, CSV, JSON or SQL at no charge.

Files up to 300 MB run smoothly. Above that the check asks you to split or archive the file first, and 500 MB is the hard limit. Very few Access databases get near it.

No, and I don’t want it. Your browser generates a technical report — page structure, error codes, which pages couldn’t be read. It has no data values in it, no file hash, and not even your table names. That report is what I work from. Your database never leaves your computer: if you want my review, you send me a report, not the file.

The $29 rescue is the engine doing the work on your machine. Expert Review is me, reading your report and writing something specific to your database. If I can’t, you don’t pay.

Repairs at this level aren’t about names or values. They’re about which pages are reachable, what the allocation map says, how the text is encoded. I change the reading strategy and send that back as a small settings file. Your engine picks it up, on your machine.

Then you don’t pay. Not “contact us for a refund” — I issue it. Some databases are beyond reading, and the honest answer is usually “restore from a backup”. I’d rather tell you that on day one than sell you a week of hope.

Two different questions, so two answers. We can tell you how many rows we recovered, how many we couldn’t read, and how many we never reached — those numbers are measured. We can’t verify that every value inside a recovered row is unchanged; some damage leaves no trace to detect. That’s why we show you real rows before you pay — check them against what you remember.

Against files we didn't make, and didn't pick to look good: mydb_7, mydb_10 and mydb_11 — a third-party set of corrupted databases that anyone can download, with destroyed page headers and byte-rotated records. On those three, the engine recovers 99.2–99.4% of rows. Two limits matter. The count is against the repaired reference files that ship with the set, not a byte-for-byte copy of an original. And it describes those files, not yours. The readout above belongs to one sample database. Your own file reports its own numbers, in the free assessment, before you pay anything.

Then it says Unknown, and tells you why — usually that the table’s definition page couldn’t be read. It never silently falls back to 0% or 100%, and it never averages an unverifiable table into a number that looks better.

No. It’s a one-time payment for a single rescue package. Expert Review is one-time as well — there is no subscription anywhere in this product, and there won’t be.

No. Your original is opened read-only. Everything we produce is written to new files — including the new .mdb — so you can compare before you decide what to keep.