To flatten a PDF using Preflight logic in your browser, choose the form-filled PDF, confirm the AcroForm field count the tool detects, and download the flattened copy where every field's current value is baked into the page and can no longer be edited. Adobe Acrobat's Preflight tool can reach the same end state through its fixup profiles, but a desktop application is not required for the common case of standard AcroForm forms: a browser-based Flatten PDF tool inspects the form, shows how many editable fields it found, and writes the current values into the page on your own device. The whole job runs locally, so the original PDF never leaves your computer and the source file on disk is never modified. This article walks through what Preflight-style flattening actually changes inside a PDF, how to run the job in your browser, what the tool will and will not touch, and when the full Acrobat Preflight panel is still the right choice for the job at hand.
Most people land on the phrase "Preflight" because Adobe bundles a long list of pre-press checks and fixups under that name. Flattening form fields is just one of those fixups, and it is the same operation whether you trigger it through Preflight, through the Prepare Form toolbar, or through a small standalone utility that targets only the form fields. The visible result is identical: a page that looks the same, with no way to click back into a field and change what was entered.
What PDF Preflight Flattening Actually Does
A traditional PDF form is a layered object. The page has a static visual layer — the form background, the labels, the lines where text should appear — and on top of that sits an interactive layer built from AcroForm fields: text boxes, checkboxes, radio buttons, dropdowns, and list boxes. Each field carries its own current value plus a default appearance, and any PDF viewer can re-render that appearance when the field is opened, tabbed into, or printed.
Flattening is the operation that merges those two layers for the current state of the form. The tool reads each AcroForm field, copies its current visible appearance into the page content stream as ordinary page text or graphics, and then removes the field object itself. After that, no viewer can find the field to edit it, and no renderer has to interpret field state when it draws the page. This is how the underlying library used by the browser tool is documented: the library's PDFForm API exposes a flatten operation that writes each field's appearance into the page and clears the interactive form dictionary.
Three things follow from that definition, and they are worth keeping straight before you flatten anything:
- The current value is preserved as drawn text or graphics, not as live data. A typed name becomes glyphs on the page.
- The field's editability disappears in the output copy only. The original PDF on your disk is untouched.
- Nothing underneath the field is removed. Hidden layers, document metadata, attachments, and any text that already existed beneath the field all survive the operation.
How to Use Preflight Logic to Flatten a PDF in Your Browser
The browser workflow mirrors what Adobe Preflight does for the form-fields fixup, with a much shorter checklist. Open the Flatten PDF tool, then follow these steps:
- Choose the PDF containing completed traditional form fields. Use the file picker or drag the saved form onto the page. The file is read locally in your browser tab; nothing is uploaded to a server.
- Review the detected editable field count and confirm the visible values are final. The tool inspects the AcroForm dictionary and reports how many standard form fields it found. If the count is zero — because the file is a scan, a static document, or an already-flattened form — the tool stops here and produces no output, rather than generating a misleading duplicate.
- Select Flatten PDF form fields, then download the new flattened copy. The browser writes each field's current appearance into the page and removes the interactive fields. A new PDF downloads; the original file is unchanged on your device.
- Open the downloaded copy in the PDF viewer your recipient uses. Spot-check a text field, a checkbox or radio button, and a dropdown or list box. Confirm that the rendered values match what you intended to send.
That last step matters because viewers can disagree on how a field's appearance was drawn in the source PDF. Fonts, complex scripts, and viewer-specific appearance settings can render differently across Acrobat, browser-based viewers, and mobile readers even before flattening touches the file. The browser tool does not change fonts or rewrite appearance streams; it only writes what was already visible. If you see drift between what you saw in your authoring tool and what the flattened page shows, fix the source first, then flatten again.
What the Browser Tool Flattens and What It Leaves Alone
Because the tool inspects the AcroForm dictionary before doing anything, you can predict its behavior from the type of PDF you hand it. The table below summarizes what is flattened, what is preserved untouched, and what causes the tool to refuse the file.
| PDF content | What the browser tool does |
|---|---|
| AcroForm fields: text boxes, checkboxes, radio buttons, dropdowns, list boxes | Current visible values are written into the page and the interactive fields are removed from the output copy. |
| Scans, image-only PDFs, or static forms with no AcroForm fields | No output file is produced; the tool refuses to create a duplicate that pretends to be flattened. |
| XFA (dynamic XML) forms | Rejected safely; XFA needs a dedicated, compatible workflow. |
| Password-protected or encrypted PDFs | Rejected safely; the tool does not attempt to bypass protection. |
| Page text, annotations, metadata, attachments, hidden layers, text already present under a field | Preserved as-is in the flattened output copy. |
| Original PDF on your device | Never modified; only a separate flattened copy is downloaded. |
A second way to read this table: flattening changes one specific property of the file — the editability of traditional form fields — and leaves everything else alone. If you also need to remove sensitive content, password-protect the file, certify signatures, or convert pages to images, those are separate jobs with their own dedicated PDF tools.
When to Reach for Preflight in Acrobat Instead
Adobe Preflight is a panel with dozens of checks and fixups, and flattening form fields is only one entry on a long list. If your workflow needs any of the things outside that narrow lane, stay in Acrobat:
- Complex pre-press fixes. Preflight can resample images, convert color spaces, fix transparency, embed fonts, and apply a PDF/X or PDF/A profile in a single pass. The browser flattening tool does none of that.
- XFA forms. Acrobat can flatten some XFA forms because it understands the dynamic form format. The browser tool deliberately refuses XFA files rather than producing an unreliable result.
- Profiles and batch runs. Preflight lets you save a fixup profile and apply it to hundreds of files in a hot folder. A browser tool processes one file at a time.
- Audit and reporting. Preflight produces detailed pre-flight reports listing every check and its result. The browser tool reports only the editable field count.
For everything inside that narrow lane — a single PDF with completed standard AcroForm fields that needs to be locked and shared — the browser workflow is faster, requires no install, and never sends the file off your machine. If you want a deeper walkthrough of that path, the how-to on converting a fillable PDF into a flat file covers the same tool with additional framing for that specific reader task.
Checking the Flattened Result Before Sending
Two habits catch most flattening mistakes before they reach a recipient. First, keep the original editable form on your device until the recipient confirms the flattened copy is acceptable — the tool only ever writes a separate output, so the source file is your safety net. Second, open the downloaded copy in the same viewer your recipient will use, not just in the one you filled the form in. Acrobat, Preview, browser-based viewers, and mobile readers can show different glyphs for the same field, and flattening bakes whatever the source drew onto the page.
Also remember that flattening is not a signing step. A visible typed name or a checked approval box is preserved on the page, but it does not become a cryptographic digital signature, and flattening does not erase the document's revision history, metadata, attachments, or hidden layers. For high-stakes paperwork — regulated filings, signed contracts, anything that has to pass an authenticity check — combine flattening with the appropriate signing, certification, or redaction workflow for that job. For a printed application, an archive copy, or a record where you simply do not want anyone to keep editing the answers, the browser Flatten PDF step on its own is enough.