How to Encrypt Images with a Password Online

When Metadata Removal Isn't Enough

The EXIF Remover strips GPS coordinates, camera info, and timestamps so a photo can be shared without leaking personal data. That covers the common case — posting to social media, sending to a client, uploading to a listing. But sometimes the problem isn't the metadata. It's the image itself.

A lawyer storing evidence photos on a shared drive. A journalist carrying source material across a border. Medical imaging files on a hospital laptop. HR documentation with employee photos. Personal photos backed up to a cloud service you don't fully trust. In all of these cases, the image content is the sensitive part — and the only real protection is making the file unreadable without a key. Our photo privacy guide covers the full spectrum of protection options, from metadata removal to encryption.

AES-256-GCM in Plain English

AES-256 is the encryption standard used by governments, banks, and security software worldwide. The "256" refers to the key length — 256 bits, which means 2²⁵⁶ possible keys. Brute-forcing that with current technology would take longer than the universe has existed. This isn't marketing language — it's the actual math.

GCM (Galois/Counter Mode) adds authentication on top of encryption. It doesn't just scramble the data — it also creates a tag that verifies nothing was tampered with during storage or transit. If a single bit of the encrypted file is modified, decryption fails entirely rather than producing corrupted output. You get integrity and confidentiality in one operation.

The Image Encryption tool uses PBKDF2 to derive the encryption key from your password. PBKDF2 runs your password through 100,000 rounds of hashing with a random salt, making dictionary attacks and brute-force password guessing computationally expensive. A strong password plus PBKDF2 key derivation means the encrypted file is as secure as anything commercial encryption software produces.

How to Encrypt an Image — Step by Step

Step 1 — Upload. Drop an image into the Image Encryption tool. JPEG, PNG, WebP, TIFF, BMP, AVIF, GIF — any format works. The image stays in your browser; nothing is uploaded to a server.

Step 2 — Enter a password. Type a strong password. Longer is better — a four-word passphrase like "correct horse battery staple" is stronger and easier to remember than "P@ss1w0rd!". The tool shows password strength feedback in real time.

Step 3 — Encrypt. Click Encrypt. The tool derives an AES-256 key from your password using PBKDF2, encrypts the image data with AES-256-GCM, and produces a .enc file. The output contains the encrypted data, the random salt, and the GCM authentication tag — everything needed for decryption except the password.

Step 4 — Download. Save the .enc file. This is your encrypted image. Store it, email it, upload it to cloud storage — anyone who intercepts or accesses it sees random bytes. Without the password, the file is indistinguishable from noise.

How to Decrypt

Switch the tool to Decrypt mode, upload the .enc file, enter the same password, and click Decrypt. If the password is correct, the original image is reconstructed byte-for-byte — same format, same quality, same metadata. If the password is wrong, decryption fails cleanly with an error message. There's no partial decryption and no way to guess how close you were.

To verify the decrypted file matches the original exactly, run both through the File Hash Scanner. If the SHA-256 hashes match, the file is bit-for-bit identical.

Encryption vs Metadata Removal — When to Use Which

These are different tools for different problems. Metadata removal makes a photo safe to share — the image remains viewable, but identifying data is stripped. Encryption makes a photo safe to store — the image becomes unviewable without the password.

For maximum protection, combine both. Run the image through the EXIF Remover first to strip metadata, then encrypt the cleaned file. This way, even if someone cracks the encryption (unlikely with AES-256, but defense in depth is good practice), the decrypted image contains no GPS, camera, or timestamp data. Check your photo's exposure level with the Privacy Score before deciding which approach you need.

If the image contains faces that need anonymizing for a non-encrypted copy, the Face Blur tool handles that. For text or sensitive regions, use the Redaction Tool. Our journalist photo safety guide covers the full workflow for handling sensitive source material. And if you want to understand exactly what location data your phone embeds, the phone camera privacy settings guide walks through every toggle.

Password Best Practices

The encryption is only as strong as the password. AES-256 is unbreakable, but "password123" is not. A few rules:

Length beats complexity. "my dog ate the router cable in 2019" is a stronger password than "Xy7!kQ#2" and vastly easier to remember. PBKDF2 makes short passwords expensive to brute-force, but a long passphrase makes it effectively impossible.

Unique per file (when it matters). If you're encrypting a batch of sensitive files, using the same password for all of them means one compromise exposes everything. For archival encryption, consider unique passwords stored in a password manager.

No recovery. This is the most important point. There is no "forgot password" link, no master key, no backdoor. If you lose the password, the file is gone permanently. Write it down and store the note separately from the encrypted file, or use a password manager. The GPS Map Viewer can show you what location data exists in a photo before encryption — useful context for deciding how much protection you need.

What Happens to the Encrypted File

The .enc output is raw encrypted bytes. It's not an image anymore — no image viewer, no OS preview, no thumbnail will display anything. File size is nearly identical to the original (encryption adds only a small overhead for the salt and auth tag). The file can be stored on any medium, transmitted over any channel, and backed up to any cloud service without exposing the image content.

Because encryption runs entirely in your browser using the Web Crypto API, the image never leaves your device during the process. No network requests, no server processing, no temporary copies. This matters for compliance-sensitive use cases where data residency and chain of custody are requirements.

Common Questions

Can I recover an encrypted image if I forget the password? No. AES-256-GCM has no backdoor, no master key, and no recovery mechanism. The password is the only way to derive the decryption key. If you lose it, the encrypted file is permanently inaccessible. This is a security feature — it means nobody else can recover it either.

Is browser-based encryption as secure as desktop software? Yes. The Web Crypto API provides the same AES-256-GCM algorithm used by professional encryption tools. The security depends on the algorithm and key strength, not on whether it runs in a browser or a native app. The advantage here is that your file never touches a server.

What's the difference between encrypting an image and removing its metadata? Metadata removal strips identifying data (GPS, camera info, timestamps) so the photo can be shared while remaining viewable. Encryption makes the entire file unreadable without a password. Use removal for sharing. Use encryption for storage and transit of sensitive material. For best protection, do both — strip metadata first, then encrypt.

The File That Can't Be Opened

Data breaches, stolen laptops, compromised cloud accounts — these are when-not-if scenarios. The photos that survive those events unscathed are the ones that were encrypted before they were stored. Two minutes with the Image Encryption tool, a strong password, and a .enc file that nobody can open without your permission. That's the simplest form of digital security there is.