Local Text & File Encryptor

Encrypt text or files with a passphrase, then decrypt authenticated packages when needed.

Workspace

Keep the passphrase separate.The same passphrase is required to decrypt. It cannot be recovered if lost.

Encrypt text or a file

AES-256-GCM protects confidentiality and detects package changes.

Use a long, unique phrase; 12+ characters is recommended.

Package format

EBURPENC version 1 uses a random 16-byte salt, PBKDF2-HMAC-SHA-256 with 600,000 iterations, a random 12-byte nonce, and AES-256-GCM with a 128-bit authentication tag. The fixed header is authenticated as additional data. Filename, file type, and content are encrypted together.

Guide

How to use

  1. Choose Text or File, enter the content, and create a long unique passphrase.
  2. Confirm the passphrase and encrypt to create a versioned .eburpenc package.
  3. Keep the package and passphrase separately. Both are required for recovery.
  4. To decrypt, choose the package, enter the same passphrase, and copy the text or download the restored file.
Help

Frequently asked questions

Which encryption does this tool use?

Version 1 packages use AES-256-GCM authenticated encryption. A 256-bit key is derived from the passphrase with PBKDF2-HMAC-SHA-256, a random salt, and 600,000 iterations.

Why is authenticated encryption important?

AES-GCM both encrypts the content and detects changes. Decryption fails if the passphrase is wrong or the authenticated package has been altered.

Can I recover a forgotten passphrase?

No. There is no account, recovery key, or back door. Keep the passphrase somewhere safe and separate from the encrypted package.

Does symmetric encryption use the same secret?

Yes. The same passphrase-derived secret key is required for encryption and decryption. Anyone with the package and passphrase can recover its contents.

Is the filename hidden?

Yes. For file packages, the original filename and MIME type are inside the authenticated ciphertext rather than the visible package header.