Skip to main content
Orilami
File RepairJPEGPNGPDF xref

File Repair: before and after

An illustration with sample files; your own files show their own results.

BeforeDamaged files that will not open

  • JPEG cut off mid-way

  • PNG header damaged

  • PDF index corrupt

AfterRepaired, and what changed is reported

  • Opens, shows what was saved

  • Opens normally again

  • PDF index rebuilt

File Repair: Fix Corrupted JPEG, PNG and PDF Files

A client-side repair tool for damaged JPEG, PNG and PDF files. It reconstructs broken headers, stitches truncated streams and rebuilds corrupted PDF cross-reference tables, using bounds-checked parsing so a fuzzed or malicious file can't over-read memory.

What it repairs

  • JPEG: missing SOI/EOI markers, leading or trailing garbage, truncated scans.
  • PNG: broken 8-byte signature, wrong chunk lengths, bad CRC-32s, missing IEND, truncated IDAT.
  • PDF: broken trailer or startxref, xref table rebuilt by scanning raw obj entries, best-effort /Root recovery.

Frequently asked questions

What kind of file corruption can actually be repaired?
Structural damage: broken or missing headers, truncated image streams, and PDF cross-reference tables that no longer point at the right objects. The content is still there and only the map to it broke, so the map can be rebuilt.
Why won't my file open at all?
Most often the header is damaged, so the application rejects the file before reading any content. A transfer or memory-card error that cut the file short has the same effect. Both are common repairable cases.
Can a partly recovered photo be fixed completely?
Not if data is missing. A truncated JPEG can be made to open and everything written will display, but the part that never arrived cannot be invented. The tool shows how much was recovered instead of filling the gap.
Should I run this on my only copy?
Yes, it is safe: the repair works on a copy in your browser and your original on disk is never modified. Keeping a backup before any recovery attempt is still good practice.
Is my damaged file uploaded to a recovery service?
No. The repair runs in your browser. Recovery sites that ask for an upload also receive whatever the file contains.
Can it guarantee the repaired file opens?
No. It repairs container structure (markers, chunks, xref). If the payload itself is destroyed, structure alone can't bring the pixels back.
More questions about Orilami

File Repair at a glance

Key facts about File Repair: where it runs, what it costs, what it accepts and produces, and its limits.
Where it runsEntirely in your browser. Files are never uploaded.
Cost200 tokens per repaired file (about $2.00 at the base rate)
AcceptsJPEG, PNG, PDF
ProducesA repaired file where the damage is recoverable, with a report of what was rebuilt.
BatchUp to 50 files per run.
Account neededOnly to spend tokens. Browsing and previewing are free.
What it does not doIt repairs structural damage. Bytes that were never written, or are physically gone, cannot be reconstructed.