Check a PDF’s health before you publish, archive, print, or send it to a client. A file can open perfectly on your computer and still contain broken fonts, unsafe metadata, weak accessibility tags, dead links, or hidden structure errors. A proper PDF health check reduces rework, protects your reputation, and helps the document behave the same way for every reader.
TLDR: A healthy PDF has embedded fonts, clean metadata, readable accessibility tags, working links, and no structural or rendering errors. For example, a 120-page compliance report may look fine, but one missing font can shift tables and make page numbers unreliable. In a review of 500 business PDFs, teams commonly find issues in about 18% to 30% of files before external release. Run checks in a PDF editor, accessibility checker, link validator, and preflight tool before sharing the final version.
Why PDF Health Checks Matter
PDFs are often treated as final, fixed files. That belief causes trouble. A PDF is not just a visual page. It contains font instructions, document properties, reading order, tags, links, bookmarks, images, scripts, forms, and internal references.
If any of those parts are damaged or incomplete, the file may fail in quiet ways. A screen reader may read headings in the wrong order. A printer may replace a font. A link may point to an old form. Metadata may reveal an internal author name or software path. Honestly, it feels like PDFs wait until the worst possible moment to expose these problems.
1. Check Fonts First
Fonts affect how the PDF looks, prints, and searches. If fonts are not embedded, another computer may substitute them. That can change spacing, symbols, line breaks, and legal text alignment.
Open the PDF properties panel in a professional PDF editor and review the Fonts tab. Each font should usually show as embedded or embedded subset. Subset embedding is common and acceptable when only used characters are stored in the file.
Watch for these warning signs:
- Fonts listed without embedded status, especially in forms, contracts, or branded documents.
- Symbol fonts that render bullets, math, or icons incorrectly.
- Mixed font versions from several editing passes.
- Text that looks like an image, which blocks proper search and selection.
If a font is missing, export the PDF again with font embedding enabled. If you received the file from a designer, ask for a corrected export rather than patching the file without source assets.
2. Review Metadata for Accuracy and Privacy
Metadata is hidden information stored inside the PDF. It may include the title, author, subject, keywords, creation date, modification date, software name, language, and copyright status.
Open the document properties panel and inspect each field. The Title should match the real document name. The Author should be a person, department, or organization approved for release. Remove draft labels unless they are still true.
Be strict with privacy. Metadata can expose names of staff, contractors, templates, or legacy systems. That may not sound dramatic, but it can create compliance problems. Expect to waste time on this if files have passed through several hands, because each editing tool may add its own traces.
Check for:
- Incorrect title shown in browser tabs or search results.
- Internal author names that should not be public.
- Old keywords from a reused template.
- Wrong language settings, which affect accessibility tools.
- Hidden comments or attachments left from review cycles.
For public files, remove private metadata and save a clean copy. Keep the original in your records if audit history matters.
3. Test Accessibility, Not Just Appearance
An accessible PDF can be read by people using assistive technology. It also works better for indexing, copying, searching, and long-term management.
Start with an accessibility checker in a reliable PDF editor. Then manually inspect the results. Automated tools can catch many problems, but they cannot understand every layout choice.
Focus on these items:
- Document language: Set the correct language so screen readers pronounce words properly.
- Tags: Headings, paragraphs, tables, lists, and figures should use proper tags.
- Reading order: Content should be read in a logical sequence, not by visual placement alone.
- Alt text: Meaningful images need short, useful descriptions.
- Tables: Header cells should be marked correctly.
- Form fields: Labels and tooltips should be clear.
- Color contrast: Text must remain readable for low-vision users.
Do not trust a green status mark without review. A document can pass basic checks and still have a terrible reading order. Multi-column reports, scanned pages, and designs with sidebars need special attention.
4. Validate Links, Bookmarks, and Cross-References
Broken links are one of the easiest PDF errors to miss. They are also one of the most annoying for readers. A link to a pricing page, policy form, citation, or email address can become outdated within weeks.
Click every visible link in short documents. For large files, use a link checker or script that extracts URLs and tests response codes. A healthy link should point to the intended destination, load without security warnings, and use the right protocol.
Check these link types:
- External website links, including redirects and expired domains.
- Email links, with correct addresses and subject lines where needed.
- Internal page links, such as table of contents entries.
- Bookmarks, especially in long reports and manuals.
- Footnote and citation links, which often break after layout changes.
Pay attention to links hidden behind buttons, icons, QR codes, and form controls. A QR code should be tested with a phone, not just visually inspected.
5. Run a Preflight Check for Document Errors
Preflight tools inspect the technical structure of a PDF. They can detect issues that normal viewing does not show. This is especially useful for print, archiving, legal submission, and regulatory documents.
Use a preflight profile that fits the job. A print shop may require PDF/X. An archive may require PDF/A. A court or agency may have its own PDF rules. Do not use random settings and hope for the best.
A good preflight check may flag:
- Corrupt objects or damaged internal references.
- Missing fonts or unsupported font types.
- Low-resolution images for print use.
- Transparency issues that may render poorly.
- Color space problems, such as RGB used in print files.
- Invalid PDF/A or PDF/X compliance.
- Oversized file structure caused by unused assets.
Preflight reports can look harsh. Not every warning is fatal. Separate true errors from advisory notices. Fix anything that affects readability, reproduction, compliance, or file stability.
6. Inspect Scans and OCR Quality
Many PDFs are scanned paper documents. These need extra care. A scan may look readable to the eye but fail search, copying, and accessibility checks.
Run optical character recognition, then test the text layer. Try selecting a sentence. Search for a known phrase. Copy text into a plain text editor and check whether letters, numbers, and punctuation survive correctly.
Common OCR issues include mixed-up characters, missing accents, split words, and headers repeated in the wrong order. For legal, medical, or financial files, do not rely on OCR without sampling several pages.
7. Check Forms, Signatures, and Security Settings
Interactive PDFs need review beyond static content. Fill every form field. Test required fields. Check dropdowns, checkboxes, date fields, and calculation fields. Submit buttons should send data to the correct place, if submission is used.
Security settings also need care. Password protection can block printing, copying, screen readers, or archiving. Digital signatures should be valid and visible where expected. If the file was modified after signing, the signature may break.
Use restrictions only when needed. A locked file that blocks assistive technology can create serious access issues.
A Practical PDF Health Checklist
Use this checklist before release:
- Open the PDF on at least two devices or viewers.
- Confirm all fonts are embedded.
- Clean title, author, keywords, and hidden review data.
- Run an accessibility check and review reading order by hand.
- Test links, bookmarks, QR codes, and internal references.
- Run the right preflight profile for print, archive, or web use.
- Verify OCR quality for scanned pages.
- Test forms, signatures, permissions, and passwords.
- Save a final copy with a clear version name.
When to Escalate the File
Some PDF problems should be sent back to the source creator. Missing fonts, broken layout, poor scan quality, and failed compliance profiles are often easier to fix from the original document. Editing the PDF itself may create new problems.
If the PDF is for legal filing, accessibility compliance, high-volume printing, investor reporting, or public government use, get a second review. The cost of one failed release can be far higher than the time spent checking the file.
A healthy PDF is predictable. It opens cleanly, reads correctly, prints reliably, protects private data, and sends readers where links promise to send them. That is the standard worth using before any serious document leaves your hands.