How to check a PDF for problems
A useful PDF check examines six separate areas: the text layer, page geometry, fonts, permissions, links and forms, and the file’s internal integrity. You can perform the first checks by hand without uploading the document; start with the matching guide in Document Doctor when a result points to a specific problem. A PDF may look normal while still containing text, printing, editing, or interactive features that fail elsewhere, so test the parts people need to use rather than relying on appearance alone.
Six checks reveal different kinds of PDF problems
There is no single pass-or-fail test that describes the health of every PDF. A document intended only for reading has different requirements from a form, a print-ready file, or a scanned archive. The practical approach is to inspect six areas and judge each result against the document’s purpose.
A text-layer check shows whether words are searchable and selectable
A PDF page can display letters without containing usable text. Scanned pages often begin as images of words, and outlined lettering may look like text even though each character has been converted into a drawn shape.
Try selecting a sentence with the text-selection tool. Then copy it into a plain-text editor and search for a distinctive word with Ctrl+F on Windows or Command+F on macOS.
A healthy text layer should normally let you:
- Select individual words in a sensible order.
- Search for text that is visibly present.
- Copy text without producing blank output or unrelated symbols.
- Use screen-reading, indexing, translation, and editing tools where the document permits them.
If nothing can be selected, the page may be an image-only scan. If selection works but copied text is scrambled, the problem may involve character encoding, font mapping, reading order, or poor optical character recognition. Security restrictions can also block copying, so check permissions before concluding that the text itself is defective.
OCR can add a searchable text layer to scanned pages, but recognition is not automatically accurate. Names, numbers, small print, handwriting, tables, and low-contrast scans deserve a manual review after OCR.
Page-geometry checks expose clipping, scaling, and mixed-size pages
Every PDF page has a defined size, and some PDFs also contain several page boundaries for display, artwork, trimming, and bleed. A document can therefore look correct on screen but print with missing edges, excessive margins, unexpected scaling, or different page sizes.
Open the page thumbnails and compare several pages rather than inspecting only the cover. Look for:
- Pages that suddenly become wider, taller, or rotated.
- Content positioned very close to an edge.
- Crop marks or artwork disappearing in print preview.
- A mixture of A4, Letter, Legal, or custom dimensions.
- Blank space that appears to be part of the page rather than an ordinary margin.
- Text or graphics that are visible only when the crop boundary is changed.
Use the print dialog to compare Actual size with Fit. Actual size reveals whether the PDF page is larger than the selected sheet and may be cropped. Fit scales the whole page into the printer’s available area, which can hide the underlying mismatch by making the output smaller.
Mixed page dimensions are not necessarily an error. A report might deliberately include a landscape chart or an oversized drawing. The problem is a size or boundary that conflicts with the intended output and causes content to move, shrink, or disappear.
Font checks identify substitution and missing-character risks
Embedded fonts carry the font data needed to display or print the document as intended. When a required font is not embedded and is unavailable on another device, a PDF viewer may substitute a different typeface.
Substitution can change character shapes, spacing, line lengths, and visual emphasis. In more serious cases, characters may appear as boxes, bullets, question marks, or blank spaces. Problems can affect only one font or one group of characters, so a quick glance at the first page is not enough.
In a desktop PDF application, open Document Properties and inspect the Fonts tab. Check whether the fonts are listed as embedded or embedded subsets. A subset is normal when the PDF includes only the characters actually used in the document.
Then inspect pages containing:
- Bold, italic, condensed, or decorative type.
- Currency symbols and mathematical notation.
- Accented letters and non-Latin scripts.
- Form fields whose text uses a different font from the page.
- Text added during editing, signing, or annotation.
- Unusual symbols, icons, or custom corporate fonts.
A font can display correctly on your computer because it is installed locally. That does not prove the PDF will display identically on another device. Testing the file in a second viewer or on a second system helps distinguish embedded document resources from fonts supplied by your own computer.
Permission checks explain why apparently available actions are blocked
PDF security settings can allow a file to open while restricting printing, editing, copying, commenting, signing, page extraction, or form completion. This means an unavailable command is not always evidence that the document is damaged.
Open Document Properties, select Security, and read the document restrictions summary. Compare the listed permissions with the task you are trying to perform.
Common permission-related symptoms include:
- Text can be read but not copied.
- Printing is unavailable or limited to reduced quality.
- Pages cannot be inserted, deleted, or extracted.
- Comments or form changes cannot be saved.
- Editing tools appear disabled.
- A password is requested only when you attempt to change the file.
Link and form checks test the PDF’s interactive layer
Links, buttons, checkboxes, fields, and menus can look like ordinary page content even when their interactive behavior is missing or incorrect. A blue underlined web address, for example, is not necessarily an active link. A printed line or empty box is not necessarily a form field.
Test links by activating them rather than judging their appearance. Check internal links, external web addresses, email links, and links intended to open attachments or other files. Confirm that each one goes to the expected destination and does not depend on a file path that exists only on the creator’s computer.
For forms, click or tab through every field. Enter representative information and test checkboxes, radio buttons, lists, calculations, reset controls, and submission actions where applicable. Save a copy, close it, and reopen it to confirm that entered values remain available.
Watch for these symptoms:
- A visible field cannot receive focus.
- Typing in one field changes another field unexpectedly.
- Text is present but invisible because its appearance is not rendered.
- A button has no action or opens the wrong destination.
- A link works in one viewer but not another.
- Tab order moves through fields in a confusing sequence.
- Completed values disappear after saving or printing.
Interactive behavior can vary between a browser viewer, a desktop application, and a mobile app. If forms or links are essential, test the document in the environment its recipients are likely to use.
File-integrity checks distinguish structural damage from content problems
A PDF is built from interconnected objects, streams, page records, resources, and cross-references. If those structures are incomplete or inconsistent, a viewer may report that the file is damaged, repair it while opening, omit pages, display blank areas, or fail to open it at all.
Begin with simple observations. Confirm that the download completed, the file size is plausible, and the filename ends in .pdf. Open the document in a second reputable viewer. Move through every page, zoom in and out, search for text, and save a copy if the application permits it.
For a technical syntax check, a local validation utility such as qpdf can inspect the PDF’s structure, encryption, linearization, and stream encoding. A clean structural result is useful, but it is not a complete content audit. A syntactically valid file can still contain a broken link, inaccurate OCR, missing font, clipped page, or nonworking field.
What each check result means for your document
Interpret the results together rather than treating every unusual property as damage. The correct question is whether the document reliably supports its intended use.
| Check | A reassuring result | A result that needs investigation |
|---|---|---|
| Text layer | Visible words can be selected, searched, and copied accurately | Text cannot be selected, search misses visible words, or copied characters are wrong |
| Page geometry | Page sizes and boundaries match the intended screen or print output | Pages are clipped, unexpectedly scaled, rotated, or inconsistent without a clear reason |
| Fonts | Required text displays consistently and important fonts are embedded or safely supported | Characters change, disappear, or substitute on another device |
| Permissions | Allowed actions match the document’s purpose and ownership rules | A required action is blocked, or restrictions are mistaken for file damage |
| Links and forms | Destinations, fields, buttons, calculations, and saved values behave as intended | Interactive elements are inactive, misdirected, duplicated, invisible, or viewer-dependent |
| File integrity | The file opens consistently, all pages render, and a structural check reports no errors | A viewer repairs the file, pages are missing, errors appear, or different viewers produce different results |
A failed text-layer check does not necessarily mean the PDF is unreadable. It may still be visually clear but unsuitable for search, copying, accessibility, or text extraction. Likewise, a restricted PDF may be structurally healthy even though you cannot edit or print it.
Prioritize a result according to its consequence:
- Reading problem: Content is blank, distorted, incomplete, or difficult to navigate.
- Search or accessibility problem: Visible information cannot be selected, found, extracted, or read in a meaningful order.
- Print problem: Page dimensions, crop boundaries, scaling, or fonts change the physical output.
- Editing problem: Permissions, missing fonts, scans, or signed-document rules prevent legitimate changes.
- Interaction problem: Links, fields, buttons, calculations, or saved values do not work.
- Integrity problem: The file cannot be parsed consistently or must be reconstructed by the viewer.
Also separate a repeatable document defect from an application-specific failure. If the same symptom appears in several viewers or on several devices, the PDF itself is the likely source. If it occurs in only one browser or app, update that software, disable conflicting extensions, and test in a desktop viewer before rebuilding the document.
Check the file by hand before choosing a repair
Use a copy of the original PDF for testing, especially if it contains signatures, completed fields, comments, or security settings. A repair can change more than the symptom you are trying to correct.
- Open the PDF in a desktop viewer. Record any warning about damage, unsupported features, fonts, passwords, or repairs. Move through every page rather than assuming that a successful opening proves the entire file is sound.
- Test the text layer. Select a sentence, copy it into a plain-text editor, and search for a visible word. Repeat the test on a scanned page, a page with unusual symbols, and a page near the end of the document.
- Compare page dimensions and print behavior. Review thumbnails for mixed sizes or rotations. Open print preview and compare Actual size with Fit without sending the job to a printer. Look for clipped edges, unexpected reduction, and inconsistent orientation.
- Inspect fonts and security. Open Document Properties and review the Fonts and Security tabs. Note any font that is not embedded and any restriction that blocks the action you require.
- Activate every important link and field. Do not test with sensitive personal data. Use made-up values, save a test copy, reopen it, and confirm that the form retains the values and that links still reach the intended destinations.
- Repeat the critical tests in another viewer. A second result helps distinguish a document defect from a browser, extension, cache, or application problem. Use the type of device your intended recipient is likely to have.
- Run a local structural check when corruption is suspected. Use a reputable validation tool if the PDF opens with repair warnings, behaves differently between viewers, or loses pages and objects. Remember that syntax validation does not verify the accuracy of the visible content.
- Choose the smallest appropriate repair. Add OCR for an image-only scan, correct page boundaries for clipping, recreate a defective link, repair form fields, re-export with fonts embedded, or obtain an authorized copy when permissions are the issue. Rebuilding the entire PDF should not be the first response to one isolated defect.
After any repair, repeat all checks that the change could affect. OCR should be reviewed for recognition errors. Resizing should be checked for clipping and unwanted scaling. Font changes should be tested on another system. Form repairs should be saved, reopened, and printed. Structural recovery should be followed by a page-by-page visual comparison with the best available original.
A PDF health check is complete only when the file’s important functions have been tested against its real purpose. A document that merely opens is not necessarily ready to search, print, edit, complete, sign, archive, or share.
Source: PDF text recognition guidance from Recognize text in scanned documents, document property guidance from Document properties and metadata overview, page-boundary guidance from Printer marks and hairlines, font guidance from Embedding fonts in PDFs overview, link guidance from Add links to PDFs, and form guidance from PDF forms help, Adobe; structural validation guidance from Running qpdf, qpdf documentation. Page last checked 2 October 2026.