"Format error: Not a PDF or corrupted" — how to rebuild the file.
A PDF tool reported "Format error: Not a PDF or corrupted" because it could not recognize a valid header, cross-reference table, or trailer in the bytes it read. FileFix runs independent rebuild paths and shows page and object counts from a validated result before you decide. A one-time $12 — and only if the repair works.
Free preview — pay only if you download ($12)
Your files auto-delete within 48 hours
No person looks at your file as part of repair
Uploading your file.
Keep this tab open while the file transfers. Large files can take a few minutes.
Starting upload...
Recovering what we can.
Analyzing your file...
Here's what we recovered.
Review the watermarked preview before checkout. Previews are capped at 90 seconds.
Repair your file
Choose a supported file to see what can be repaired before checkout.
Simulated checkout — no payment is processed.
Optional — we'll email your private download link.
Download repaired fileYou preview before you pay. If the download is materially worse than the preview you approved, we'll refund you.
Good news — your file isn't damaged. No charge.
There's nothing to repair. If it still looks broken, the issue may be the player, codec, or viewer on your device rather than the file itself.
We couldn't recover this one.
The file is too damaged to rebuild, so there is nothing to preview and no charge. You can try another file.
Have another clip from the same device?
A healthy video recorded on the same device — ideally the same settings — gives the repair engine a template to rebuild from. It can unlock repairs that fail on their own.
FileFix can't fix that kind of file yet.
Right now we repair video, audio, and document files (MP4, MOV, M4V, MKV, AVI, TS, MTS, M2TS, MPG, MPEG, VOB, 3GP, WebM, M4A, WAV, MP3, AAC, FLAC, OGG, AIFF, XLSX, DOCX, ZIP, and PDF). We're adding support for more formats over time.
Something went wrong.
The request could not be completed.
Why this happens
"Not a PDF or corrupted" is an identity-and-integrity check reported by many PDF libraries and viewers. It fires when the opening bytes do not present a usable PDF header, or when the cross-reference and trailer that a reader relies on are missing, stale, or point past the end of the file.
The same message covers two different situations. Sometimes the file is genuinely another format — an HTML error page, an image, or a truncated download saved with a .pdf name. Other times it is a real PDF whose header or index was damaged while some page objects remain intact in the bytes.
FileFix inspects the uploaded bytes, runs several PDF recovery and rewrite paths, and reopens each candidate with recovery mode disabled. A result is only offered when it contains at least one readable page; the summary then reports validated page and object counts rather than assuming the original was complete.
What we can and can't recover
We can usually fix
- PDFs that show "the file is damaged and could not be repaired"
- PDFs Chrome or Edge won't open ("Failed to load PDF document")
- files cut off mid-download or mid-save
- PDFs with a broken cross-reference table or trailer
We can't fix
- password-protected or encrypted PDFs
- genuinely empty (0-byte) files
- deleted or formatted files (that's data recovery, a different job)
- pages whose content was never written to disk
How it works
- Upload. Drop the file in. It uploads over an encrypted connection.
- We rebuild it. The repair runs automatically — no person looks at your file.
- Read the summary, then decide. You see exactly what we recovered — page and object counts and a short excerpt of recovered text. If the summary shows what you need, unlock the repaired PDF for a one-time $12.
You see a recovery summary built from your actual file before you decide anything — so you never guess.
Upload your PDF
Free recovery summary · files auto-delete within 48 hours
Browse by problem
Questions
Does this message always mean my PDF is damaged?
No. The same error appears when the file is really another format saved with a .pdf name, such as a web error page. If the bytes are not a PDF, repair cannot turn them into the document you expected; re-download it from the original source.
How can FileFix open a file that my PDF tool rejected outright?
Different parsers tolerate damaged headers and cross-reference data differently. FileFix rewrites the object structure and validates the result with a separate non-recovery open, so it can sometimes rebuild a file another tool refused to parse.
Will the rebuilt PDF keep its original page order?
The engine preserves the page objects it can recover and reports the validated page count. It does not invent pages that were absent from the upload, so compare the repaired count against what you expected before checkout.