Why Combining Filled PDF Forms Changes the Answers (or Drops the Fields)
You have a stack of filled-in copies of the same PDF form: daily field sheets, W-9s, applications, inspection checklists. You combine them into one file, and one of two things happens. Every copy now shows the first person's answers, and typing into one box changes the same box on every page. Or the merged file looks right, but nothing in it can be filled in or corrected anymore. Both come from how PDF forms are built. Once you see the structure, the fix for each is simple.
A form field isn't the box you see
A PDF form has two layers. The fields live at the document level, in one list (the AcroForm) that belongs to the whole file. Each field has a name, such as applicant.name or Date, and one value. The widgets are the boxes on the pages, and each one points back to the field it displays. A single field can have several widgets. That's deliberate: it's how a form shows your name in the header of every page while you type it once.
Within one document, the field's name is its identity. Two widgets that belong to fields with the same fully qualified name are, as far as PDF viewers are concerned, two views of the same field with the same value.
Why every copy shows the same answers
Ten filled copies of one form contain ten fields that are all called applicant.name, one in each file. While they are separate files, that's fine. Combine them while keeping the form, which is what Acrobat's Combine Files and most libraries' "append" do, and the merged document has one name with ten widgets. A name can only hold one value, so one copy's answer wins and appears in all ten places. Usually it's the first file's answer, though that depends on the tool. Typing into any of them updates all of them.
That's why the problem only appears with copies of the same form, and why combining a form with an unrelated document works fine. It's also why Acrobat's community forums have threads going back to at least 2014 with titles like "Combining PDFs with the same form field names", one of them with over 6,000 views. The usual accepted answer is to flatten first.
Why the merged file looks filled but isn't a form anymore
The opposite failure comes from tools that copy pages. Pages carry their widgets, and each widget carries a picture of what was typed (its appearance), so the merged file looks completely filled in. The document-level list of fields stays behind, though, because it isn't part of any page. The result is boxes with old answers drawn in them that belong to no form. Depending on the viewer, they can't be clicked at all, or they behave strangely when edited, or a viewer that redraws forms shows them empty. Many lightweight mergers and page-copy functions in PDF libraries work this way.
How to combine them correctly
It depends on what the merged file is for:
- For submitting or archiving: flatten each copy first. Flattening draws every answer into the page as ordinary content and removes the fields. Nothing can collide or change afterwards, and the file looks the same in every viewer. In Acrobat Pro, this is a
this.flattenPages()action, or printing to PDF, which also flattens. Flattening is irreversible, so keep the originals. - For files someone still has to review or correct: rename the fields per copy. If each file's fields get a unique prefix (
alice_applicant.name,bob_applicant.name), nothing is shared and everything stays fillable. Doing this by hand in Acrobat's Prepare Form is impractical for dozens of fields across dozens of files. It has to be automated. - When you actually want one answer everywhere (one company name filled into every copy, say), keep the shared names. That's the default behavior.
FreeToolDev's PDF form merger does the first two in the browser. Drop in the filled copies and it lists every field name that appears in more than one file, which is exactly what would collide. Then it merges with each file's fields renamed after the file name, or with everything flattened. Nothing is uploaded, which matters when the forms contain tax IDs or medical details. The PDF merge & compress tool now keeps form fields fillable and separate per file as well.
Three cases that behave differently
- Digitally signed forms. Merging creates a new document, so a signature from a source file won't verify in the combined file. Keep the signed originals as the record, and merge only for reading.
- XFA forms (made with Adobe LiveCycle or Designer; they often show "Please wait…" outside Acrobat). Most of them also contain an ordinary form layer, and that's what most tools keep. Purely dynamic XFA forms don't. Print those to PDF from Adobe Reader first, then merge the printed copies.
- Forms filled in a lightweight viewer. Some apps save a field's value without updating its appearance (the picture of the answer that the page shows). If a merged copy shows a box as empty when the original showed text, open the original in a full PDF reader, save it once, and merge again, or flatten it.
If the merged file has a different problem, such as one page much bigger than the rest or the file being larger than expected, see why a merged PDF is bigger (or smaller) than the originals.