Security
For IT and security teams. Last updated 17 November 2026
Someone sent you or a colleague a file ending in .locked.zip and a link to this site. This page explains what that file is and what happens when it is opened here.
What a locked file contains
It is an ordinary ZIP archive, stored without compression and without ZIP password protection. It holds no executable code.
README.txt: instructions for the recipient.payunlock.json: readable details the sender chose to show: file name and size, a title, the sender's name, a note, an amount, a payment link, the time of locking and the SHA-256 checksum of the original file. After unlocking, the page shows that checksum so the recipient can compare it with their own tools.preview.jpg: optional watermarked or blurred preview. For archives it can be a list of the file names inside. It is not encrypted.locked.bin: the original file, encrypted.
Encryption
- AES-256-GCM through the browser's built-in Web Crypto API. No custom cryptography.
- A new random 256-bit key for every file, generated in the sender's browser.
- The file is encrypted in 1 MiB chunks. Each chunk is bound to its position and to a hash of
payunlock.json, so chunks cannot be reordered or removed, and the readable details cannot be edited without the unlock failing.
Where it runs and what leaves the device
- Locking and unlocking run entirely in the browser. The file, its name, the key and the readable details are never sent to payunlock.io or anywhere else.
- The site is static files plus one endpoint. The page sends anonymous usage counts to
payunlock.io/api/e(for example "a file was unlocked"), described on the privacy page. - No third-party scripts, fonts, analytics or cookies. The Content-Security-Policy header allows scripts and connections from this origin only.
- The scripts that do the work are not minified and can be read directly: core.js (file format and encryption) and app.js (the page). PDF previews use a bundled copy of pdf.js.
The key and the unlock link
- We never receive the key and cannot recover it.
- An unlock link carries the key after the
#. Browsers do not send that part of an address to the server, and the page removes it from the address bar after reading it. - The link is as private as the channel it travels through. If it is sent by email or chat, those systems, including link-rewriting mail security gateways, can see it.
What PayUnlock does not do
- It does not scan files. The unlocked file is whatever the sender locked. Treat it like any attachment from that sender and check it with your own tools after unlocking.
- It does not verify the sender. The name shown is what the sender typed.
- It does not handle or check payments. A payment link shown with a file was added by the sender. Pay only someone you know and expect an invoice from.
- It does not control the file after unlocking. It is a normal file from then on.
Hosting and contact
The site is served by Cloudflare. It is run by Marek Černevič, a sole proprietor in Vilnius, Lithuania. Report a security problem or misuse to hello@payunlock.io.