Passwords, redaction, and flattening address access, disclosure, and editability - Not the same security problem. There is no one-line answer here: it depends on evidence from the source, the specific properties named below, and the destination's real requirements.
Pages, text flow, fonts, tables, forms, accessibility tags, signatures, and macros need separate consideration. In “Protect, redact, or flatten? Three very different PDF actions,” begin with this specific observation: Encryption controls who can open or change a file.
Three findings that guide this choice
The core distinction
Encryption controls who can open or change a file.
The practical trade-off
True redaction removes underlying content, not merely its appearance.
The verification test
Flattening merges interactive layers but is not a substitute for redaction.
A practical decision for this workflow
Verify redactions by searching, copying, and inspecting exported objects before release.
Use flattening merges interactive layers but is not a substitute for redaction. as the acceptance test on a representative source before committing an entire archive, publication, or delivery batch.
The pdf & documents mistake to avoid here
Drawing a black rectangle over confidential text and leaving the text selectable underneath.
That failure conflicts directly with the recommendation for “Protect, redact, or flatten? Three very different PDF actions”: Verify redactions by searching, copying, and inspecting exported objects before release.
Review checklist before delivery
- ✓Page count, order, dimensions, and orientation are correct.
- ✓Text remains searchable or editable where required.
- ✓Tables, fonts, links, forms, and reading order were inspected.
- ✓Signatures and permissions are revalidated after conversion.
Judge “Protect, redact, or flatten? Three very different PDF actions” by whether the result passes these specific checks, not by whether a new file merely opens.