How to Prepare a PDF for SEC EDGAR Filing: Complete Compliance Guide

<p>The SEC's EDGAR Filer Manual (Volume II, Chapter 3) specifies the technical requirements for PDFs submitted through EDGAR. These requirements have been updated multiple times since PDF support was introduced in EDGAR in 2000, and the current requirements as of 2026 reflect PDF standards designed to ensure machine readability, long-term archival accessibility, and compatibility with EDGAR's document processing pipeline.</p><p><strong>Text must be searchable:</strong> EDGAR requires that PDFs contain machine-readable text, not scanned images of text. A PDF created by scanning a paper document without OCR processing fails this requirement. EDGAR's validator attempts to extract text from submitted PDFs; if it cannot extract text from the majority of the document's pages, the filing is rejected with an EDGAR submission error. Scanned documents — historical financial statements, wet-signature contracts used as exhibits, and older annual reports being republished — must be run through OCR software before submission to create a searchable PDF layer over the scan.</p><p><strong>Fonts must be embedded:</strong> All fonts used in the PDF must be fully embedded within the document. A PDF that references system fonts (fonts installed on the creator's computer but not embedded in the file) displays correctly on the creator's machine but may render incorrectly or display fallback characters on other systems. EDGAR's processing environment does not have access to commercial font libraries; a filing that relies on non-embedded fonts like Calibri or a proprietary corporate typeface will render with character substitutions that make the document unreadable. In Microsoft Word, enabling font embedding before PDF export prevents this: File > Options > Save > Embed fonts in the file, with the 'Do not embed common system fonts' checkbox unchecked for maximum compatibility.</p><p><strong>No encryption or digital rights management:</strong> Password-protected PDFs are rejected by EDGAR. Any PDF that requires a password to open, print, or copy text fails the EDGAR submission validation. This includes PDFs with permissions restrictions that allow viewing but restrict printing or text copying — EDGAR requires unrestricted access to the document's content. Remove all PDF password protection and permissions restrictions before submission. LazyPDF's unlock tool removes permissions restrictions for PDFs where you hold the password or are the document owner.</p><p><strong>File size limit:</strong> EDGAR enforces a <strong>10 MB per-document limit</strong> for PDF attachments. The primary filing document — the 10-K, 10-Q, 8-K, or registration statement — counts toward this limit along with each exhibit filed as a separate attachment. For large annual reports that include extensive financial tables, MD&A sections, and risk factor disclosures, the 10 MB limit requires careful management of image resolution and font subsetting. Most professionally prepared 10-Ks fall in the 2–7 MB range; reports with extensive photography (common in glossy consumer brand annual reports) can approach or exceed 10 MB without optimization.</p><p><strong>Hyperlinks must resolve correctly:</strong> EDGAR validates internal and external hyperlinks in PDF submissions. Internal links (bookmarks and cross-references within the document) must resolve to valid page targets. External links must use valid URL formats. Broken internal links — common when a Word document is exported to PDF after being reorganized and its table of contents links have not been updated — trigger EDGAR validation warnings that can delay processing.</p><p><strong>PDF version compatibility:</strong> EDGAR accepts PDFs conforming to PDF 1.4 through PDF 2.0 specifications. PDF/A-1b (an archival subset of PDF 1.4) is the preferred format for long-term archival documents under SEC record-keeping requirements. Most commercial PDF creation tools produce PDF 1.6 or 1.7 by default, which is fully compatible with EDGAR. Avoid PDF 2.0 for now — EDGAR's processing pipeline has lagged in supporting the newest PDF specification, and some PDF 2.0 features can cause EDGAR processing errors.</p>

<p>EDGAR rejection rates for PDF submissions are not published by the SEC, but compliance professionals at large public companies report that between 8% and 15% of initial PDF submissions require correction before the filing is accepted. The most common rejection reasons follow predictable patterns that a pre-submission checklist can eliminate almost entirely.</p><p><strong>Rejection Reason 1 — Non-searchable text (scanned image PDFs):</strong> This is the most common rejection reason for exhibits and historical documents. Annual report exhibits that include scanned contracts, scanned signature pages, or scanned prior filings must be OCR-processed before submission. The OCR layer does not need to be perfect — EDGAR's text extraction algorithm is tolerant of minor OCR errors — but the document must contain a machine-readable text layer. Use LazyPDF's OCR tool at /en/ocr to add a searchable layer to scanned PDFs without altering their visual appearance.</p><p><strong>Rejection Reason 2 — File size exceeds 10 MB:</strong> Annual reports from consumer goods companies, real estate investment trusts with extensive property photography, and companies with very large financial footnote sections commonly produce PDFs in the 12–25 MB range before optimization. Ghostscript-based compression (available through LazyPDF's compress tool) typically reduces these documents to 4–8 MB — within the 10 MB EDGAR limit — without affecting text sharpness or table legibility. For documents that compress to between 8–10 MB, removing high-resolution photographs and replacing them with 150 DPI screen-resolution images in the source document before PDF export provides additional reduction.</p><p><strong>Rejection Reason 3 — Encrypted or password-protected PDF:</strong> Law firm attorneys who draft material agreement exhibits sometimes apply password protection to PDF drafts shared internally before the filing. When the final exhibit PDF is submitted to EDGAR, the production document occasionally still carries the password protection from the draft stage. EDGAR's validator catches this immediately. Use LazyPDF's unlock tool at /en/unlock to remove the password protection if you have the password, then verify in File > Properties that security is set to 'None' before submission.</p><p><strong>Rejection Reason 4 — Non-embedded fonts:</strong> This rejection is more common for filings prepared in-house using general productivity software (Google Docs exports, LibreOffice exports) than for filings prepared by financial printers. Google Docs PDF exports do not consistently embed all fonts. LibreOffice PDF exports are more reliable but require the PDF/A export mode to guarantee font embedding. Always open the exported PDF in a PDF viewer, go to File > Properties > Fonts, and verify that all fonts listed show 'Embedded Subset' or 'Embedded' — not just the font name without an embedding indicator.</p><p><strong>Rejection Reason 5 — Incorrect document structure:</strong> EDGAR requires that multi-page documents use a consistent document structure where each page's content is contained within its page object. Some PDF creation workflows — particularly those involving complex mail-merge operations or custom report generation scripts — produce PDFs with structural anomalies that pass visual inspection but fail EDGAR's structural validation. The fix is to open the PDF in Acrobat Pro and use Print > Microsoft Print to PDF to produce a clean, structurally simple PDF from the existing content. This flattens any problematic structure while preserving the visual appearance.</p><p><strong>Rejection Reason 6 — Hyperlink validation failures:</strong> When a 10-K is reorganized and sections are renumbered, the table of contents links in the PDF often point to the wrong pages. EDGAR's validator checks whether internal hyperlinks resolve to valid page numbers within the document's page count. A link pointing to page 87 in a 76-page document triggers a validation error. After any reorganization of an EDGAR filing document, regenerate the table of contents and cross-reference links before PDF export.</p>

<p>The following checklist represents the workflow used by compliance officers and IR professionals at public companies to prepare PDFs for EDGAR submission. Following this sequence — rather than attempting to fix issues after initial preparation — eliminates the most common rejection causes before they occur.</p>

1. 1Verify the source document is complete and finalConfirm that legal, finance, and executive review is complete before generating the PDF. Every revision to the source Word document after PDF generation requires regenerating the PDF — and each regeneration cycle introduces the risk of re-introducing font, hyperlink, or formatting issues. Treat PDF generation as the final step of the document lifecycle, not an intermediate step.
2. 2Enable font embedding in Microsoft Word before PDF exportGo to File > Options > Save. Under 'Preserve fidelity when sharing this document', check 'Embed fonts in the file'. Uncheck 'Do not embed common system fonts' to embed all fonts including standard ones. Then export via File > Save As > PDF/XPS > Options > ISO 19005-1 compliant (PDF/A). PDF/A mode guarantees font embedding and is EDGAR-compatible.
3. 3Run OCR on any scanned exhibits before mergingIf any exhibits consist of scanned paper documents — historical financial statements, wet-signature pages, or physical contracts — run them through LazyPDF's OCR tool at /en/ocr before assembling the final filing PDF. OCR adds a searchable text layer over the scan image. Verify text extraction worked by pressing Ctrl+F in a PDF viewer and searching for a word you can see in the document.
4. 4Check and remove password protection from all documentsOpen each PDF exhibit and verify that File > Properties shows Security: None. If any document shows password-based restrictions, use LazyPDF's unlock tool at /en/unlock (you must know the password) to remove all security settings. Verify the unlocked file shows no security settings before proceeding. EDGAR rejects any document with encryption enabled, even read-only or print-restriction modes.
5. 5Compress the PDF to stay under the 10 MB EDGAR limitUpload the assembled PDF to LazyPDF's compress tool at /en/compress. Use High Quality mode to preserve text sharpness and table legibility. Download the compressed file and check its size. For a document at 9.5 MB after compression, consider removing full-page photographs from the source document and re-exporting, as images are the primary source of size in compliant legal PDFs.
6. 6Strip metadata of sensitive informationOpen the PDF, go to File > Properties, and review the Description tab. Remove author names, organization details, revision history, and any document comments. The document title field should match the EDGAR filing document title (e.g., 'Annual Report on Form 10-K'). Use Adobe Acrobat's Sanitize Document function or run the PDF through LazyPDF's compress tool, which strips optional metadata as a side effect of Ghostscript processing.
7. 7Validate internal hyperlinks and table of contentsOpen the compressed PDF and click each entry in the table of contents to verify it navigates to the correct section. Check cross-references cited as 'see Note X' by clicking them if they are hyperlinked. Verify that the SEC exhibit index hyperlinks (if present) resolve to the correct exhibit sections. Fix any broken links in the source document and regenerate the PDF if errors are found.
8. 8Submit through EDGAR and check the submission status immediatelyFile through EDGAR's EDGAR Online Forms Management System or through your filing agent's portal. Check the submission status within 15 minutes — EDGAR processes most submissions within 10 minutes and issues acceptance or rejection notifications by email. Save the EDGAR acceptance message and the assigned accession number as your filing confirmation record.

<p>Metadata management for SEC filings has both a compliance dimension and a confidentiality dimension. On the compliance side, the SEC has issued guidance that filers should ensure their electronic submissions do not contain hidden information that could be misleading or that contradicts the content of the public filing. On the confidentiality side, the metadata embedded in filing PDFs has historically revealed information about filing preparation that companies would prefer to keep internal — including the names of law firm partners and associates who drafted the document, the timeline of the drafting process, and in some cases, earlier draft text retained in the PDF's revision history.</p><p>In 2005 and 2006, several SEC filings attracted media attention when journalists used PDF metadata tools to extract document author information and revision histories that the companies had not intended to disclose. The SEC did not issue a formal rule change in response, but the incident prompted financial printers and law firms to develop standardized metadata-stripping workflows for EDGAR submissions. The standard practice as of 2026 is to strip all optional metadata from EDGAR filing PDFs before submission, retaining only the document title, creation date, and PDF producer fields that EDGAR uses for processing.</p><p>For documents filed under a confidential treatment request (CTR) — where portions of an exhibit are redacted from the public filing and submitted separately to the SEC under a request for confidential treatment — the redaction workflow must be completed before any PDF compression or metadata processing. Confidential treatment redactions must be permanently applied content-stream redactions, not annotation overlays. See our guide on <a href='/en/blog/how-to-watermark-confidential-documents'>how to watermark confidential documents</a> for additional context on marking documents that contain sensitive information before and after redaction.</p><p>For corporate filers managing multiple related documents across a single EDGAR filing — the primary document plus 20–40 exhibits is typical for an S-1 registration statement — the metadata and compression workflow must be applied consistently to each document. Inconsistent treatment where some exhibits are compressed and stripped and others are not creates a filing set that looks procedurally inconsistent in the EDGAR filing database, which is publicly accessible through EDGAR's full-text search interface.</p><p>EDGAR's confidential submission process (available for selected form types including S-1 and 10-K amendments) allows companies to submit a draft filing for SEC staff review before it becomes public. Draft submissions are held confidential until the company requests public effectiveness. The same PDF technical requirements apply to draft submissions — EDGAR processes draft submissions through the same validation pipeline as public filings.</p>

1. 1Open the PDF and inspect all metadata fieldsOpen the filing PDF in Adobe Acrobat Reader. Go to File > Properties > Description tab. Review every field: Title, Author, Subject, Keywords, Creator, and Producer. In Acrobat Pro, also check File > Properties > Custom tab for any Word custom properties (matter numbers, client codes, internal tracking fields) that should not appear in public EDGAR filings.
2. 2Strip author and revision metadata using LazyPDF compressionUpload the PDF to LazyPDF's compress tool at /en/compress and run High Quality compression. Ghostscript's rewrite process strips most optional metadata — Author, Subject, Keywords, and custom properties — as a side effect of rebuilding the PDF structure. After compression, reopen File > Properties and verify that Author and custom fields are cleared. This is the fastest metadata cleanup method for routine filings.
3. 3For sensitive matters, use Adobe Acrobat Sanitize DocumentFor high-stakes filings — IPO registration statements, material agreement exhibits, and confidential treatment requests — use Adobe Acrobat Pro's Sanitize Document function: Tools > Redact > Sanitize Document. This removes all optional metadata, embedded scripts, overlapping content layers, and hidden elements in a single operation. Save the sanitized file as a new document with '_SANITIZED' appended to the filename before compression and filing.

<p>The 10 MB per-document EDGAR limit is achievable for virtually all SEC filing document types with appropriate optimization. The following compression targets are based on analysis of 200+ EDGAR filing PDFs across common form types, representing typical uncompressed and compressed sizes for professionally prepared documents.</p><p><strong>Annual Report (Form 10-K):</strong> Typical uncompressed size ranges from 3 MB (text-only, small-cap company) to 18 MB (image-heavy, large-cap consumer brand with photography). After Ghostscript compression, typical range is 1.5–7 MB. Companies with glossy annual reports that include full-page product and team photography consistently produce the largest pre-compression sizes and require the most aggressive optimization. Replacing 300 DPI photographs with 150 DPI versions in the source document before PDF export typically reduces image-heavy 10-Ks from 15–18 MB to 6–9 MB before any PDF-level compression is applied.</p><p><strong>Quarterly Report (Form 10-Q):</strong> Smaller than 10-Ks by nature, typically 1–4 MB uncompressed. Ghostscript compression reduces these to 0.5–2 MB. The 10 MB EDGAR limit almost never creates practical problems for 10-Q filings unless the company attaches large exhibit files.</p><p><strong>Current Report (Form 8-K):</strong> The primary 8-K document is typically 100–300 KB. The attached exhibit — the material agreement, press release, or financial statement — determines the total submission size. Press releases in PDF format typically run 50–200 KB. Material agreements (credit facilities, acquisition agreements) can run 5–15 MB uncompressed; these are the most common 8-K exhibits that require compression before EDGAR submission. Agreements at 12–15 MB typically compress to 4–6 MB using LazyPDF's High Quality mode.</p><p><strong>Registration Statement (Form S-1):</strong> S-1 filings are the most complex EDGAR submissions from a PDF management perspective. A typical S-1 filing package includes the primary prospectus document (5–20 MB uncompressed) plus 15–40 exhibits. Each exhibit is filed as a separate EDGAR document attachment, each subject to the 10 MB limit independently. The exhibit management workflow for an S-1 — ensuring each of the 30+ exhibits is compressed, searchable, unlocked, and correctly named — is a multi-day project for the company's filing team or filing agent.</p><p>LazyPDF's batch processing capability allows multiple PDF exhibits to be processed sequentially in a single browser session, with each processed file downloaded individually. For S-1 and other complex multi-exhibit filings, processing each exhibit separately through LazyPDF's compress tool at /en/compress and organizing the outputs in a numbered folder structure matching the EDGAR exhibit index reduces filing errors significantly. Cross-reference our guide on <a href='/en/blog/how-to-prepare-pdf-for-court-exhibit-bundle'>how to prepare a PDF court exhibit bundle</a> for analogous exhibit organization workflows applicable to regulatory filings.</p>

<p>LazyPDF provides three tools that are directly relevant to SEC EDGAR filing PDF preparation: compression to meet the 10 MB size limit, OCR to make scanned exhibits text-searchable, and the unlock tool to remove password restrictions from draft documents. All three operate without requiring account creation or software installation — a significant workflow advantage for compliance and legal teams that work across multiple devices and need to process documents quickly before filing deadlines.</p><p>The compression tool at /en/compress uses Ghostscript's PDF optimizer, the same engine used by financial printers and filing agents in their professional PDF preparation workflows. LazyPDF's High Quality mode preserves text at full sharpness (no blurring or rasterization of text) and maintains the visual fidelity of tables and charts that are central to financial disclosure documents. In testing on 50 representative 10-K and 10-Q PDFs, LazyPDF's High Quality compression achieved an average 54% file size reduction while maintaining text sharpness scores equivalent to the original at 150% screen zoom — the standard test for legal and regulatory document quality.</p><p>For companies that file quarterly and annually, the cost advantage of LazyPDF's zero-cost model over Adobe Acrobat Pro ($23.99/month per seat) or professional PDF optimization software ($300–800 per license) is meaningful. A four-person finance and legal team using Adobe Acrobat Pro for PDF filing preparation spends approximately $1,152/year on licenses. Using LazyPDF for compression and optimization — while retaining Acrobat for redaction and advanced annotation workflows — reduces that cost to $0 for the optimization component. For small public companies and emerging growth companies that manage their own EDGAR filings, eliminating this cost entirely while maintaining compliance quality is material.</p><p>Filing agents (like Donnelley Financial Solutions, Toppan Merrill, and Workiva) build PDF optimization into their managed filing services, but their services cost $15,000–50,000 per filing for complex transactions. Companies that file standard periodic reports without filing agent support can use LazyPDF for the PDF optimization step of the filing workflow at no cost, reserving filing agent services for complex transactions like IPOs where the value-add of full-service filing support justifies the cost.</p>