The answers you typed into that form are not part of the page

Open a filled-in form in one viewer and the figures sit neatly in their boxes. Open the same file in another and the boxes have a pale blue tint, or the text sits a couple of pixels high, or a field you know you completed comes up empty. The file didn’t change between the two. What changed is who did the drawing.

reader.me now has a tool for the moment you decide that drawing should stop being negotiable: Flatten PDF takes what a field or a comment currently paints on screen, presses it into the page itself, and removes the interactive object behind it.

A field keeps its value and its picture in two different places

An AcroForm field isn’t written into the page the way a paragraph is. It’s an annotation: an entry in a list attached to the page, sitting on top of it. That entry holds two things that are easy to confuse.

One is the value — the string 1,480.00, the state Yes on a checkbox, the name you typed into the box marked Signature. The other is the appearance: a small self-contained drawing that says how that value should look, with its own font, size, colour and position inside the field’s rectangle.

The page content stream, the part of the file that actually describes the document, mentions none of it. It draws the blank form. Everything you filled in is painted afterwards, on top, by whatever program has the file open.

Which is why “looks the same” and “is the same” come apart

Two people can open the identical file and see slightly different documents, because the appearance is a suggestion the viewer is free to regenerate. Some forms are even saved with a flag that asks it to. Most of the time the result is close enough that nobody notices. Sometimes it isn’t, and the difference lands in a number.

The bigger issue isn’t cosmetic. An unflattened form is a blank document plus a set of instructions for writing on it, and both halves travel together. Whoever receives it gets the fields, the values inside them, and the ability to type over any of them. Change the string, and the drawing follows the string. The document looks exactly as legitimate afterwards as it did before.

That’s the gap flattening closes. Not “the file is protected now” — it isn’t, and no PDF operation makes a document tamper-proof on its own. What changes is that the answers stop being data with a rendering attached and become part of the drawing, indistinguishable from the printed form around them.

What the tool actually moves

For each field it resolves the appearance, works out where that drawing belongs on the page, writes it into the page’s own content, and then removes the field from the form. The result renders identically, because it is literally the same drawing — just relocated from the layer above the page into the page.

Two independent switches, because they’re two different questions:

• Form fields — the boxes, checkboxes, dropdowns and signature fields.
• Annotations — comments, highlights, sticky notes, stamps, freehand ink. Everything that lives in the same list as the fields but isn’t one.

You can flatten the form and leave the review comments alone, or the reverse. Before it does anything the tool counts what it found and tells you, so a document with nothing to flatten says so instead of handing you back an identical file with a triumphant message.

Links are left alone, on purpose

Links are annotations too, technically speaking. They also draw nothing at all — the blue underlined text is page content, and the link is just a clickable rectangle sitting over it. Flattening a link would move an empty drawing onto the page and take away the click. The visible document wouldn’t shift a pixel and every cross-reference in it would quietly stop working.

So links are counted and kept, every time, and the tool tells you how many it kept.

Removed from the file, not just unhooked

When an annotation is flattened, dropping it from the page’s list isn’t enough. A comment that read “don’t send this figure yet” is an object in the document, and unlinking it leaves the object sitting in the file with its text intact. Anyone reading the raw bytes finds the sentence.

So the object gets deleted from the document, not just detached from the page. It’s the same distinction that separates real redaction from drawing a black rectangle over a name: hidden and gone are not the same state, and only one of them survives someone who looks properly.

The fields that stay editable, and why you’ll be told

Some fields can’t be flattened. A widget with no stored appearance, an appearance that isn’t a proper reference, a field attached to no page at all — malformed documents are common, and there’s no honest way to paint a drawing that doesn’t exist.

The tool could fail the whole file over one bad field. It doesn’t. It flattens everything it can and then names the fields it couldn’t, so you know that specific boxes in the copy you’re about to send are still typeable. A tool that flattened nine fields out of ten and said “done” would be worse than useless.

Two things it won’t touch at all: XFA forms, the XML-based ones that demand Adobe’s own software to open properly, and encrypted documents it can’t read.

It doesn’t undo

Once the values are page content, they cannot be typed over again. There’s no un-flatten. The copy you download is final in that specific sense, and it’s why the operation belongs at the end of a document’s life rather than in the middle — after the signature, not before the next revision.

Your original file isn’t touched. Everything runs in your browser, the document never leaves your machine, and if you decide you flattened too early, the version you started from is still sitting where you left it.