Password Protect a PDF Online – Encrypt Your File with AES-256

Password protect a PDF without sending it anywhere

Jobsixo lets you password protect a PDF in your browser. You add the file, choose a password, decide whether people who open it may print, copy or edit, and download an encrypted copy. Without the password the document will not open, in any reader, on any device.

It suits anyone who has to email something sensitive: a bank statement, a salary slip, a scanned ID, a draft contract, a medical report. Because the encryption happens on your own device, the unprotected file never travels to a server on its way to being locked.

How to add a password to a PDF

1. 1
   Drop the PDF on the upload area, or click it to browse. You can add several files and they will all get the same settings.
2. 2
   Type a Password. It must be at least four characters, and spaces at the very start or end are trimmed off. Note that the box shows what you type rather than dots.
3. 3
   Optionally fill in Owner password. Leave it empty and the first password is reused, which has consequences explained below.
4. 4
   Set Allow printing, Allow copying text and Allow editing. Each is a Yes or No choice and all three start at Yes.
5. 5
   Press Protect PDF and wait for the Done heading.
6. 6
   Download protected.pdf. With several files, each is named after its original with -protected.pdf added, and a Download all button packs them into one ZIP.
7. 7
   Open the result in a reader and confirm that it asks for the password before showing anything.

How the encryption works

The page runs qpdf, compiled to WebAssembly, inside your tab. qpdf writes the standard PDF security handler at revision 6, which uses AES with a 256-bit key for the document's streams and strings. That is the same scheme the desktop qpdf program produces, and it is what current versions of Acrobat and every mainstream browser reader expect. There is no weaker option on this page, so you do not have to pick a key length.

Two passwords can sit in one file. The open password, also called the user password, is what a reader asks for before showing the pages. The owner password governs permissions. When you choose No for printing, copying or editing, qpdf records the matching permission flags: no printing at any resolution, no extraction of text and images, and no modification, which covers form filling, annotations and page assembly. Extraction for screen readers stays allowed, so assistive software can still read the document aloud.

The three permission switches

These are permissions, not locks on the content. The open password is what keeps people out. The flags only ask a cooperative reader to behave.

Use a separate owner password if you want the restrictions to hold

This is the point people miss. If you leave Owner password empty, the open password is used for both roles. Anyone who types it is then recognised as the owner, and a reader gives owners full rights, so your No settings have no effect on someone who knows the password. We checked this against qpdf: with a matching pair the supplied password is reported as the owner password and the permissions are not enforced.

If printing, copying or editing really should be blocked for recipients, enter a different Owner password and keep it to yourself. Recipients then open the file with the open password and meet the restrictions. If you only want the file to stay private and every recipient is trusted, one password is fine.

How strong the protection really is

A 256-bit key is not something anyone can guess by brute force. The weak point is the password that the key is derived from. A short or predictable password can be tried quickly by software, whatever the cipher, so the protection you get is only as good as the phrase you chose.

Encryption also protects the file, not what happens after it is opened. Someone who has the password can save an unprotected copy, take screenshots or retype the content. If the real concern is who sees a particular figure or name, remove that text before you protect the document, and treat the password as a gate rather than a guarantee.

When a password is the right choice

Use it when a document has to travel through channels you do not control, such as email, a messaging app, a shared drive or a USB stick, and you want only the intended person to read it. It is less useful for files that live on a device you already protect, or for material you actually want strangers to read.

For something public that you only want to keep tidy, leave the open password out of the picture altogether. This tool always sets one, so if the aim is just to discourage editing, a watermark or a flattened export may serve you better than a lock that every reader must unlock first.

Choosing a strong password

• Length beats cleverness. A phrase of four unrelated words is easier to remember and far harder to guess than an eight-character mix of symbols.
• Avoid anything findable: names, birthdays, phone numbers, the file's own title.
• Do not reuse a password from an email account or a bank login.
• Share the password through a different channel from the file. Posting both in the same email undoes the protection.
• Store it in a password manager, or write it down somewhere other than next to the document.
• The four-character minimum is a floor, not a recommendation.

If you lose the password

There is no recovery route. The password is never stored by the page, and the encryption is designed so that the file cannot be read without it. Jobsixo cannot reset it, and neither can anyone else. The tool's own note says as much when it finishes.

The practical rule is to keep an unprotected original somewhere safe before you encrypt the copy you send out. If you still know the password later and want the protection gone, Unlock PDF removes it.

A worked example

You are sending a 12-page bank statement, statement-june.pdf, of about 1.8 MB, to your accountant, and you want her to read and print it but not copy figures out of it. You add the file, enter a passphrase of four random words as the Password, type a different phrase as the Owner password, leave Allow printing on Yes, and set Allow copying text and Allow editing to No.

You press Protect PDF. The page reports one finished file, protected.pdf, with a note that it was encrypted with AES-256 and cannot be recovered without the password. You open it: a prompt appears. After entering the open password the statement displays and prints, while selecting text is blocked. You email the file and send the passphrase by message. If you had added three statements instead of one, you would receive three files named statement-april-protected.pdf and so on, plus a ZIP.

How to read the result

The line under the Done heading confirms the encryption and repeats the warning about the password. The proof is in the file itself: open it in two different readers, such as a browser and a desktop viewer, and check that both ask for the password first. In Acrobat Reader, the Security tab of Document Properties lists which actions are allowed, and it should match your Yes and No choices when you opened the file with the open password.

Common situations

• Emailing payslips, tax returns, offer letters or ID scans.
• Sharing a draft with a client who should not forward or reuse the content.
• Archiving documents on a shared drive or cloud folder where several people have access.
• Locking a final report before sending it to print, with editing set to No.
• Adding a layer of protection to a scanned certificate before uploading it somewhere you do not fully control.

Mistakes to avoid

• Sending the password in the same message as the file.
• Encrypting the only copy of a document and then forgetting the password.
• Leaving Owner password empty and expecting the No switches to bind recipients.
• Protecting before finishing the edits. Compress, watermark and fix the file first, then encrypt last.
• Believing the permission flags are unbreakable. A person who can open the file may be able to clear them with a tool such as Remove Restrictions, which is why the open password is the real protection.
• Putting confidential text under a black box and assuming it is gone. Use Redact PDF to destroy the text before encrypting.

Limits and honest limitations

A file that is already encrypted is blocked, and the page tells you to open Unlock PDF first. Files over 100 MB, or with more than 500 pages, are blocked too, because the work happens in browser memory. A damaged file is also stopped, with a pointer to the repair tool.

The page offers one scheme, AES-256 with a password. It does not do certificate-based encryption, does not sign the document, and does not hide the file name, size or the fact that it is a PDF. Metadata inside the document stays with the document and is simply encrypted along with it. A very old reader that predates AES-256 support may fail to open the result, so recipients on ancient software should update.

The same password goes onto every file in a batch. If different recipients need different passwords, run the files one at a time.

Your file and your password stay local

Encryption runs in your browser through WebAssembly. Neither the PDF nor the password is sent to Jobsixo. When a workflow includes a protect step, the password is asked for at run time and never written to storage or into an exported workflow file.

Related tools

Before locking a file, shrink the PDF if it is too big to email, or add a watermark that marks it as confidential. If you have several documents for one recipient, merge them first so only one password is needed. For jobs you repeat, a saved workflow can run merge, compress and protect in one go.