How to lock filled pdf form fields to make them read-only
- Step 1Confirm every answer is final — Verify all fields are complete and correct. Locking is permanent — there is no step after this to fix a typo without starting from the editable original.
- Step 2Archive the editable source — Keep the still-interactive file. If a record must be amended later, you re-fill that copy and lock again; the flattened file itself cannot be reopened as a form.
- Step 3Drop the filled form onto the tool — Open the PDF Flatten tool and drop the file. There is no Process button — locking starts as soon as the PDF is read.
- Step 4Let it flatten every field — The tool draws each field's appearance onto the page and removes the field. Text, checkboxes, radios, and dropdowns are all handled in the single pass.
- Step 5Verify nothing is still clickable — Open the result and click where fields used to be. If locking worked, there is nothing to select — confirm long answers and any special characters rendered correctly.
- Step 6Download the locked file — Download
yourfile.flatten.pdf. The data is now read-only page content, ready to archive or distribute.
Read-only flag vs flattening
Why flattening is the stronger lock for sensitive form data.
| Approach | How it works | Weakness |
|---|---|---|
| Field read-only flag | Sets a per-field Ff read-only bit; field still exists | Many viewers ignore it; the bit can be cleared and the field edited again |
| Form-level locking in a viewer | Viewer disables editing in its UI | Only that viewer enforces it; the fields are still live in the file |
| Flattening (this tool) | Draws values onto the page and deletes the fields | Irreversible — keep the editable original for amendments |
Field types and how they lock
Every AcroForm field type the flatten pass handles, with what survives.
| Field type | Locked result | Behaviour |
|---|---|---|
| Text field | Static text | Typed value is drawn, field deleted |
| Checkbox | Static checkmark / empty | Current checked state is frozen |
| Radio button group | Static selected mark | Chosen option frozen, group removed |
| Dropdown / combo box | Static selected value | Only the picked value remains |
| List box | Static selected entries | Selection frozen as drawn |
Cookbook
Locking workflows for forms carrying sensitive answers.
Consent form locked before filing
A signed consent form needs its answers frozen so the record cannot be altered after the fact. Flatten removes every field and bakes the responses in.
Before: 12 checkboxes + 4 text fields, all editable After: same marks and text, zero editable fields Download: consent-2026.flatten.pdf (read-only content)
Why read-only flags are not enough
A field set read-only in one viewer often opens as editable in another. Flattening removes the field so there is nothing to toggle.
Read-only field: Viewer A → greyed out Viewer B → fully editable (ignores the flag) Flattened field: Every viewer → static text, nothing to click
Medical intake sheet, locked locally
Intake forms carry health data that must not be uploaded. Flatten runs in the browser, so the data stays on the machine and the fields end up frozen.
intake.pdf → (browser-local flatten, 0 bytes uploaded)
→ intake.flatten.pdf
PHI never leaves the device; fields no longer editable.Verify the lock actually took
Always confirm after flattening, because a value with unusual characters can fail to bake (see edge cases). Click-test the result.
Open intake.flatten.pdf Try to click each former field → should do nothing If a field is still clickable → re-check that value (likely a non-WinAnsi character; see edge cases)
Lock, then scrub identifying metadata
Locking the answers does not remove document metadata (author, software). For a clean archived record, scrub metadata after flattening.
Step 1: PDF Flatten → freezes the answers Step 2: Metadata Scrubber → strips author/creator/dates Result: locked content + anonymised file metadata
Edge cases and what actually happens
A value with non-WinAnsi characters fails to bake
may fail silentlyFlatten regenerates appearances with the default WinAnsi Helvetica. A field value containing CJK or some accented characters can throw during that step. The tool catches the error and re-saves, which can leave that field still editable. Open the result and verify; for forms heavy in non-Latin text, flatten in a tool that embeds a matching font (e.g. Adobe Acrobat).
Locking cannot be undone
By designFlattening deletes the fields permanently — there is no read-only-off switch afterward because the fields no longer exist. Keep the editable original for any future amendment. This is the intended trade-off for a hard lock.
Annotations are not part of the lock
PreservedComments, stamps, and highlights are annotations, not form fields, so flatten does not touch them and they remain editable. Use the Annotation Remover if the locked record must also be free of markup.
Free tier file or page limit exceeded
blocked on freeFree locking caps at 2 MB and 50 pages. A larger multi-page form is blocked with an upgrade prompt. Pro extends to 50 MB / 500 pages, which covers most bulk intake batches handled one file at a time.
Form is a dynamic XFA form
not supportedXFA (LiveCycle) forms are not standard AcroForm fields and are not flattened here. The data may not appear at all in a non-Adobe renderer. Convert XFA to static PDF in Adobe Acrobat first, then flatten.
Encrypted form is decrypted on output
decrypts on saveThe tool reads encrypted PDFs by ignoring the password but writes the output unencrypted. The fields are locked, but the file itself is no longer password-protected. Re-apply protection with the Password Protect tool if the archive must stay encrypted.
Read-only fields are still flattened
ExpectedIf some fields were already marked read-only, flatten still removes them along with the editable ones — the whole interactive layer goes. The visible value is preserved as page content; the distinction between read-only and editable disappears entirely.
Empty required fields freeze as blanks
ExpectedFlatten bakes the current state, so any field you left empty becomes a permanent blank with no way to fill it afterward. Complete every required field before locking, or the recipient is left with an un-completable gap.
Frequently asked questions
Is flattening really more secure than marking fields read-only?
For preventing edits, yes. A read-only flag is a per-field bit that many viewers ignore and that can be cleared, leaving the field editable again. Flattening deletes the fields and bakes the values into the page, so there is nothing to toggle. It is not encryption — it stops form-field editing, not all possible tampering — but for locking answers it is far stronger than a flag.
Can someone reverse the lock and recover the fields?
No. The interactive fields are removed from the file; there is no un-flatten. A person with a full PDF editor can still alter page content like any document, but they cannot recover the original form structure or the convenience of clicking and editing fields. For a hard answer-lock, that is the point.
Does this encrypt or password-protect the form?
No. Flattening locks the form data into the page; it does not add a password. In fact, if your input was encrypted, the output comes out decrypted. To add protection on top of the lock, run the result through the Password Protect tool, or restrict actions with the Permission Setter.
Will checkboxes and radio buttons lock too?
Yes. The flatten pass handles every AcroForm field type — text fields, checkboxes, radio groups, dropdowns, and list boxes — in one go. The current checked or selected state is frozen as drawn and the interactive control is deleted.
Is the form data sent to a server?
No. All flattening runs in your browser via pdf-lib. Sensitive answers — health data, declarations, personal details — never leave your device. Only an anonymous usage count is recorded when signed in, with no file content.
What if a field value does not lock?
The most common cause is a value with characters outside WinAnsi (CJK or some accents). When flatten regenerates that field's appearance with the default Helvetica, it can error; the tool catches it and re-saves, which may leave that one field editable. Always click-test the result; for non-Latin-heavy forms, flatten in a tool that embeds the right font.
Are there any options to set before locking?
No. The tool has no options panel — it flattens the entire form automatically when you drop the file. That is deliberate: with nothing to configure, you cannot leave a subset of fields unlocked by mistake. Everything gets locked or, if a value errors, you see it in the click-test.
Does locking remove comments and stamps?
No. Those are annotations, separate from form fields, and flatten leaves them in place. If the locked record must also be free of reviewer markup, run the Annotation Remover first or after.
How many forms can I lock at once?
One per run, on every tier — flatten processes a single PDF at a time. For a batch of intake forms, run them one after another. Free allows files up to 2 MB / 50 pages each.
Will the locked file look different from the original?
No. Flatten draws each value where its field was, so the page is visually identical. The only change is that the values are now fixed page content instead of editable fields. If a field had a visible box outline, that outline is drawn too, which is expected.
Should I scrub metadata after locking?
For an archived record, yes. Flattening locks the answers but leaves document metadata — author, creation date, producing software — intact. Run the Metadata Scrubber afterward to anonymise those fields. For removing visible PII from the page itself, use the PII Redactor.
Can I lock just some fields and leave others editable?
No. This tool flattens the whole form — selective per-field flattening is not supported. If you need a mix of locked and editable fields, that requires a full PDF editor like Adobe Acrobat. For most security use cases, locking everything is exactly what you want.
Privacy first
All PDF processing runs locally in your browser using PDF-lib and pdf.js. No file is ever uploaded — only metadata counters are saved for signed-in dashboard stats.