Short answer: to unlock a batch of password protected images, upload the locked ZIP to a browser-based unlocker, type the password you used when locking it, and download the decrypted images. If the tool runs on the Web Crypto API, everything happens on your device and nothing is uploaded.

That is exactly how Bulk Image Unlocker works. In this post I will explain the idea, show the core of the decryption logic, and list the limits so you know what to expect.

What problem does it solve?

Sometimes you want private photos locked so that only you can open them. Maybe you share a computer, send files through a messenger, or store backups in the cloud.

The usual way to unlock them again is another online tool. That means uploading the files, and often the password, to a stranger's server. For private photos, that defeats the purpose.

So the unlocker was built around one rule: the images and the password stay in the browser.

How do you unlock password protected images?

  1. Open the Bulk Image Unlocker page.
  2. Drop in the locked .zip file.
  3. Enter the password you used when you locked the images.
  4. Click unlock and wait for the progress to finish.
  5. Check the thumbnail previews.
  6. Download one image directly, or use "Download All (ZIP)" for the whole batch.

Which ZIP files does it accept?

Only ZIP files created by the companion lock tool, Password Protect Images, on the same site. Inside that ZIP there is a manifest.json file that stores the settings needed to rebuild the key.

ZIP files from other tools, or ZIPs that were renamed, re-zipped or edited, will usually fail. If you see a "no manifest.json found" message, that is the most likely reason.

How does the decryption work?

Three standard pieces are involved.

Part What it does
PBKDF2 Turns your password into a 256-bit key, using the salt and iteration count saved in manifest.json
AES-GCM Decrypts each image and checks that the data was not changed
Web Crypto API The browser's built-in crypto engine, so no custom crypto code is needed

Because AES-GCM includes an authentication check, a wrong password fails cleanly. You get an error instead of a broken or garbled image.

Here is a simplified version of the idea. It is not the full source, just the shape of it:

async function unlock(password, salt, iterations, iv, encryptedBytes) { const enc = new TextEncoder(); // 1. Import the password as raw key material const baseKey = await crypto.subtle.importKey( "raw", enc.encode(password), "PBKDF2", false, ["deriveKey"] ); // 2. Derive a 256-bit AES-GCM key (example parameters) const key = await crypto.subtle.deriveKey( { name: "PBKDF2", salt, iterations, hash: "SHA-256" }, baseKey, { name: "AES-GCM", length: 256 }, false, ["decrypt"] ); // 3. Decrypt. This throws if the password is wrong return crypto.subtle.decrypt({ name: "AES-GCM", iv }, key, encryptedBytes); } 

If you want to read more about these calls, the MDN SubtleCrypto documentation is the best reference.

Are my images uploaded anywhere?

No. The files are processed locally in your browser, so the images and the password stay on your device. The safest upload is the one that never happens.

Can I recover a forgotten password?

No. There is no password recovery. If the password is lost, the images cannot be unlocked. This is a normal result of real encryption, and it is also why you should keep the password somewhere safe, such as a password manager.

How many images can I unlock at once?

There is no fixed limit in the tool. Batches of hundreds should work, but bigger batches take longer, and a progress indicator shows where you are. Images are processed one after another.

Tips for the best results

  • Upload the ZIP exactly as it was created. Do not rename, re-zip or edit it.
  • Passwords are case-sensitive. Even an extra space will fail.
  • An "incorrect password" message usually means just that, not that the file is damaged.
  • If you used different passwords for different batches, test with a small batch first.
  • Unlocked images are normal, unencrypted copies. Check them first, store them safely, and only then delete the locked ZIP.

Quick summary

  • It unlocks ZIPs made by the BytePriva lock tool, nothing else.
  • It uses PBKDF2, AES-GCM and the browser's Web Crypto API.
  • Everything runs locally, with no upload and no account.
  • A lost password cannot be recovered.

Try it

You can use it free here: bytepriva.com/bulk-image-unlocker

I am still improving the tools, so if something is unclear or you have a feature idea, tell me in the comments. I read all of them.