An upload form that says your PDF is invalid or damaged

When an upload form says your PDF is invalid, damaged or unreadable, but the same file opens perfectly well in Preview, the file is usually one of five things: not really a PDF, protected by a password, structurally damaged in a way Preview quietly works around, too big for the form, or named in a way the form dislikes. Check them in that order. Most take under a minute, and the fix for each is a new copy of the file, so the original stays as it is.

Why a PDF that opens fine can still be rejected

Preview is forgiving. When it meets a PDF with a broken index or a slightly malformed page, it rebuilds what it needs in memory and shows you the document without complaint. The software behind an upload form is often much stricter. It may check the structure, read the text or count the pages, and if any step fails it reports the whole file as invalid.

So “it opens on my Mac” tells you the content is there. It does not tell you the file is clean. The checks below find which rule the form is enforcing.

Check 1: is it really a PDF

A file can end in .pdf without being one. A download that stopped early, a web page saved with the wrong name, a Pages document renamed by hand, or a photo exported from a phone app can all carry a .pdf extension.

1. Select the file in Finder and choose File, Get Info. The Kind line should say PDF document.
2. For a firmer answer, open Terminal, type file and a space, drag the PDF onto the window, and press Return:

file ~/Downloads/application.pdf

A real PDF reports something like PDF document, version 1.7. If it says HTML, Zip archive, JPEG or just data, the form is right: that file is not a PDF. Open the original document again and export it properly (in most Mac apps, File, Export To, PDF, or File, Print, then the PDF menu, Save as PDF). If the file came from a download, download it again. If it shows a cloud icon in Finder, it may not be fully on your Mac yet; a file that will not open because iCloud kept a placeholder covers that case.

Check 2: is it password-protected

Many upload systems refuse encrypted PDFs, including ones you can open without typing anything. A PDF can carry a permissions password that blocks printing, copying or editing while still opening freely, and to a strict form that is still an encrypted file it cannot process.

A quick test in Terminal:

grep -ac "/Encrypt" ~/Downloads/application.pdf

A result of 0 means the file is not encrypted. Any higher number means it is.

If you know the password, or the file opens without one, make an unprotected copy. Open it in Preview, choose File, Export, and save it as a PDF under a new name, leaving any encryption or permissions options switched off. If Preview will not let you export because the file restricts it, File, Print, then the PDF menu, Save as PDF produces a new file without the protection. Printing to PDF flattens fillable form fields into plain page content, which many forms prefer anyway.

If you do not know the password, ask whoever made the file for an unprotected version. No honest tool will remove a password you do not have, and Manatee does not try.

Check 3: is the structure damaged

This is the case where Preview’s forgiveness hides the problem. The file opens, the pages look right, and the form still says it is corrupt. Typical causes are a download or copy that was interrupted near the end, a sync conflict, or a save that went wrong partway. Preview reads what it can; the form’s parser gives up.

There are two ways to get a clean copy.

Re-save it through Preview. Open the PDF, choose File, Export, and save a new copy. Preview writes the document out from scratch, with a fresh structure. This fixes a lot of rejections, with a caveat: Preview’s rewrite can drop some features and occasionally makes things worse on complex files, as described in a PDF that broke after you saved changes to it in Preview. Keep the original and check the new copy page by page.

Repair it with Manatee. Open Manatee, choose Repair, and drop the PDF in, or right-click it in Finder and choose Services, Fix with Manatee. It writes a repaired copy next to the original and never touches the original. The result is reported honestly: Fixed, Partial (for example, 34 of 41 pages recovered), or Not fixable. A Partial result tells you exactly what you have before you upload it. The repair runs on your Mac; the file is not uploaded anywhere. How to repair a corrupted PDF on a Mac goes into what can and cannot be rebuilt.

Check 4: is it simply too big

Some forms state their size limit clearly. Others fail with a generic “invalid file” message when the real problem is size, or when the upload times out partway. If the PDF is several megabytes and the form’s help text mentions any limit, assume size is the issue until you rule it out.

Look at the size in Finder, then compare it with the limit. If it is over, Manatee’s Shrink mode lets you type the size you need in MB and finds the quality that fits. How to get a PDF under 10 MB for an upload portal and how to get a PDF under 2 MB for a job application walk through the options, including the built-in Quartz filter in Preview.

Check 5: the details forms are fussy about

If the file is a real, unprotected, undamaged PDF within the size limit and the form still refuses it, look at the smaller things.

• The file name. Slashes, colons, emoji, accented letters or very long names trip some systems. Rename it to plain letters, numbers and hyphens, such as smith-application-2026.pdf, and make sure it ends in .pdf once, not .pdf.pdf.
• Attachments and portfolios. A PDF can carry other files inside it, or be a portfolio of several documents in one. Forms that expect a simple document may reject these. Printing to PDF, as in Check 2, produces a plain single document.
• Fillable fields and signatures. Some forms reject PDFs that still have live form fields. Printing to PDF flattens them. Be aware that it also removes a digital signature, so if the signature matters, ask the form’s help desk what they accept.
• The browser. Occasionally the form itself is the problem. Try a different browser, or a private window.

Questions

Why does the form accept other PDFs but not this one? Because the rule it is enforcing only applies to some files. Encryption, a damaged structure and attachments are all invisible when you view the document, which is why this file looks no different from the ones that worked.

Will re-saving or repairing change what the document says? It should not change the text or images on the pages. It can drop extras such as live form fields, signatures, bookmarks or attachments, so compare the new copy with the original before you upload it.