Proteger PDF com Senha

AES-256 is the correct choice for any PDF you encrypt today, and it is the default this tool applies. It is standardised in PDF 1.7 Extension Level 3 and adopted in PDF 2.0, supported natively by every PDF viewer released after 2009 — including Acrobat Reader, macOS Preview, Chrome's built-in viewer, iOS Books, and any Android PDF app. The algorithm itself uses 256-bit keys in CBC mode with a PBKDF2-SHA256 key-derivation step that significantly raises the computational cost of brute-force attacks compared to older schemes. AES-128, introduced in Acrobat 7, is technically adequate for low-sensitivity documents but offers no meaningful advantage over AES-256 on modern hardware since both encrypt and decrypt at essentially the same speed. The older RC4-based encryption — 40-bit from PDF 1.1 and 128-bit from PDF 1.4 — is cryptographically broken; dedicated GPU cracking tools can recover RC4 PDF passwords in minutes on consumer hardware, and both variants should be considered insecure for any document you care about protecting. The only reason to choose RC4 today is if a recipient is using a legacy reader from the early 2000s that does not support AES, which is an extremely rare scenario. When in doubt, stay with AES-256 and pair it with a strong password — the algorithm is only as effective as the passphrase protecting it. Use the entropy meter in the tool to confirm your password reaches an acceptable estimated crack time before exporting.

No — the two password types are entirely independent in the PDF specification, and you can set one, both, or configure them differently depending on your use case. The user password (also called the open password) gates access to the document completely; anyone who receives the PDF must type this credential before a single page renders. The owner password (also called the permissions password) controls what an authenticated user can do with the file — it governs printing, copying, editing, form-filling, and annotation permissions without blocking reading. Setting only a user password creates a fully locked document where reading itself requires a credential, appropriate for confidential material like salary slips or tax returns. Setting only an owner password leaves the file readable by anyone but enforces the permission flags you choose, a common approach for whitepapers or client deliverables where the creator wants to prevent editing and watermark removal. Setting both passwords gives the most granular control: one password opens the file for reading, a different (and preferably stronger) password grants full modification rights. This tool lets you fill each field independently; the owner password field defaults to blank, which means the tool reuses the user password for the owner slot — the simplest and most common setup. If you only need to lock down printing and copying for a widely distributed document, an owner-only password with print and copy restrictions ticked is the standard approach. Store both passwords securely; neither can be recovered from the encrypted file without the credential.

The PDF 1.7 specification defines a permissions bit-field embedded in the encryption dictionary that controls six categories of user action, all governed by the owner password. Print restricts whether the viewer's print function is available, with an additional sub-option to allow only low-resolution or draft printing rather than full-quality output — useful for watermarked review copies. Modify blocks structural content changes: inserting, deleting, or rotating pages, as well as editing the body text of the document. Copy prevents selecting and extracting text or images; most PDF viewers enforce this by disabling clipboard access for PDF content. Annotate controls whether users can add comments, highlights, sticky notes, or free-draw annotations. Fill forms permits the user to complete interactive form fields and sign signature fields even when the broader Modify flag is off, which is the standard setup for fillable forms distributed to external parties. Extract for accessibility allows assistive technologies — screen readers, text-to-speech engines — to read the document content even when the Copy flag is disabled; best practice is to always leave this enabled because blocking it makes the document completely inaccessible to visually impaired readers without providing any meaningful security benefit. This tool exposes all six flags with safe defaults: print, copy, and accessibility are permitted; editing, annotation, and form-fill are blocked. Adjust them to match your distribution policy, then apply AES-256 encryption and a strong owner password. The encryption and flags are written into the output PDF's trailer dictionary and honoured by all compliant viewers.

In practical terms, no — provided you choose AES-256 encryption and a genuinely strong password. AES-256 itself has no known cryptographic weaknesses; attacks universally target the password rather than the cipher. The security of your encrypted PDF therefore reduces entirely to password strength. A randomly generated 12-character password mixing uppercase, lowercase, digits, and symbols requires an estimated 10^20 guesses under brute force, which exceeds the capacity of all consumer GPU clusters combined by many orders of magnitude. A correctly chosen 5-to-7 word passphrase generated from a large wordlist (Diceware-style) is similarly unbreakable in practice. What does fail quickly: single dictionary words reach under a second on modern hardware. First-name plus birth year combinations fall in minutes. Short all-numeric PINs under 8 digits can be cracked in hours. The AES-256 key-derivation scheme in PDF uses PBKDF2-SHA256 with a 50,000 iteration count, which adds meaningful cost per guess compared to raw hash cracking, but that protection is overwhelmed by poor password choices. This tool includes a live entropy meter that estimates crack time as you type; use it to confirm your password reaches years rather than hours before exporting. Do not reuse passwords across different encrypted files. Do not store the password in the same location as the encrypted PDF. For documents that must remain confidential indefinitely — legal agreements, medical records, financial instruments — treat the password as you would treat a cryptographic key: generate it randomly, store it in a password manager, and share it only over an end-to-end-encrypted channel.