PDF safety boundary
Why Aftermath rejects signed, encrypted, and interactive PDFs
A PDF that looks flat on screen can contain signatures, forms, encryption, permissions, attachments, annotations, or other interactive structures. Rewriting it carelessly can create a file that looks plausible while losing important meaning or trust.
On this page
A visible page is not the whole document
PDF pages can carry interactive form fields, signature data, access restrictions, embedded files, comments, bookmarks, and metadata in addition to the visible page canvas. A renderer may display the page while a rewrite tool cannot preserve every feature correctly.
A safe local tool therefore has to distinguish supported flat documents from documents that need a dedicated professional workflow.
Why rejection can be the correct result
Rejecting an encrypted, signed, permission-restricted, or interactive PDF protects the original from an accidental “successful” export that discards a field or invalidates a signature. The user can then choose an authorised flattened copy or a dedicated application that understands the document’s requirements.
This is a product boundary, not a claim that every complex PDF is malicious or unusable. It is an honest statement about what the browser-local workflow will not rewrite.
| Feature | Risk of casual rewrite | Safe response |
|---|---|---|
| Digital signature | A rewrite can invalidate or obscure the signature state. | Keep the original and use an authorised workflow. |
| Interactive form | Fields and actions may stop working or flatten unexpectedly. | Use a dedicated PDF editor or approved flattened copy. |
| Encryption or permissions | The document owner may have restricted extraction or modification. | Do not bypass the protection. |
| Attachment or annotation | Visible pages may not reveal all related data. | Inspect with an appropriate PDF application. |
What supported operations still do
For supported flat PDFs, Aftermath can perform focused local operations such as merging, splitting, creating a PDF from images, adding new overlays, checking page size, normalising page geometry, removing common metadata, and reviewing probable blank pages.
Each completed operation creates a separate output. Review the new file before replacing any original.
Use a copy for every experiment
Whether a document is processed in a browser or desktop application, preserve the original. A PDF can contain legal, operational, or personal information that cannot be reconstructed from a visual preview alone.
Desktop tools and commands
Use a local tool