Flattening a PDF form writes the current visible value of every traditional AcroForm field — text boxes, checkboxes, radio buttons, dropdowns, and list boxes — directly into the page content and removes the interactive field, so the value becomes part of the page instead of a still-editable control. To flatten PDF multiple files at once, run each completed form through the browser-based Flatten PDF tool in sequence; the tool processes one file per pass, but each pass is local, takes only as long as the browser needs to read the AcroForm dictionary and rewrite the page, and leaves your original file untouched on your device. Because the work happens in your browser using pdf-lib's form-flatten operation, there is no upload queue and no server copy of your paperwork sitting in transit. Processing a stack of completed forms is therefore a matter of repeating the same three clicks for each file, which in practice is the closest a privacy-first, browser-based workflow can get to a true one-click batch. The rest of this article walks through what flattening actually changes, why so many real workflows end up needing it for more than one PDF, the exact steps to repeat, and the limits to keep in mind before you send the finished copies anywhere.
What flattening actually does to a PDF
When a recipient, printer, or archive opens a traditional fillable PDF, the viewer reads an AcroForm dictionary that lists the fields and their current values. As long as that dictionary is intact, the viewer also offers an editing cursor, a checkmark toggle, or a dropdown picker on top of the page. Flattening rewrites that situation by walking every AcroForm field, painting its current appearance into the underlying page content stream, and then dropping the interactive field from the dictionary. The downloaded PDF still looks the same on screen, but the values are now ordinary painted glyphs and shapes rather than data bound to a control.
This matters for three practical reasons. First, a flattened copy prints consistently because viewers no longer need to interpret a field's state at print time. Second, sharing a flattened copy prevents accidental edits in transit, since there are no fields left to type into. Third, a flattened copy sidesteps font and appearance differences between PDF viewers, because the text has already been placed on the page using the appearance the original viewer recorded.
When you need to flatten multiple PDF files
Almost every fillable form in a real workflow arrives in batches rather than one at a time. Hiring packets, vendor onboarding forms, patient intake sheets, school enrollment documents, tax organizers, and event registrations all tend to come back filled out across an entire team or customer base. Once the values are final, the person collecting those forms usually needs a read-only version of each one for archiving, audit, or print — not a stack of still-editable PDFs that could be quietly altered after submission.
The same situation shows up when you are preparing paperwork for a printer or a downstream system that does not handle AcroForm fields gracefully. A print shop may flatten forms automatically for you, but a small office printer, a records-management system, or a simpler PDF viewer often will not. Sending flattened copies removes the guesswork. The receiver gets a finished document that looks like the one you reviewed, with the same typed values, the same checkmarks, and the same dropdown selection locked into the page.
The honest batch workflow in your browser
The Flatten PDF tool processes one file at a time, so a true multi-file run is a short loop of the same three actions repeated inside the browser. There is no upload step in between and no queue to configure. Open the tool, run the first PDF, save the flattened result, then run the next one. The whole loop runs against files already sitting on your device, so the time per file is mostly the time the browser needs to load the PDF, walk the AcroForm dictionary, repaint the values into the page content, and serialize the result.
- Choose the PDF containing completed traditional form fields from your device.
- Review the detected editable field count and confirm the visible values are final.
- Select Flatten PDF form fields, then download the new flattened copy.
- Move that downloaded copy into a clearly named "flattened" folder on your device.
- Repeat steps 1–4 with the next completed PDF in your batch until every file is processed.
For a stack of typical intake or application forms, this loop is fast enough that the bottleneck is usually opening and saving files in your file manager, not the conversion itself. A simple naming convention helps a lot when the batch is large: rename each flattened copy with a clear suffix such as "_flattened" before moving on, so you never confuse the editable original with the read-only deliverable later. The original file is never modified by the tool, so you can always re-run the same PDF if you spot a typo in your values, but it is much easier to keep the two streams of files visually separated from the start.
What the tool flattens, and what it deliberately leaves alone
The tool is narrow on purpose. It targets the interactive controls known as AcroForm fields and nothing else, so the result you get depends entirely on what kind of PDF you feed it. The table below summarizes the four cases you are most likely to meet while working through a batch.
| PDF type | Field count found | Outcome |
|---|---|---|
| Traditional fillable form with completed values | One or more AcroForm fields | Flattened copy downloaded; original file on your device is unchanged |
| Scanned image-based PDF or static document | Zero | No output file produced; the tool refuses rather than generating a look-alike |
| XFA dynamic form | Not supported | Stopped safely; no flattened copy generated |
| Password-protected or damaged PDF | Not processed | Rejected safely; protection is never bypassed |
If the tool reports zero fields, that message is meaningful: the file is either a scan, a static document, or a PDF whose values are already baked into page content, so there is nothing left for the tool to flatten. Producing a download in that case would be misleading, which is why the tool deliberately does not generate one. For a deeper walkthrough of preserving appearance across many viewers, the guide on flattening a PDF without losing quality covers the same field-handling logic in more depth.
What flattening does not do
It is worth being specific about what the tool does not change, because several of these limits are easy to confuse with the flattening step itself, especially when you are processing many files at once and trying to remember which copy was flattened for which reason.
- It does not add a password or otherwise encrypt the flattened PDF.
- It does not redact text that was already present on the page beneath a field, nor does it erase metadata, attachments, or hidden layers.
- It does not turn a typed name or a checked box into a cryptographic digital signature; it only preserves the visible value on the page.
- It does not convert the PDF into an image, certify the document, or handle XFA dynamic forms.
If any of those jobs are also on your list — redaction, certification, password removal, or signing — handle them with a dedicated tool before or after flattening rather than expecting the flatten pass to cover them. Flattening changes editability, not the underlying purpose or security state of the document.
Quick checklist before sending flattened copies
Before you ship a stack of flattened PDFs to a recipient, printer, or archive, a short verification loop saves a lot of back-and-forth later. The four checks below only take a few seconds per file and they catch the rendering surprises that cause the most reprint and resend requests.
| Check | Why it matters |
|---|---|
| Open each downloaded copy in the viewer your recipient uses | Fonts, scripts, and appearance settings can render differently across viewers even before flattening |
| Confirm values look final and complete on the page | Flattening is a one-way change for that copy; editing later requires the original PDF |
| Keep the original editable PDF until the recipient confirms acceptance | The tool never overwrites your source file, but it also cannot unflatten a download |
| Use a separate signed-process workflow for regulated paperwork | A visible signature on a flattened page is preserved on the page but is not a cryptographic signature |
Once each copy passes those four checks, you can rename and ship the entire batch with confidence that the values the recipient sees are the values that were entered, and that no stray cursor can quietly change them on the way through. Keep the editable originals in a separate folder from the flattened deliverables, and the next round of forms in your workflow will be a repeat of the same quick loop rather than a fresh puzzle.
Related reading: Flatten a PDF Offline in Your Browser.