PDF

PDF Error: 'Not a Supported File Type or File Has Been Damaged'

Error message: Adobe Reader could not open '[filename]' because it is either not a supported file type or because the file has been damaged (for example, it was sent as an email attachment and wasn't correctly decoded).

This is one of Adobe’s broader error messages — the parenthetical hint about email attachments is a clue, but it’s only one of four distinct problems that produce this exact wording. The fix depends on which one you have, and identifying it takes about thirty seconds. Working through the diagnosis in order saves a lot of time spent on repair tools that wouldn’t have helped.

Quick fix

The four causes, in order of frequency:

  1. The file came from email and was corrupted in transit. This is the most common case — Adobe’s error text itself names it. Re-download the attachment using “Save As” rather than opening from the email preview pane. In Outlook, right-click the attachment and choose Save As. In Gmail, use the download arrow. If the second download produces a working file, the first was a transit casualty.
  2. The file is a OneDrive placeholder, not the actual file. OneDrive’s Files On-Demand feature shows files in the folder without storing them locally — they download when you open them, but some applications try to open the placeholder before the download completes. Right-click the file and check whether it shows a green checkmark (locally available) or a cloud icon (placeholder). If it’s a placeholder, right-click and choose “Always keep on this device,” wait for the download to complete, then try again.
  3. The file isn’t actually a PDF. Open it in Notepad (Windows), TextEdit (Mac), or any text editor. The first line should start with %PDF- followed by a version number like 1.4 or 1.7. If you see HTML, an error message, or random binary content, the file was saved with a .pdf extension but isn’t actually a PDF — usually a download error page that was saved instead of the real file.
  4. The file has a damaged or missing PDF header. Acrobat versions 10.1.5 and 11.0.01 introduced stricter parsing — the %PDF- header must appear at the very start of the file, not somewhere in the first kilobyte as older versions tolerated. A file with extra bytes prepended (commonly from email gateways or web servers adding metadata) will be rejected by current Acrobat but accepted by browsers and other readers. Try the file in Chrome, Firefox, or Edge — if it opens there, the file is otherwise fine and you can save a clean copy by printing it back to PDF.

If the first three quick checks identify the cause, you’re done. If none of them apply, the file genuinely has structural damage and the next section covers repair.

If that didn’t work

For genuine structural damage, qpdf is the standard tool. Open a terminal and run:

qpdf --linearize input.pdf output.pdf

This rebuilds the file’s cross-reference table and produces a cleanly-structured output. If qpdf reports warnings but completes successfully (exit code 3), the output file is usually fine — open it in Acrobat to verify.

If qpdf cannot process the file at all (exit code 2 with "file is damaged and cannot be processed"), the damage is severe enough that structural repair won’t help. In that case, your best remaining option is to ask the sender for a fresh copy. If that’s not possible, see the advanced recovery section below.

Advanced recovery

When qpdf fails, Ghostscript can sometimes salvage the visual content by re-rendering the entire file:

gs -o output.pdf -sDEVICE=pdfwrite -dPDFSETTINGS=/prepress input.pdf

This is a last resort, not a default. Ghostscript re-renders rather than repairs, which means the output loses form fields, annotations, digital signatures, bookmarks, and tagged accessibility structure. If the file is a contract, signed document, or anything where these elements matter, Ghostscript output is not equivalent to the original. Use it only when the alternative is no file at all and you only need the visual content.

Why this happens

The four causes have very different mechanisms.

Email transit corruption. Email transports binary attachments using base64 encoding (RFC 2045). At every relay between sender and recipient, the message gets parsed, sometimes scanned by antivirus, sometimes rewritten by gateways. Most of the time this works invisibly. Occasionally a relay encodes the attachment incorrectly, scans it in a way that modifies bytes, or truncates oversized messages. The recipient downloads what looks like a complete PDF but has subtly different bytes from what was sent. Adobe knows this happens often enough to mention it in the error text.

OneDrive Files On-Demand. Microsoft’s cloud-first sync model shows files in your OneDrive folder without storing them locally until they’re needed. Acrobat sometimes attempts to open a placeholder before OneDrive has downloaded the file, sees zero or partial bytes, and reports the file as damaged. The fix isn’t repair — the file is fine on the server, you just need to wait for the download.

File extension mismatch. A surprisingly common scenario: a website returns an HTML error page ("404 Not Found", a login page, a paywall message) when you tried to download a PDF, and your browser saves the response with a .pdf extension because that’s what you asked for. The file isn’t damaged; it was never a PDF. The 30-second text editor check above catches this immediately.

Stricter header parsing in modern Acrobat. Adobe’s pre-2013 readers accepted %PDF- headers that appeared anywhere within the first 1024 bytes of the file. Acrobat 10.1.5, 11.0.01, and later versions enforce stricter parsing requiring the header at byte zero. Files that were technically non-conforming but readable in older Acrobat are now rejected. This affects PDFs from certain server-side generators, files that have been through some content delivery networks, and PDFs with stray bytes added before the header. Browsers tolerate these files; current Acrobat does not.

Preventing this in future

For files you’ll send by email, prefer cloud links — Google Drive, OneDrive shared links, Dropbox, or a corporate file-sharing system — over direct attachments. Cloud links don’t go through the encoding layers that cause transit corruption, and the recipient can re-download if the first attempt fails.

For OneDrive users, configure important folders as “Always keep on this device” rather than relying on Files On-Demand for active work. The storage cost is trivial compared to the time cost of intermittent placeholder errors.

For developers generating PDFs server-side, validate output with qpdf --check before delivering. If your toolchain is producing files that current Acrobat rejects, you’ll find out at build time rather than from frustrated users.

If the file specifically came from an email attachment and you’ve confirmed transit is the cause, see the guide to PDFs from email that won’t open for the more detailed mail-client diagnostic sequence, or the broader email-corrupted PDF guide for the full transport story. For Adobe’s other catch-all error wording, see the guide to “file is damaged and cannot be repaired”. For the underlying technical explanation of PDF structure, the PDF repair pillar covers the format in depth.

Last verified: April 2026