7 Common PDF Mistakes That Trip Up Professionals (And How to Fix Every One)

<p>The single most common PDF problem in business communication is file size. Gmail's attachment limit is 25 MB. Outlook's default limit is 20 MB. Many corporate email servers enforce limits as low as 10 MB. A presentation exported from PowerPoint with full-resolution images routinely hits 40–80 MB. A multi-page report with embedded photos can reach 150 MB. The result: emails bounce, recipients get attachment-not-included versions, or senders resort to clunky workarounds like WeTransfer links when a compressed PDF would have been fine all along.</p><p>The root cause is almost always unnecessary image resolution. A photograph embedded in a PDF at 300 dpi — correct for print — contains about 9 times more pixel data than the same image at 100 dpi, which is sufficient for screen reading at normal zoom levels. A single high-resolution photo at full print resolution takes up approximately 3–5 MB in an uncompressed PDF. A presentation with 20 such photos is 60–100 MB before any other content is added.</p><p>Most PDF creation tools do not compress images aggressively by default. Microsoft Word's &quot;Export to PDF&quot; preserves images at nearly their original resolution. Adobe InDesign's default PDF export settings are configured for print, not web distribution. Google Slides exports at reasonable resolution but PowerPoint does not. The fix is simple: use a PDF compressor after export, or change export settings before creating the PDF.</p><p>The compression sweet spot for email-ready PDFs is the &quot;screen&quot; or &quot;web&quot; preset in most tools, which downsamples images to 72–96 dpi and applies JPEG compression at approximately 70–80% quality. This produces files that look sharp at 100% zoom on any modern display while reducing file size by 60–85% compared to the original. A 50 MB presentation typically compresses to 3–8 MB with no visible quality loss at normal viewing sizes. For presentations intended for both screen sharing and potential printing, the &quot;ebook&quot; or &quot;medium quality&quot; preset — typically 150 dpi images — gives a reasonable balance: files stay under 15 MB while preserving adequate print quality for home and office printers.</p><p>The other file size culprit is embedded fonts. A PDF that embeds every font used in a 30-page document can add 1–3 MB of font data. For standard fonts (Times New Roman, Arial, Helvetica, Calibri), embedding is often unnecessary — every computer has these fonts. For specialty fonts (brand typefaces, icon fonts, display fonts), embedding is essential to prevent rendering failures. Font subsetting — embedding only the characters actually used in the document rather than the complete character set — reduces font data by 50–90% and is the default in modern PDF creation tools.</p>

1. 1Compress the PDF before sending if it exceeds 10 MBUse LazyPDF's free compressor at /en/compress. Upload the PDF, select the compression level that matches the use case — Screen for email-only, Medium for email that may also be printed — and download. Most presentations and reports compress to under 5 MB in under 30 seconds. The tool preserves the visual appearance at normal zoom and maintains all text, links, and structure.
2. 2Change export settings at the source for recurring workflowsIn PowerPoint: File → Export → Create PDF/XPS → Options → set Image quality to 150 dpi for email-friendly output. In Word: File → Save As → PDF → Options → Bitmap text when fonts may not be embedded (unchecked) → Optimize for: Standard for print, Minimum size for email. In InDesign: File → Export PDF → Compression → Bicubic Downsampling to 150 ppi for images above 225 ppi. Setting this once saves repeated compression steps.
3. 3For very large files, split before compressingA 200-page document may still exceed email limits even after compression. Split it into logical sections first using LazyPDF's split tool at /en/split, then compress each section. Recipients can reassemble with merge if needed. A 200-page report split into four 50-page sections at 5 MB each is far more usable than a single 60 MB file that cannot be emailed at all.

<p>Font embedding is the PDF feature most people have never heard of and most frequently encounter the consequences of. When a PDF does not embed a font, it relies on the recipient's computer having that font installed. If the font is not present, the PDF viewer substitutes the closest available font — which changes character spacing, line breaks, paragraph flow, and sometimes produces entirely unreadable substitution glyphs. A meticulously formatted document can be reduced to something resembling an early internet page viewed on an incompatible browser.</p><p>Specialty fonts are the primary risk: brand typefaces that a company licensed and installed company-wide, display fonts used in marketing materials, icon fonts that render symbols rather than text characters, and international fonts for scripts with large character sets (Chinese, Japanese, Korean, Arabic). If any recipient opens the PDF on a machine that does not have these fonts, the substitution problem occurs. Icon fonts are particularly catastrophic — a substituted icon font renders the application icons as random Latin characters, making the PDF completely confusing.</p><p>Standard system fonts — Arial, Helvetica, Times New Roman, Courier, Calibri — are present on virtually every Windows, Mac, and Linux system and every PDF viewer. Embedding them is technically unnecessary and inflates file size. However, if there is any chance the PDF will be opened in an unusual environment (an older system, a mobile PDF viewer, a government system with restricted software), embedding even standard fonts is safer than relying on system presence.</p><p>The failure mode for unembedded fonts in critical document types causes real business impact. A contract sent to a counterparty whose system uses a different default font may have different page breaks, causing signature lines to appear on different pages than intended. A court filing that relies on system font substitution may not meet formatting requirements for page length or margin specifications. A proposal sent to a client who opens it on a tablet with a PDF reader that does not include the brand font used in section headers looks unprofessional and can undermine credibility before the content is even read.</p><p>Checking font embedding takes about 10 seconds in Adobe Acrobat: File → Properties → Fonts tab. Every font in the document is listed with its encoding type and embedding status. &quot;Embedded Subset&quot; is the ideal status — the font is embedded, only the characters used in the document are included, and the file size impact is minimal. &quot;Embedded&quot; means the full font is included. Anything listed as neither — just the font name with no embedding qualifier — means it is not embedded and will substitute on systems without that font. If you discover unembedded fonts, the cleanest fix is to reopen the source document and re-export to PDF with font embedding enabled in the PDF export settings.</p>

1. 1Check font embedding status before sending important PDFsOpen the PDF in Adobe Acrobat (free or Pro). Go to File → Properties → Fonts tab. Review the list: every font should show 'Embedded Subset' or 'Embedded' in the Type column. If any font shows no embedding status, that font will substitute on systems that do not have it installed. Note which fonts are unembedded — you will need to fix them in the source document.
2. 2Re-export from source with font embedding enabledIn Word: File → Save As → PDF → Options → check 'Embed fonts in the file'. In InDesign: File → Export PDF → Advanced → Fonts → Subset fonts below 100% (this embeds all fonts used in the document as subsets). In PowerPoint: File → Options → Save → check 'Embed fonts in the file' before exporting. These settings should be verified once and set as defaults for all exports.
3. 3For received PDFs with unembedded fonts, flatten the documentIf you received a PDF with unembedded fonts and need to send it forward without substitution issues, open it in Adobe Acrobat Pro → Print → Print to PDF (using Adobe PDF printer) with 'Embed All Fonts' selected. This rasterizes the text as images, which guarantees identical rendering on all systems but makes the text non-selectable and increases file size. A better solution, when possible, is to obtain the original source file and re-export correctly.

<p>Every PDF file contains metadata — structured data about the document that is not visible in normal viewing but is accessible to anyone who knows how to look. Standard PDF metadata includes: document title, author name, application name used to create the file, creation date, modification date, and a unique document ID. PDFs created from Word or PowerPoint also inherit Office-specific metadata: the username of the last editor, the company name from the application registration, and sometimes the file's path on the creator's computer.</p><p>The privacy and confidentiality risks from unexamined metadata are real and specific. A legal firm sends a settlement proposal PDF to opposing counsel. The PDF's metadata reveals it was created by a partner at a rival firm before the company changed counsel — information that reveals the client's legal history. A company sends a price quote; the metadata shows the original filename as &quot;price-quote-inflated-for-external.docx&quot; — exposing a dual pricing strategy. A contractor sends a bid; the author name in metadata is a name that does not match the submitting company — suggesting the document was prepared elsewhere.</p><p>More commonly, metadata reveals simply that a document was edited after what was claimed to be its final version, or that the &quot;original&quot; document being presented as the authoritative version has been modified 14 times since its stated creation date. In negotiations, litigation, and procurement, metadata details can be used by sophisticated recipients. Most recipients are not sophisticated, but some are — and the ones who check metadata are usually the ones where it matters most.</p><p>Beyond privacy, metadata also causes practical problems. The document title stored in PDF metadata is what appears in browser tabs, screen reader announcements, and document management system imports. A PDF exported from a Word template called &quot;TEMPLATE — Annual Report 2019 [DRAFT]&quot; will appear with that name in every system that reads PDF metadata, regardless of what the file is named on disk. Recipients who import it into a document management system see the template name, not the meaningful document title they expect.</p><p>Removing or editing PDF metadata before sharing takes less than 2 minutes. For a complete guide on what PDF metadata contains, how to view it, and how to remove it, see our guide on <a href='/en/blog/pdf-metadata-how-to-view-edit-remove'>how to view, edit, and remove PDF metadata</a>. As a quick reference: in Acrobat, go to File → Properties → Description tab to view and edit standard metadata fields, and File → Properties → Custom to see any additional custom fields. Tools → Redact → Sanitize Document removes metadata, embedded content, scripts, and other hidden data in a single operation.</p>

<p>Images look sharp on screen at 72–96 dpi because monitors display at approximately 72–110 pixels per inch. The same image printed on paper at 72 dpi looks visibly blurry because commercial printers output at 300–600 dpi — they need 4–8 times more pixels than a screen to produce a sharp printed result at the same physical size. An image that looks perfectly crisp in a PDF viewed at 100% zoom on screen can look unacceptably blurry when printed, because the printer is forced to scale 72 dpi pixel data to fill the required print resolution.</p><p>The threshold for acceptable print quality is 250–300 dpi at the final print size. For a 4×6 inch photo in a printed brochure, this means the image needs at least 1,200×1,800 pixels (4 inches × 300 dpi × 6 inches × 300 dpi). A screenshot taken on a standard 1080p monitor is typically 72 dpi at screen size — scaled to print size, it has a print resolution of approximately 80–100 dpi, which looks extremely blurry on paper. Even Retina display screenshots at 144 dpi still fall short of the 300 dpi print minimum by a factor of 2.</p><p>The problem frequently appears in these specific workflows: presenting screenshots of software in printed training materials, including website screenshots in printed marketing reports, embedding images copied from web pages into Word documents that are then exported to PDF for printing, and using profile photos or social media images (which are typically low resolution by design to minimize web page load times) in printed directories or membership lists.</p><p>The fix is to obtain images at the correct resolution from the source — not to upscale low-resolution images. Upscaling (increasing pixel dimensions without additional real data) through Photoshop or an AI upscaling tool can improve apparent sharpness somewhat, but does not recover detail that was never captured. The correct approach is to take new screenshots at higher resolution using full-screen capture on high-DPI displays, request original high-resolution images from image sources rather than using web thumbnails, and use vector graphics (SVG, AI, EPS) for logos and diagrams, which are resolution-independent and print sharply at any size.</p><p>If a PDF is intended for both screen reading and potential printing, use 150 dpi as the compromise resolution — sharp enough for home and office printing while keeping file sizes manageable. For detailed analysis of how print quality issues manifest in PDFs, including specific fixes for different types of blurriness, see our troubleshooting guide on <a href='/en/blog/pdf-blurry-when-printed-how-to-fix'>fixing blurry PDFs when printed</a>.</p>

<p>PDF encryption is one of the most underused document security features available to every professional. Any PDF containing personally identifiable information, financial data, health information, contractual terms, employee data, or strategic business information should have a password before being emailed or shared via a file sharing platform. The operational overhead of password protection is minimal — it takes 30 seconds with the right tool — but the protection it provides against accidental forwarding, unauthorized access when email is compromised, and unintended distribution is substantial.</p><p>PDF password protection has two distinct types that serve different purposes. A <strong>document open password</strong> (user password) requires anyone opening the file to enter a password — this protects confidential documents from unauthorized access. A <strong>permissions password</strong> (owner password) restricts what authenticated users can do with the document: printing, copying text, editing, form filling, and adding annotations can all be independently enabled or disabled. Many professionals use only a document open password, not realizing they can also prevent recipients from copying the content to another document or printing without restriction.</p><p>The situations where the absence of password protection causes real harm are specific and common. An HR manager emails a salary review PDF to a manager; it gets accidentally forwarded to the entire distribution list by reply-all. A lawyer emails a draft settlement to a client; the client's email account is later compromised in a data breach, and the draft document is accessed by the opposing party. A company sends detailed pricing to a prospect; the prospect shares it with the company's competitors without authorization. In none of these cases would a password have been a perfect prevention — but it would have added a meaningful friction barrier that prevents accidental access and establishes a record of intent to protect the information.</p><p>Password strength matters significantly. A 4-digit PDF password is trivially crackable by brute force in under a minute using freely available tools. A 12+ character password with mixed case, numbers, and symbols — or a passphrase of 4+ random words — is computationally infeasible to crack with current technology. For documents requiring genuine security rather than symbolic protection, use 128-bit AES or 256-bit AES encryption (available in Acrobat and most serious PDF tools) rather than 40-bit encryption from older tools, which is crackable.</p>

1. 1Add a document open password before sharing sensitive PDFsUse LazyPDF's free protect tool at /en/protect. Upload your PDF, set a password of 12+ characters, and download the encrypted file. The tool uses 256-bit AES encryption — the same standard used by financial institutions. Send the password to the recipient through a separate channel (text message, phone call) rather than in the same email as the document.
2. 2Set permissions restrictions to prevent copying or printingIn Adobe Acrobat: File → Properties → Security → Security Method: Password Security → Permissions section. Set Printing Allowed to 'None' or 'Low Resolution' to prevent full-quality printing. Uncheck 'Enable copying of text, images, and other content' to prevent copy-paste. Enter a separate owner password. These settings restrict what authenticated users can do with the document even after they open it.
3. 3Test the password protection before sendingClose the protected PDF completely, then reopen it. Verify that the password prompt appears before the document opens. Try opening it in a different PDF viewer if possible (Chrome's built-in viewer, Firefox, Acrobat Reader) to confirm the protection is universally applied. A protection that works in Acrobat but not in browser viewers fails at the first point of contact for most recipients.

<p>Scanned PDFs are image files in a PDF container. Each page is a photograph of paper — pixels arranged to look like text, but no actual text data that software can read, search, copy, or process. A 50-page contract scanned to PDF is essentially a stack of 50 photographs. Finding a specific clause requires reading every page manually. Copying a paragraph requires retyping it by hand. Processing the document with any downstream software — a contract management system, a legal research tool, a document comparison tool — is impossible without first converting the images to text.</p><p>The scale of this problem in business workflows is significant. A lawyer searching for a specific indemnification clause in a 200-page scanned contract spends 20–30 minutes instead of 10 seconds with Ctrl+F. An accountant reconciling invoices received as scanned PDFs processes each one manually instead of using automated data extraction. A researcher trying to aggregate data across 50 scanned research papers must read each one cover-to-cover rather than running a keyword search across all 50 simultaneously.</p><p>OCR (Optical Character Recognition) converts scanned PDFs from image-only files to searchable, text-containing PDFs by reading the image pixels and producing a text layer overlaid on the original image. Modern OCR accuracy for clearly scanned printed text is 97–99% — essentially perfect for most business documents. Handwriting recognition is significantly less accurate (typically 70–85%) and requires specialized tools beyond standard OCR.</p><p>The key variables affecting OCR quality are scan resolution and image clarity. OCR works best on images scanned at 300 dpi or higher. Scans at 150 dpi produce OCR text with notably more errors. Scans with skewed alignment, low contrast (faded ink, poor original), or background patterns (colored paper, watermarks printed in the scan area) reduce accuracy further. Before running OCR, check the scan quality — a blurry or skewed scan produces more errors than no OCR at all, because confident but wrong OCR text is harder to identify than obviously missing text. For guidance on how to produce quality multi-page scans from mobile devices that produce better input for OCR, see our guide on <a href='/en/blog/scan-multiple-pages-to-pdf-mobile'>how to scan multiple pages to PDF on mobile</a>.</p>

1. 1Check whether your PDF is already searchableOpen the PDF and try to select text with your cursor. If you can highlight individual words, the PDF contains a text layer and is already searchable. If your cursor turns into a crosshair and you can only select rectangular regions rather than individual words, the PDF is image-only and needs OCR. This test takes 5 seconds and works in any PDF viewer.
2. 2Run OCR to add a text layer to scanned PDFsUse LazyPDF's OCR tool at /en/ocr. Upload the scanned PDF, and the tool extracts text from each page and creates a new PDF with a searchable text layer overlaid on the original image. The visual appearance of the document is unchanged — the original scan is preserved — but the document is now fully searchable, copy-pasteable, and processable by downstream software.
3. 3Verify OCR accuracy on critical documentsAfter OCR processing, open the PDF and run a search (Ctrl+F) for a word you can see on one of the pages. If it is found, OCR succeeded. Then copy a paragraph of text and paste it into a text editor to spot-check accuracy. For contracts and legal documents, check proper nouns, numbers, and dates — these are the areas where OCR errors most commonly cause consequential misunderstandings.

<p>PDF accessibility — the set of structural properties that make PDF documents usable by people relying on screen readers, keyboard navigation, and other assistive technologies — is the most technically involved item on this list, but it is also the one with the clearest legal and reputational stakes for organizations that publish documents publicly.</p><p>An inaccessible PDF is, from a screen reader's perspective, either completely silent (if it is a scanned image PDF) or a stream of disconnected text fragments read in the wrong order (if it is a standard untagged PDF). A multi-column layout reads across both columns word by word rather than reading the left column completely before the right column. Tables have no row or column header associations so screen reader users cannot understand the relationship between a data cell and its headers. Forms have no label associations so users cannot tell what information each field requests. Headings have no semantic identity so users cannot navigate by heading structure.</p><p>Legal requirements for PDF accessibility are now widespread and enforced. In the United States, Section 508 of the Rehabilitation Act requires federal agencies and recipients of federal funding to make electronic documents accessible — PDF/UA (ISO 14289) is the applicable technical standard. The EU Web Accessibility Directive (EN 301 549) requires similar compliance from public sector bodies across all member states. Australia's Disability Discrimination Act has been interpreted to require accessible PDFs from public sector organizations. Major enterprises routinely include accessibility compliance requirements in their vendor contracts, meaning inaccessible PDFs can create contractual liability.</p><p>Beyond legal requirements, accessibility has a practical reach beyond users with disabilities. Searchable, structured PDFs perform significantly better in PDF search indexing and in AI-extraction tools that parse documents for content. A tagged PDF with proper heading structure can be processed by document automation tools and contract analysis software more reliably than an untagged equivalent. Google indexes PDF content for search — properly tagged, structured PDFs are indexed with higher fidelity, appearing more accurately in search results. The business case for accessibility extends well beyond disability accommodation.</p><p>The most efficient approach to creating accessible PDFs is building the accessibility into the source document before export. A Word document with correctly applied heading styles, properly described images, correct table structure, and language declaration exports a PDF that is close to PDF/UA compliant. Post-hoc remediation of an unstructured PDF requires significantly more time — typically 30–90 minutes per document for complex files compared to 5–15 minutes of upfront structure in the source document. For a complete checklist of accessibility requirements and how to verify them, see our guide on the <a href='/en/blog/pdf-accessibility-checklist-2026'>PDF accessibility checklist for 2026 compliance</a>. If your organization publishes PDFs for public consumption, investing in accessible source document templates pays for itself the first time you avoid a compliance complaint or an accessibility audit finding.</p>