A filled-in form is not a finished document

You open a PDF form, type your answers, save, and send it. The recipient opens it and half the fields are empty, or the text is a different size, or a date reads differently from the one you entered.

Nothing went wrong in transit. The values were never part of the page.

Fields are a separate layer

A PDF form field is an interactive object sitting above the page content, holding a value and a description of how to draw it. Its appearance is generated by the reader.

That is the crux: the reader decides what the field looks like. Different readers make different choices about fonts, sizes, date formats and how to handle text longer than the box. Some regenerate appearances on open; some trust what was stored; some do neither reliably.

Which is how a form that looks perfect in the software you filled it in with can look wrong in the software your recipient uses.

The specific failures

• Fields appearing empty. The value is stored but no appearance was generated, and the recipient's reader does not generate one.
• Text sized differently. Auto-sizing fields recalculate per reader.
• Dates reformatted. Formatting is a script attached to the field, and script support varies.
• Values silently editable. Anyone who opens it can change your answers. Nothing marks them as submitted.
• Printing differently from the screen. Print paths sometimes take the stored appearance where the screen takes a regenerated one.

Flattening

Flattening draws each field's current appearance into the page content and removes the field. Afterwards there is no interactive layer, no value to regenerate, and nothing for a reader to reinterpret. It looks the same everywhere because it *is* the same everywhere.

It is one-way. Keep the fillable original if you might need to fill it again — the flattened copy cannot be un-flattened, and reconstructing a form from a flat page is a job nobody wants.

When to flatten

• Before sending a completed form anywhere. This is the main one.
• Before merging into a packet. Merging often loses form fields entirely, which silently discards every answer. Flatten first and the values are page content, which merging preserves.
• Before archiving. A document whose appearance depends on the software that opens it is a poor archival record.

The metadata footnote

Form fields have names, and those names sometimes reveal more than the answers: internal identifiers, department codes, the structure of a system. They disappear when you flatten, which is a small privacy benefit thrown in for free.

Worth inspecting a form before flattening if only to see what was there.