On this page
Values and appearance streams
A form field can store a value while also carrying an appearance stream that tells viewers how it should look. Some viewers regenerate appearances; others rely on the stored version.
Updating appearances immediately before flattening reduces the chance that text, checks or selections disappear.
Different controls render differently
Text fields require font, size and boundary handling. Checkboxes and radio groups use defined on-states, while dropdowns display a selected option.
Unsupported field technologies such as XFA require a different workflow.
Visual review remains necessary
Structural verification can prove that fields were removed, but it cannot judge clipping, font substitution or an incorrect selected value.
Review representative pages at useful zoom and test the intended viewer for important submissions.
Put the workflow into practice
Arrange source documents, select the pages you need, and create one PDF locally in your browser. Review the result before choosing any optional next step.
Try Merge PDFFrequently asked questions
Clear answers before you merge
What is a field appearance?
It is the visual representation of a stored form value.
Why can one viewer show a different value?
Viewers may regenerate or interpret field appearances differently.
Are signatures preserved?
Visual signature fields may flatten, but cryptographic signature validity requires separate care.
Is structural verification enough?
No. Also inspect the visible output.
