Free · runs in your browser

File Encrypter Decrypter

File Encrypter Decrypter. Drop a file and enter a passphrase to instantly encrypt or decrypt it with AES-256-GCM. Signing a release or encrypting an email to a colleague both start with the pgp key pair generator and a User ID.

Your values
Mode

AES-256-GCM encrypts the file and adds an authentication tag that detects tampering. The XOR key cipher only shows how a key scrambles text; it is not secure.

Encrypting: any file. Decrypting: the .enc file this tool produced (the earlier version's .enc files work too) or its Base64 text saved as a file. A chosen file is used instead of the pasted content. It never leaves your browser.

Encrypting pasted content: how it is written (use Base64 or Hex for images, PDFs and other binary data). Decrypting: how the restored file is shown; a binary file is shown as Base64 when Text is chosen.

Used when no file is chosen. Decrypting: paste the Base64 output exactly as this tool produced it (for XOR, the comma-separated numbers). Nothing is sent to a server.

On: the key is derived from your passkey with PBKDF2. Off: a random 256-bit key is generated and shown, and you need that key to decrypt.

Decrypt with the exact same passkey. A lost passkey cannot be recovered, and the file stays locked. Not used when Use secret key is off.

Encrypting only: catches a typo before it locks the file with a passkey you do not know.

Result

Result
—
Output size
—
Suggested file name
—
Generated encryption key
—
Details
—
  • No account, no logging
  • Open formulas explained below
  • Works offline once loaded

A file encrypter decrypter turns readable files into scrambled data that only the right password can reverse, so sensitive files stay safe from unauthorized access and malware snooping. Whether you want a simple file encryption tool or a full encryption tool for entire drives, this guide shows how to encrypt a file, how to decrypt it later, and which choices keep your data secure.

How a File Encrypter Decrypter Uses AES-256 and Symmetric Keys

Most modern file encryptor programs rely on symmetric key cryptography: the same key locks and unlocks the data. The dominant cipher is AES-256, often written as 256-bit AES, and no practical brute-force attack has broken it. The encryption algorithm splits your files into 16-byte blocks and scrambles each one, so security depends on how well you guard that key. Once you encrypt content, only the secret can reopen it. If you want to use the text to nato alphabet converter for an aviation exercise, remember the ICAO forms Juliett and Niner.

Formula card showing 10 billion guesses per second divided by 600,000 PBKDF2 iterations equals 16,667 guesses per second against a file encryption password
PBKDF2 key stretching cuts an attacker's guess rate from 10 billion to 16,667 per second.

A key's size is simply its bit length divided by eight:

$$\text{bytes} = \frac{\text{bits}}{8}$$

That makes a 256-bit key exactly 32 bytes. Strong encryption is about the secret, not the program: even a well-known cipher stays private as long as nobody else holds your secret. Good file encryption decryption workflows are symmetrical, so whatever you did to lock the data you can undo.

Encrypt and Decrypt a File Step by Step

The workflow is the same in nearly every tool. To encrypt files, pick the input file, choose an algorithm, supply a secret and write an output file. Encrypting never touches your original, and decrypting needs the identical secret and algorithm to restore the content. When a helpdesk asks you to read it out loud, check your password phonetic readout first and use the Alfa Bravo style words to avoid ambiguous letters.

  1. Open your encryption tool and select the file you want to encrypt.
  2. Type a long password, then type it again to confirm.
  3. Click Encrypt and wait until the files finish processing; encrypt one test file first.
  4. To decrypt, select the locked copy, enter the same password and click Decrypt.
Encrypt and Decrypt a File Step by Step
AlgorithmKey lengthKey size in bytes
AES128 bits16
AES (strong)256 bits32
3DES192 bits24
ARCFOUR8 to 128 bits1 to 16

Prefer the 256-bit option and treat 3DES and ARCFOUR as legacy choices for old archives only.

Protect an Encrypted File with a Password or Passphrase

Your password never encrypts the data directly. The program stretches it into a key, so a long passphrase of four or five random words beats a short password full of symbols. Store the passphrase in a manager, not beside the encrypted file, and remember that a lost password cannot be recovered by any vendor. You can also password protect a single archive when you only need to share one item.

Run the Command Line on a Folder

A command-line mode in your encryption software suits automation. A recursive option walks a folder and will encrypt or decrypt every file inside it, an unattended flag skips prompts, and a progress bar shows speed. Passing the password inside a command exposes it in your shell history, so prefer an interactive prompt when the folders hold private records. Folders of tax papers or medical scans deserve that protection, and the same folder logic applies to a single folder of scans.

Keep the Original File and Key File Safe

Securely delete the original file only after you confirm the encrypted copy opens. If you use a key file instead of a password, keep a backup on a USB drive stored offline, because losing that file makes your content unrecoverable. Encrypted filenames hide even the document title, which adds privacy and security for shared drives. Encrypt the backup copy as well.

Choosing Free Encryption Software

Dozens of free file encryption options exist, and they split into open source projects you can inspect and freeware whose code stays closed. Open source software lets outside reviewers verify there is no backdoor, which matters for a security tool. Freeware can still be excellent: a Windows freeware program lets a casual user lock files, or a whole folder, with a password and no setup. Choose open source when you want to audit the code, and freeware when convenience wins. Some open source projects are also freeware, so cost and transparency are separate questions, and a signed Windows installer from a known publisher is a good sign in either camp.

Look for these traits when comparing file encryption tools:

  • Solid AES support with a published encryption algorithm
  • Compress and encrypt in one step, so files shrink before locking
  • Compatibility with 7-zip or WinZip, so decryption never depends on one vendor
  • Offline operation, so privacy does not rely on a cloud upload
  • A clearly stated open source or freeware licence and a visible download source

An online tool that asks you to upload a file adds trust risk, since the data leaves your machine. Local freeware or open source apps are the safer default for anything confidential, and any secure choice should lock your files before they travel.

Locking a Scanned Tax PDF with an Encryption Tool

I need to email a scanned tax return, receipts-2025.pdf, to my accountant, and email is not a safe place for a Social Security number. So I decide to encrypt the file first and send the passphrase through a separate channel. The PDF is 3,482,917 bytes.

In my file encryption tool I pick AES with a 256-bit key, type a six-word passphrase, and set 600,000 PBKDF2 iterations, the figure OWASP currently recommends for PBKDF2 with SHA-256. Before sending, I cross-check the result by hand: 3,482,917 bytes is 217,682 full blocks plus 5 bytes, so padding adds one block, giving 217,683 × 16 = 3,482,928 bytes. The 16-byte OpenSSL header (the Salted__ marker plus salt) brings the output to 3,482,944 bytes, and the file on disk matches exactly.

Next I rerun with one input changed, a scan that is 11 bytes larger:

Locking a Scanned Tax PDF with an Encryption Tool
Input size (bytes)Padded (bytes)Output with header (bytes)
3,482,9173,482,9283,482,944
3,482,9283,482,9443,482,960

The second row is the edge case: a file that is an exact multiple of 16 still gains a whole extra padding block, so never use output size alone to guess the original length. What stands out is that the passphrase matters far more than the size arithmetic. If my accountant mistypes one character, the decryption fails outright, so I send a short test file first and keep the original until she confirms she can open it.

Password-Based File Encryption Settings

Password-based encryption follows the PKCS standard: a random salt and many iterations turn your secret into a key. PBKDF2 is the usual derivation function, and OpenSSL implements it with a command such as openssl enc -pbkdf2 -in notes.txt. More iterations slow each guess an attacker makes, so choose at least 600,000 for modern hardware. Always encrypt before you upload anything. Security rests on the secret's strength first and the settings second. Encryption strength also rises with every extra iteration.

Heatmap of average time to crack an encrypted file password by length and character set, from 73 days to 452.7 billion years
Average time to find the password behind an encrypted file, with the 12-character letters-and-digits example outlined.

Size changes after encryption are predictable. For a 1,000,003-byte file in CBC mode, padding rounds the data up to 1,000,016 bytes and the salt header adds 16 more, giving an output file of 1,000,032 bytes. Some tools keep keys in a keystore instead, which is convenient but ties decryption to that one machine.

Decrypt Files Without Losing Data

To decrypt files, reverse the exact settings: same algorithm, same password, same iteration count. A mismatch yields garbage or an error, never partial recovery, so write the settings down. Open a copy first, encrypt a copy for testing, and run your decryption tool on a test file before you trust it with the only copy.

Some tools lock critical metadata in a companion file, and moving or editing it makes decryption impossible. Back up both the encrypted data and that metadata. Treat decryption as a privilege: only an authorized user with the right secret should ever perform it, and you should decrypt only on a trusted, secure machine.

Frequently Asked Questions

What file types can I encrypt?
Any file at all -- documents, images, archives, videos -- since the tool operates on raw bytes rather than parsing the file's format. The encrypted output is a generic binary file (.enc) regardless of what you started with.
How do I get my original file back?
Switch to Decrypt mode, choose the .enc file, enter the exact same passphrase you encrypted it with, and click Decrypt File -- the original file downloads with its original name restored (the .enc suffix is stripped automatically).
Why does the download start automatically?
Both encryption and decryption produce a new file as the direct result, so this tool triggers a browser download immediately rather than displaying the (typically large, binary) result on the page -- the same behavior as any file-processing tool that hands you back a modified file.
Is there a file size limit?
The whole file is read into memory and encrypted in one pass, so very large files (many gigabytes) may be slow or hit your browser's memory limits -- this tool is best suited for typical document, image, and archive sizes rather than huge media files.
Is my file uploaded anywhere?
No. Encryption and decryption both happen entirely in your browser using the Web Crypto API -- the file is never uploaded, transmitted, or stored anywhere outside your own device.

About the author

Vinitha Pu

Founder and designer

Vinitha Pu is a graphic designer based in Palakkad, Kerala, who builds free, privacy-friendly browser tools. She studied Textile and Apparel Design at Avinashilingam University and completed a C-Tech in Graphic Design at Image Creative Education in 2025. She designs, builds and maintains the password generators, strength checkers, hash tools and security calculators on PasswordHive.

  • Content author: Vinitha Pu
  • Fact checked by: Vinitha Pu. Each tool's output is checked against official test vectors or a reference implementation, and every strength and crack-time figure against the formula it uses, before it goes live.
  • Published Updated