It usually starts with a bad half-hour: a PDF that always opened fine now refuses to open at all, or opens half-drawn — first pages visible, the rest blank — or throws a "file is damaged" error and closes. The instinct is to assume the file is gone. Often it isn't. A corrupted PDF is frequently a file whose contents are mostly intact but whose internal structure is broken — and a broken structure is something a repair tool can rebuild. Repair PDF does it entirely in your browser, without uploading the file anywhere.
This guide covers what corruption actually is, what it looks like, the boring fixes to try first, and — honestly — what repair can and can't get back.
What "corrupted" actually means
A PDF isn't a single stream of text; it's a structured file. Content — text, images, fonts — lives in objects scattered through the file, and a cross-reference table at the end maps out where everything is. A PDF reader opening the file reads that map first and navigates by it.
Corruption is what happens when the map and the territory stop agreeing: the cross-reference table is broken, or objects are invalid or malformed. The content can still be sitting there, byte for byte, but the reader can't find its way around it — so it refuses to open the file, or gives up halfway through drawing it. That's why "damaged" so often means "disorganized" rather than "destroyed."
How corruption looks from the outside
- The file won't open at all — the reader reports it as damaged and gives up.
- It opens partially — some pages render, others come up blank or stop the viewer cold.
- One reader opens it and another refuses — lenient viewers paper over damage that strict ones reject.
- The file is noticeably smaller than it should be — a sign the end of the file, map included, never made it.
Before you repair anything: try the boring fixes
Repair is for files with no intact copy left. Check that yours is really one of them first, because re-copying beats rebuilding:
- Re-download or re-copy from the source. An interrupted download is the classic cause of a broken PDF, and downloading again — completely, in one pass — fixes it for free.
- Get the original re-sent. If the file arrived by email or chat, ask for it again; transfers get truncated silently more often than anyone notices.
- Check the copy, not the source. A file that stopped working after being copied to a USB stick or a cloud folder may simply be a truncated copy — recopy it and compare sizes.
If a fresh copy exists anywhere, use it. Repair is the move for when it doesn't.
What repair can and can't do
The honest version, because pretending otherwise helps nobody:
What it can do: re-read your PDF leniently and rebuild a clean, valid file from what's recoverable. That covers many common problems — a broken cross-reference table, invalid or malformed objects, or a file that other viewers refuse to open. The structure is rebuilt around the content that's still intact.
What it can't do: bring back content that's truly missing or unreadable. If the data is gone — truncated off the end of the file, overwritten, never downloaded — no repair tool can restore it, this one included. Repair rebuilds structure; it doesn't invent content. A rebuilt file contains everything that survived and nothing that didn't.
How to repair a corrupted PDF
- Open Repair PDF and drop in the damaged file — up to 100 MB, processed locally in your browser.
- Confirm, and let it work. There are no settings to configure; repair is automatic.
- Download the rebuilt file.
- Spot-check it — scroll to a few places deep in the document, especially past the point where the broken version gave up.
That last step deserves more than a glance. A rebuilt file is only as complete as the content that survived, so check the places damage was visible before: the pages that drew blank, the section where the old reader stalled, the images that rendered as gray boxes. If you knew the original page count, compare it. Five seconds of scrolling tells you whether you have a whole document back or a partial one that changes your next move.
Why PDFs break in the first place
Usually an interrupted download or save, a bug in whatever created the file, or an incomplete transfer. What these share is that they interrupt the file mid-write: the PDF gets saved only partway, or its final structural section never arrives, and the map ends up broken even though most of the content is still there. Files living on failing storage can suffer the same fate — the file is present, but pieces of it no longer read correctly.
If the rebuilt file still isn't whole
When repair succeeds structurally but the file was truncated, the rebuilt PDF will contain what survived — and the honest next move is going back to the source: the original attachment, the sender's copy, the application's autosave, last night's backup. None of those depend on the damaged file at all.
An ounce of prevention
Every cause of corruption in the section above has a boring, reliable countermeasure. Let downloads finish completely before opening the file — the preview that opens mid-download is reading a file that doesn't exist yet. Save documents before the application, the battery, or the network decides to end the session for you. When a file matters, make a second copy somewhere else the day it's created, not the day it breaks. And treat removable media and flaky transfers as suspect by default: copy the file to your device properly, then open the copy.
Repair is a good tool to have and a bad one to need. The quiet lesson of every repair story is that the best protection against corruption is an intact second copy, made before anything goes wrong.