Encrypt your .env file online

AES-256-GCM vault, byte-identical to the CLI. The vault updates live as you type, and your plaintext and key never leave this tab.

Free tool · Updated August 2026 · No account required

How It Works

1

Add your .env and a key

Paste the file, then use a 64-char hex key, a raw 32+ byte string, or a passphrase.

2

Read the live vault

The # envy:v1 vault builds in real time with AES-256-GCM and a fresh random nonce.

3

Copy or download

Save .env.vault, commit it to Git, and share the key out-of-band.

Env encrypt

Live encryption, 100% in your browser

.env
5 lines · 109 chars runs locally in your browser
Secret key
256-bit hex key Anyone with this key can decrypt the vault. There is no recovery.

Algorithm

AES-256

Mode

GCM

Key strength

256-bit

Keys stored

0

.env.vault

Add a .env and a secret key above and the vault appears here.

Encrypted locally

Even golive.ly cannot read this vault without your key

4 keys encrypted · 256-bit hex key

Runs locally in your browser

Why encrypt .env files before committing to Git?

Plaintext .env files in Git leak secrets forever.

  • Deleting a file does not remove it from history
  • Every clone and every CI run exposes the same secrets
  • Rotating keys after a leak is expensive and slow

Encrypting the file gives you versioned config without exposing keys. Only someone holding the key can read it, and the key never touches the repo.

How .env encryption with AES-256-GCM works

  1. The tool derives a 256-bit key from your secret.
  2. It generates a fresh random nonce for every encryption.
  3. It writes # envy:v1 followed by base64(nonce + ciphertext).
  4. GCM authenticates the data, so tampering is detected on decrypt.

Decrypt with the CLI via envy decrypt, or generate key material with the secret generator.

Frequently Asked Questions

Common questions about encrypting .env files

No. Encryption happens entirely in your browser with the Web Crypto API. Your key never leaves this tab and is never transmitted to any server.