Introduction is a free opensource web app that provides secure file encryption in the browser.



The libsodium library is used for all cryptographic algorithms. Technical details here.


  • The app runs locally in your browser.
  • No data is ever collected or sent to anyone.​


  • Secure encryption/decryption of files with passwords or keys.
  • Secure random password generation.
  • Asymmetric key pair generation.
  • Authenticated key exchange.
  • Password strength estimation.


It's easy to self host and deploy, you can do that either with npm or docker

If you wish to self host the app please follow these instructions:

With npm

Before installation make sure you are running nodejs and have npm installed

  1. clone the github repository
git clone
  1. move to the folder
  1. install dependencies
npm install
  1. build app
npm run build
  1. start
npm run start

the app should be running on port 3391.

if you wish to run the app in development enviroment run :

npm run dev

With docker

You can install the app with docker in multiple ways. You are free to choose wich method you like.

  • install from docker hub

  1. pull image from docker hub
docker pull shdv/
  1. run container
docker run -p 3991:3991 shdv/

  • Build an image from source

  1. clone the github repository
git clone
  1. move to the folder
  1. build image using docker
docker build . -t shdv/
  1. run container
docker run -p 3991:3991 shdv/

  • Using docker compose

  1. clone the github repository
git clone
  1. move to the folder
  1. build image using docker compose
docker compose build
  1. run container
docker compose up

The app should be running on port 3991. is also available as a Docker image. You can find it on Docker Hub.


File Encryption

  • using a password

  1. Open
  2. Navigate to the Encryption panel.
  3. Drag & Drop or Select the file that you wish to encrypt.
  4. Enter a password or generate one.
  5. Download the encrypted file.

You should always use a strong password!

  • using public and private keys

  1. Open
  2. Navigate to the Encryption panel.
  3. Drag & Drop or Select the file that you wish to encrypt.
  4. Choose public key method.
  5. Enter or load recipient's public key and your private key. if you don't have public and private keys you can generate a key pair.
  6. Download the encrypted file.
  7. Share your public key with the recipient so he will be able to decrypt the file.

Never share your private key to anyone! Only public keys should be exchanged.

File Decryption

  • using a password

  1. Open
  2. Navigate to the Decryption panel.
  3. Drag & Drop or Select the file that you wish to decrypt.
  4. Enter the encryption password.
  5. Download the decrypted file.
  • using public and private keys

  1. Open
  2. Navigate to the Decryption panel.
  3. Drag & Drop or Select the file that you wish to decrypt.
  4. Enter or load sender's public key and your private key.
  5. Download the decrypted file.


Folder & Multiple Files Encryption

This feature is not available for security reasons. If you wish to encrypt a whole directory or multiple files then you should make a Zip and encrypt it.

File Metadata

Files encrypted with are identifiable by looking at the file signature that is used by the app to verify the content of a file, Such signatures are also known as magic numbers or Magic Bytes. These Bytes are authenticated and cannot be changed.

Safari and Mobile Browsers

Safari and Mobile browsers are limited to a file size of 1GB due to some issues related to service-workers. In addition, this limitation also applies when the app fails to register the service-worker (e.g FireFox Private Browsing).

Best Practices

Choosing Passwords

The majority of individuals struggle to create and remember passwords, resulting in weak passwords and password reuse. Password-based encryption is substantially less safe as a result of these improper practices. That's why it is recommended to use the built in password generator and use a password manager like Bitwarden, where you are able to store the safe password.

If you want to choose a password that you are able to memorize then you should type a passphrase made of 8 words or more.

Using public key encryption instead of a password

If you are encrypting a file that you are going to share it with someone else then you probably should encrypt it with the recipient public key and your private key.

Sharing Encrypted Files

If you plan on sending someone an encrypted file, it is recommended to use your private key and their public key to encrypt the file.

The file can be shared in any safe file sharing app.

Sharing the public key

Public keys are allowed to be shared, they can be sent as .public file or as text.

Never share your private key to anyone! Only public keys should be exchanged.

Storing the Public & Private keys

Make sure to store your encryption keys in a safe place and make a backup to an external storage.

Storing your private key in cloud storage is not recommended!

Sharing Decryption Passwords

Sharing decryption password can be done using a safe end-to-end encrypted messaging app. It's recommended to use a Disappearing Messages feature, and to delete the password after the recipient has decrypted the file.

Never choose the same password for different files.


Does the app log or store any of my data?

No, never stores any of your data. It only runs locally in your browser.

Is free?

Yes, is free and always will be. However, please consider donating to support the project.

Which file types are supported? Is there a file size limit? accepts all file types. There's no file size limit, meaning files of any size can be encrypted.

Safari browser and mobile/smartphones browsers are limited to 1GB.

I forgot my password, can I still decrypt my files?

No, we don't know your password. Always make sure to store your passwords in a password manager.

Why am I seeing a notice that says "You have limited experience (max file size of 1GB)"?

It means that your browser doesn't support the server-worker fetch api. Hence, you are limited to small size files. see Limitations for more info.

Is it safe to share my public key?

Yes. Public keys are allowed to be shared, they can be sent as .public file or as text.

But make sure to never share your private key with anyone!

Why the app asks for my private key in the public key encryption mode?

Because uses authenticated encryption. For verification and decryption, the recipient must provide the public key that belongs to the sender, this way can verify that the encrypted file was not tampered with, and was sent from the sender.

I have lost my private key, is it possible to recover it?

Nope. lost private keys cannot be recovered.

Also, if you feel that your private key has been compromised (e.g accidentally shared / computer hacked) then you must decrypt all files that were encrypted with that key, generate a new keypair and re-encrypt the files.

How do I generate a keypair (Public & Private)?

In the encryption panel, choose Public key mode, then you can see a button that says "Generate now", make sure to store the keys safely.

Does the app connect to the internet?

Once you visit the site and the page loads, it runs only offline.

How can I contribute? is an open-source application. You can help make it better by making commits on GitHub. The project is maintained in my free time. Donations of any size are appreciated.

How do I report bugs?

Please report bugs via Github by opening an issue labeled with "bug".

How do I report a security vulnerability?

If you identify a valid security issue, please write an email to

There is no bounty available at the moment, but your github account will be credited in the acknowledgements section in the app documentation.

Why should I use

  1. The app uses fast modern secure cryptographic algorithms.
  2. It's super fast and easy to use.
  3. It runs in the browser, no need to setup or install anything.
  4. It's free opensource software and can be self hosted.

When should I not use

  1. If you want to encrypt a disk (e.g VeraCrypt).
  2. If you want to Frequently access encrypted files (e.g Cryptomator).
  3. If you want to encrypt multiple files and directories at once (e.g Kryptor).
  4. If you want to encrypt files for another person that only they can decrypt (e.g Kryptor).
  5. If you want something that adheres to industry standards, use GPG.

Technical Details

Password hashing and Key derivation

Password hashing functions derive a secret key of any size from a password and a salt.

let salt = sodium.randombytes_buf(sodium.crypto_pwhash_SALTBYTES);
let key = sodium.crypto_pwhash(

The crypto_pwhash() function derives an 256 bits long key from a password and a salt salt whose fixed length is 128 bits, which should be unpredictable.

randombytes_buf() is the easiest way to fill the 128 bits of the salt.

OPSLIMIT represents a maximum amount of computations to perform.

MEMLIMIT is the maximum amount of RAM that the function will use, in bytes.

crypto_pwhash_OPSLIMIT_INTERACTIVE and crypto_pwhash_MEMLIMIT_INTERACTIVE provide base line for these two parameters. This currently requires 64 MiB of dedicated RAM. which is suitable for in-browser operations.
crypto_pwhash_ALG_ARGON2ID13 using the Argon2id algorithm version 1.3.

File Encryption (stream)

In order to use the app to encrypt a file, the user has to provide a valid file and a password. this password gets hashed and a secure key is derived from it with Argon2id to encrypt the file.

let res = sodium.crypto_secretstream_xchacha20poly1305_init_push(key);
header = res.header;
state = res.state;

let tag = last
  ? sodium.crypto_secretstream_xchacha20poly1305_TAG_FINAL
  : sodium.crypto_secretstream_xchacha20poly1305_TAG_MESSAGE;

let encryptedChunk = sodium.crypto_secretstream_xchacha20poly1305_push(
  new Uint8Array(chunk),

stream.enqueue(signature, salt, header, encryptedChunk);

The crypto_secretstream_xchacha20poly1305_init_push function creates an encrypted stream where it initializes a state using the key and an internal, automatically generated initialization vector. It then stores the stream header into header that has a size of 192 bits.

This is the first function to call in order to create an encrypted stream. The key will not be required any more for subsequent operations.

An encrypted stream starts with a short header, whose size is 192 bits. That header must be sent/stored before the sequence of encrypted messages, as it is required to decrypt the stream. The header content doesn't have to be secret because decryption with a different header would fail.

A tag is attached to each message accoring to the value of last, which indicates if that is the last chunk of the file or not. That tag can be any of:

  1. crypto_secretstream_xchacha20poly1305_TAG_MESSAGE: This doesn't add any information about the nature of the message.
  2. crypto_secretstream_xchacha20poly1305_TAG_FINAL: This indicates that the message marks the end of the stream, and erases the secret key used to encrypt the previous sequence.

The crypto_secretstream_xchacha20poly1305_push() function encrypts the file chunk using the state and the tag, without any additional information (null).

the XChaCha20 stream cipher Poly1305 MAC authentication are used for encryption.

stream.enqueue() function adds the signature(magic bytes), salt and header followed by the encrypted chunks.

File Decryption (stream)

let state = sodium.crypto_secretstream_xchacha20poly1305_init_pull(header, key);

let result = sodium.crypto_secretstream_xchacha20poly1305_pull(
  new Uint8Array(chunk)

if (result) {
  let decryptedChunk = result.message;

  if (!last) {
    // continue decryption

The crypto_secretstream_xchacha20poly1305_init_pull() function initializes a state given a secret key and a header. The key is derived from the password provided during the decryption, and the header sliced from the file. The key will not be required any more for subsequent operations.

The crypto_secretstream_xchacha20poly1305_pull() function verifies that the chunk contains a valid ciphertext and authentication tag for the given state.

This function will stay in a loop, until a message with the crypto_secretstream_xchacha20poly1305_TAG_FINAL tag is found.

If the decryption key is incorrect the function returns an error.

If the ciphertext or the authentication tag appear to be invalid it returns an error.

Random password generation

let password = sodium.to_base64(
return password;

The randombytes_buf() function fills 128 bits starting at buf with an unpredictable sequence of bytes.

The to_base64() function encodes buf as a Base64 string without padding.

Keys generation and exchange

const keyPair = sodium.crypto_kx_keypair();
let keys = {
  publicKey: sodium.to_base64(keyPair.publicKey),
  privateKey: sodium.to_base64(keyPair.privateKey),
return keys;

The crypto_kx_keypair() function randomly generates a secret key and a corresponding public key. The public key is put into publicKey and the secret key into privateKey. both of 256 bits.

let key = sodium.crypto_kx_client_session_keys(

Using the key exchange API, two parties can securely compute a set of shared keys using their peer's public key and their own secret key.

The crypto_kx_client_session_keys() function computes a pair of 256 bits long shared keys using the recipient's public key, the sender's private key.

The crypto_scalarmult_base() function used to compute the sender's public key from their private key.


XChaCha20 is a variant of ChaCha20 with an extended nonce, allowing random nonces to be safe.

XChaCha20 doesn't require any lookup tables and avoids the possibility of timing attacks.

Internally, XChaCha20 works like a block cipher used in counter mode. It uses the HChaCha20 hash function to derive a subkey and a subnonce from the original key and extended nonce, and a dedicated 64-bit block counter to avoid incrementing the nonce after each block.

V2 vs V1

  • switching to xchacha20poly1305 for symmetric stream encryption and Argon2id for password-based key derivation. instead of AES-256-GCM and PBKDF2.
  • using the libsodium library for all cryptography instead of the WebCryptoApi.
  • in this version, the app doesn't read the whole file in memory. instead, it's sliced into 64MB chunks that are processed one by one.
  • since we are not using any server-side processing, the app registers a fake download URL (/file) that is going to be handled by the service-worker fetch api.
  • if all validations are passed, a new stream is initialized. then, file chunks are transferred from the main app to the service-worker file via messages.
  • each chunk is encrypted/decrypted on it's own and added to the stream.
  • after each chunk is written on disk it is going to be immediately garbage collected by the browser, this leads to never having more than a few chunks in the memory at the same time.



  • Fixed navigation bug that lead sometimes to duplicate functions which caused increased encrypted file size. (CRITICAL)
  • Documentation enhancement.
  • Bug fixes and code review.


  • End to End testing with Cypress.
  • OS-level virtualization with Docker.
  • Show notification when copy to clipbaord.
  • Documentation enhancement.
  • Bug fixes and code review.


  • Adding asymmetric key cryptography.
  • Adding a key pair generator.
  • Create shareable links that contain sender's public key.
  • Possibility to choose encryption methods.
  • Hide encryption passwords by default
  • Removal of idle timer.
  • File validation checks are now performed before passwords entry.
  • Documentation enhancement.
  • Bug fixes and code review.


  • stable release of v2.
  • code review and minor bug fixes.


  • Fix file name bug in decryption download.
  • Implementing the password strength checker using zxcvbn.
  • Adding a password generate button inside the password field in the encryption panel.
  • Adding a password visibility button (on/off) inside the password field in the decryption panel.
  • About page redesign (documentation).
  • Idle timer fixes.
  • Detect if the file was decrypted using an old version of (v1).
  • Safely encode file names passed to SW.
  • Update node.js to the newest version.
  • Adding the changelog file to github.


  • Fix critical bug with useEffect that leads to increased file output size.
  • Programming the markdown file parser for the documentation.
  • Creating the About page.
  • Implementing an idle timer where user gets notified when they are inactive with app, where they are asked to reload the page.
  • Panel redesign.
  • Redesigning the Browse Button.
  • Adding an emoji on the homepage.
  • Removal of extra code comments.


  • Code review.
  • Removal of unwanted lines of code.
  • Comments cleanup.


  • Bug fixes.
  • Changing the whole UI design.
  • Improved File Validation.
  • Improved Password Validation.
  • Implementing a Stepper like design where the user has to go through steps to finish the encryption/decryption.
  • Safari and Mobile users are now limited to 1GB file.


  • A lot of bug fixes and code cleaning.
  • Adding support to Safari and Mobile browsers.


  • bug fixes.
  • Switching to React (next) instead of vanilla javascript.


  • The birth of v2 beta where it introduced in-browser memory efficient large file chunked encryption using streams with libsodium.js and switching algorithms to xchacha20poly1305 and argon2id.