BASALT · JOURNAL
Removing restrictions from a PDF you own
A document that opens but refuses to let you print, copy or edit carries an owner password setting permissions. This is different from a document that will not open at all.
What permissions actually are
A set of flags asking viewers to restrict certain operations. Cooperative applications honour them. They are not a protection: the content is fully present and readable, and any tool that ignores the flags can do whatever it likes.
Treat them as a courtesy setting. If material genuinely must not be copied, it should not be in the document.
Removing them on your own document
qpdf --decrypt input.pdf output.pdfIf an owner password was set and you have it, add --password=. If only permissions were set with no user password, the command above often works without one, because the document was never encrypted against reading in the first place.
When you should not
If the restriction was placed by someone else on a document you received, removing it may breach the terms you received it under, whatever the technical ease. The fact that it is trivial is not permission.
The related confusion
People frequently apply a password expecting it to make a document safe to send. It does not remove anything. Metadata, attachments, hidden layers and any text under a black box are all still there and all readable by anyone with the password.
Encryption controls who opens the document. It has no effect on what is inside it. If the concern is content, the operation you want is redaction and sanitisation, not a password.
After removing
You now hold an unrestricted copy. Keep the original alongside it if the document matters, so it remains clear which is which.
Frequently asked questions
How do I remove restrictions from a PDF?
qpdf --decrypt input.pdf output.pdf removes permissions on a document you own, adding --password= if an owner password was set and you have it.
Are PDF permissions actual security?
No. They are flags asking cooperative viewers to restrict operations. The content is fully present and any tool that ignores the flags can copy, print or edit freely.
Should I remove restrictions from a document someone sent me?
Technical ease is not permission. If the restriction reflects the terms you received the document under, removing it may breach those terms regardless of how simple it is.
Does password protecting a PDF make it safe to send?
No. Encryption controls who can open the document and removes nothing from it. Metadata, attachments, hidden layers and text under black boxes remain and are readable by anyone with the password.
Doing it in Basalt
Basalt is a native macOS PDF toolkit: eighteen tools in one window covering merge, split, page organisation, compression, OCR, passwords, Bates numbering, forms, signing, watermarks and comparison. Every file is processed on your Mac, and the engine that opens documents holds no network entitlement at all, which macOS enforces at the code-signature level. Redaction destroys content rather than covering it, and an independent verifier proves the material is gone before a file is written. A one time $29 licence covers up to three Macs, free for the first 24 hours. basaltformac.com, or brew install --cask chipmunk1101/tap/basalt.
Redaction that proves itself
Basalt destroys the content you mark, then re-opens the file it wrote and proves the content is gone before it saves anything. Your documents never leave your Mac.