What flattening a PDF form changes

PDF form values live outside the ordinary page content

Under the hood, a fillable PDF form is built on what the PDF spec calls an AcroForm: a list of field objects (text fields, checkboxes, radio buttons, dropdowns) that each carry a current value and a set of coordinates telling a PDF viewer where to draw an editable widget on top of the page. The page's actual content stream, the text and graphics that were there before anyone filled anything in, is untouched by filling in a field. The value lives in the field object, not on the page itself, which is exactly why a viewer can still let you edit it after you've saved.

Flattening writes appearances onto the page

A PDF flattening library takes each supported field’s current appearance, draws that representation into the page content and removes its field widget. The exported copy should retain the visible answers while no longer offering those controls for editing. Appearance streams, fonts, unsupported field types and viewer behavior can complicate the result, so compare every completed field rather than assuming pixel-for-pixel identity.

Why the original fields cannot simply be restored

Once a field's value is merged into the page's content stream, there's no metadata left connecting that drawn text back to "this used to be an editable field called email." A PDF's content stream is just drawing instructions, lines, text positions, fonts, with no concept of "this text used to be interactive." Un-flattening isn't a supported operation in any PDF tool because the information needed to reverse it (which specific text corresponds to which original field, and where the field boundaries were) simply isn't preserved.

Printing to PDF creates a different kind of derivative

Printing to a virtual PDF printer also tends to remove interactive fields, but its output depends on the operating system and driver. It may preserve some text and vectors or rasterize some or all of the page. Either way, document structure, links, tags and other features can change. Purpose-built flattening targets form widgets more directly, though its result still deserves verification.

Before you flatten

Does flattening reduce file size? Usually only slightly, if at all, it removes the field/widget objects, but the underlying content (text, images) is unchanged, so most of the file size stays the same.

Will a flattened PDF still show checkbox marks and radio button selections correctly? Yes, whatever the field displayed at the moment of flattening (checked, unchecked, which radio option was selected) becomes the permanent visual result.

Does a signature field flatten the same way? Yes, in principle, a signature field's current appearance (an image or drawn signature) gets merged into the page just like any other field's value, though digital signature validation objects are a separate PDF feature from AcroForm fields and behave differently.

Flattening is useful when recipients need a stable-looking copy rather than editable controls. Keep the unflattened source, verify every value and remember that visible permanence is not encryption, redaction or tamper protection.