IntactFile

Repair a corrupted PDF — without uploading it anywhere

Contracts, invoices, records. Most broken PDFs lost their index, not their pages, and an index can be rebuilt.

Your file never leaves your device — repair runs in your browser. 0 bytes uploaded.

Your data is the big block — usually intact. What breaks is the small index. Repair rebuilds it.

Drop a file here or browseTap to choose a file

ZIP · Office · PDF · video · JPG · PNG · RAR/7z · SQLite — repaired right here in your browser. Nothing is uploaded

0 bytes uploadedFree: 3 repairs/day — up to 500 MB video, 100 MB docs & archives, 50 MB photos. Free download. Single repair €5.90. No account required.

Short version: this tool repairs PDFs that won't open because their cross-reference table (the index) is damaged, missing, or truncated — it scans the file for the objects that survived and rebuilds the index around them. The whole repair runs in your browser, so 0 bytes of your document are uploaded — you can confirm that in the Network tab. Honest limit: pages whose object data was actually overwritten can't come back, because that content no longer exists in the file.

PDF won't open? Repair it now

  1. Drop the PDF
  2. Repair runs locally
  3. Download the repaired file

To fix a PDF that won't open, you rebuild its cross-reference table (the index that tells viewers where every page and object lives) around the content that survived. Structural PDF repair runs right here in your browser: drop the file above, the diagnosis shows what survived, and the repair engine rebuilds the index around it. Nothing is installed, and the document is never uploaded.

The errors this covers

There was an error opening this document. The file is damaged and could not be repaired.

Adobe Acrobat and Acrobat Reader. Read that wording carefully: it reports that Acrobat's recovery pass failed: "could not be repaired" means "not by Acrobat", not "not by anything". Acrobat's pass is conservative; a dedicated rebuild that scans the whole file for surviving objects gets further on exactly the files that produce this message.

Failed to load PDF document.

Chrome's built-in viewer. Same family of failure, terser wording. One check worth doing first: if this file was just downloaded, the download may have been cut short or may not be a PDF at all — an error page saved with a .pdf name shows exactly this. Re-download once; if it fails again, the file needs repair.

How PDFs break: the index and the pages

A PDF is a bag of numbered objects (pages, fonts, images, text streams) plus a cross-reference table (the "xref") that records the byte position of every object. The xref is the document's index: a viewer reads it first, then jumps straight to whatever it needs. It lives at the end of the file, because it's written last.

That position is its weakness. A truncated download, an interrupted save, an email gateway that clipped the attachment: anything that costs a PDF its tail takes the index with it, and viewers refuse the whole document even though the pages are still sitting in the file. If you've read our video pages, this is the same story as the MP4's missing index — the format differs, the failure rhymes.

It's also why repair works: object boundaries are visible in the raw bytes, so an engine can scan the file, find every object that survived, and write a fresh index pointing at them. Pages whose data is intact come back; the rebuilt file opens in any viewer.

Why no-upload wins for PDFs

Think about what people keep in PDFs: signed contracts, scans of IDs and passports, medical records, tax filings. The big online PDF suites are upload-based: your document travels to their servers, gets processed there, and exists as a copy outside your control for some period, however well-run the service is. In-browser repair removes that step rather than promising to handle it carefully: the file is read from your disk and rebuilt in your tab, and no copy ever exists anywhere else. You can verify that in the Network tab while the repair runs.

What this can and can't fix

Can fix

  • Damaged or missing cross-reference table — rebuilt by scanning for surviving objects
  • Truncated files: every complete page before the cut is salvaged
  • Broken trailers and object offsets that make viewers reject an otherwise-intact file
  • PDFs Acrobat's own recovery gave up on, when the page data survived

Can't fix

  • Pages whose object streams were overwritten — that content no longer exists in the file
  • Encrypted PDFs repair structurally, but opening them still requires the password
  • Scanned-image PDFs recover page by page — each scan comes back whole or not at all
  • 0-byte files: do data recovery first, then repair what it returns

The result report says which pages were recovered and which were lost, and a failed repair is never charged.

FAQ

How do I repair a corrupted PDF file for free?

Drop it into the tool above. Structural PDF repair runs right here in your browser (the document is never uploaded), and you get an honest result: a repaired file to download, or a plain explanation of what is broken and why it can't be fixed. The free tier covers documents up to 100 MB, 3 repairs per day, with a free download and no account. If the PDF came from a download or email, also try re-downloading it first: the source copy is often intact.

What does 'the file is damaged and could not be repaired' mean?

It's Adobe's wording for: Acrobat found the document's structure unreadable and its own recovery pass gave up. Read it precisely: it means Acrobat could not repair it, not that nobody can. The most common damage is a broken cross-reference table (the PDF's index), which can often be rebuilt by scanning the file for the objects that survived.

Why does Chrome say failed to load PDF document?

Chrome's viewer hit something it couldn't parse — a damaged index, a truncated file, or a download that isn't really a PDF (an HTML error page saved with a .pdf name is a classic). If re-downloading produces the same failure, the file itself is damaged and structural repair is the next step.

Can I fix a PDF that won't open without Adobe?

Yes. Repair doesn't require Acrobat or any install: the tool on this page reads the file locally in your browser, rebuilds the index around the objects that survived, and gives you back a standard PDF that any viewer can open.

Is it safe to upload a contract to an online PDF repair tool?

A contract is exactly the kind of document you shouldn't have to gamble with. Uploading creates a copy on infrastructure you can't inspect, under retention terms you didn't write. The alternative is a tool where no upload happens: here the repair runs in your browser, and you can watch the Network tab to confirm 0 bytes are transmitted.

Why is my PDF 0 bytes?

A 0-byte file contains no data: there is nothing in it to repair. That usually means the file was lost at the storage level (failed save, interrupted sync, deleted then carved back empty), which makes it a data-recovery problem: recover the bytes from the device first, then repair whatever the recovery returns if it doesn't open.

Related: spreadsheet won't open — repair Excel files · archive won't extract — repair ZIP files · photos with gray boxes — repair JPG photos ·verify the zero-upload claim