Your PDF is about to ask for a password before it opens. Whether that's worth anything depends entirely on who you're protecting it from: a password that stops a coworker from casually opening a shared-drive file is not the same thing as one that stops someone running cracking software against it overnight.
Protect PDF locks your file with a password entirely in your browser — the document never leaves your device. What it can't do is make legacy encryption behave like modern encryption, or force a reader to respect a restriction it was never obligated to enforce. This guide covers both halves: setting a password that actually helps, and what it's realistically worth.
User Password vs. Owner Password: Two Very Different Locks
A PDF can carry two separate passwords, and readers treat them very differently.
- User password gates opening the file at all. Without it, a compliant reader won't render the document — no preview, no text, nothing.
- Owner password doesn't block opening. It sets permission flags — "don't allow printing," "copying," or "form-filling" — that a reader is supposed to respect once the user password is entered.
That second part is where people get the wrong idea. Owner-password restrictions are advisory, not enforced by encryption — a request written into the file, not a lock on the content. Mainstream apps tend to grey out the print or copy menu as asked, but command-line tools, some mobile viewers, and anything built on lower-level PDF libraries commonly ignore the flag, since the decrypted content is fully available the moment the user password is entered. A permission flag is not a security control — it's closer to a "please don't copy" note.
Specific to this tool: PDFCraft's Protect PDF sets the owner password equal to the user password, and hardcodes every permission bit to "granted" — printing, copying, editing, form-filling. The output carries no copy, print, or edit restriction whatsoever — only the password gate on opening it. There's no separate, unshared owner password here, and no restrictive flag to turn on even if there were. A genuine user/owner split, or an actual permission restriction, needs desktop software that exposes both as configurable fields.
How Strong Is This Encryption, Really?
PDFCraft encrypts with RC4 128-bit, using standard security handler revision 3 (V2/R3) — a deliberate compatibility choice. Every PDF reader built since the early 2000s can open it, including older systems that never picked up the AES-256 handler (revision 6).
The trade-off: RC4/R3 is legacy cryptography, and the weak point is how fast a computer can test password guesses. Its key derivation runs a small, fixed number of MD5 rounds — adequate for 1999 hardware, never hardened against brute force the way a modern password hash (bcrypt, Argon2) is. Tools such as hashcat ship PDF-cracking modes built for exactly this, testing tens of millions of guesses per second on one consumer GPU. An eight-character dictionary-plus-digits password can fall in minutes; a long, random passphrase pushes the same attack out to years, because it's the password's entropy doing the protecting, not the encryption's name.
In practice, RC4 128-bit with a genuinely long password is adequate against a coworker glancing over a shoulder or a lost laptop — not against someone who downloaded the file, has cracking software, and is motivated to get in. Every method has a ceiling; your password decides how close you get to it, but none pushes RC4/R3 past where AES-256 starts.
What Password Protection Actually Stops
Each layer stops something different, and none of them stop everything:
| Protection | What it stops | What it does not stop |
|---|---|---|
| User password | Opening the file at all; keeps casual viewers out entirely | An attacker running offline cracking software; the password holder sharing it onward |
| Owner password / permission flags | Greys out print, copy, or edit menus in readers that honor them | Readers that ignore the flags (common); screenshots or OCR; re-saving to a fresh, unrestricted PDF |
| RC4 128-bit (PDFCraft's method) | Everyday snooping, a lost device, accidental exposure; opens in virtually any reader | Sustained offline brute-force with GPU cracking tools, especially against short passwords |
| AES-256 (desktop software) | The same everyday protection, plus a far slower key derivation that makes each guess dramatically more expensive | A weak or dictionary password — still crackable eventually; some legacy readers can't open it |
| Encrypted archive or transfer service | Protects the file as a container, independent of the PDF's own encryption | Nothing about the PDF itself — extract and re-share it alone and the protection is gone |
Heads up: none of this replaces judgment about who you send a file to. A password stops an interceptor — it does nothing once you've knowingly sent it to the wrong person, or that person forwards the file and password together.
Choosing a Password That Actually Matters
Two decisions matter far more than throwing in symbols:
- Length beats complexity. A password like
Tr0ub4dor&3and a passphrase likehorse battery staple lighthouselook different on a strength meter, but the passphrase is harder to brute-force — length multiplies the search space exponentially, while a swapped symbol barely dents it. Aim for sixteen or more characters, or let a password manager generate one. - The encryption ceiling still applies. No password, however long, makes RC4 128-bit resistant to a well-resourced, patient attacker with specialized hardware — it just makes the everyday attempt take impractically long. Surviving that adversary needs a different encryption method, covered below.
Avoid anything tied to public information about you or the recipient — names, invoice numbers, dates that also appear in the document or the email carrying it. If the password is guessable from context an attacker already has, length stops helping.
Sharing the Password Without Undoing the Point
The most common way PDF password protection fails isn't cracking — it's habit. Attaching the file to an email and typing the password in the same message hands both halves to anyone who gets access to that one channel. If either account is compromised or the message is forwarded to the wrong person, the password travels with the file for free.
Send the password a different way than the file went: a text message if the PDF went by email, a phone call, or a password manager's secure-sharing feature. It just needs to not sit next to the file it unlocks.
Why PDFCraft Won't Protect an Already-Protected PDF
Run a PDF that already has a password back through Protect PDF and the tool refuses. That's not overcaution — PDF encryption isn't a wrapper you can stack like an already-zipped file. A single encryption dictionary describes exactly one state for the whole document, so encrypting it a second time doesn't double-lock it; it processes data the library can no longer interpret, and the usual result is a PDF neither password can open.
To change a PDF's password, unlock it with the current password first, confirm the plain result opens correctly, then run it back through Protect PDF with the new one. That's a different job from stripping sensitive content out of a document rather than locking it — for that, redacting and removing PDF content covers what genuinely deletes data versus what only covers it up.
When You Need More Than RC4
For routine sharing — a signed lease, a low-stakes scanned form, an internal draft — RC4 128-bit with a long password is proportionate. For serious exposure — medical records, legal files, financial statements, government IDs — move up a tier:
- AES-256 from desktop software. Adobe Acrobat Pro and other desktop tools offer AES-256 (revision 6) encryption with a far slower, more brute-force-resistant key derivation, supported by almost anything from the last decade.
- An encrypted archive. Put the PDF inside a 7-Zip or similar archive with AES-256 before sending it — a container independent of whatever the PDF itself carries.
- A secure transfer service instead of an email attachment for sensitive one-off sends — ideally one with link expiry and no permanent copy left on a third-party server.
If you're weighing whether an online tool is safe for confidential documents at all — not just PDFCraft — this guide on evaluating online PDF tools walks through what to check before you upload anything, client-side processing or not.
Frequently Asked Questions
Can someone tell my PDF is password protected without opening it?
Yes. File managers and PDF readers typically show a lock icon or password prompt right away, because the file's encryption dictionary flags it as protected — even though the content itself stays unreadable without the password.
If I forget the password I set, can PDFCraft recover it?
No. Protect and Unlock only remove a password you already know; building a recovery function would mean shipping a password-cracking tool. If you lose the password, restore the unprotected original, or try a dedicated recovery utility yourself.
Does protecting a PDF also stop someone from copying the text out of it?
No. PDFCraft leaves every permission bit granted, so its output carries no copy or print restriction at all — the password gates opening the file, nothing more. Desktop software that does set restrictive flags is only marginally better, since those flags are advisory and many readers ignore them anyway.
Will a password-protected PDF still work with e-signature tools or online form fillers?
Generally not until it's unlocked, since most third-party services need to read the file's content to place signature fields or fill forms — they'll ask for the password or fail outright. Unlock it for that step, then re-protect it afterward if needed.
Is RC4 128-bit illegal or non-compliant for business use?
No — RC4 128-bit is a standard, documented part of the PDF specification and legal to use anywhere; it's a strength question, not a legal one. Some contracts specify a minimum standard, often AES-256 — check your own obligations rather than assuming any tool satisfies them automatically. This isn't legal advice.
Can I set different passwords for opening the file versus restricting printing?
Not with PDFCraft's Protect PDF — it sets one password that serves as both the user and owner password. Desktop software such as Acrobat Pro exposes these as two separate fields if you need a document that opens freely but restricts printing under a different password.