Encrypt & Decrypt Text Online with AES-256-GCM (Zero Knowledge)
Lock sensitive notes, seed phrases, and credentials using native browser WebCrypto AES-256-GCM with 250,000 PBKDF2-SHA256 iterations.
Step-by-Step Client-Side Workflow
- Enter Secret Plaintext & Passphrase: Type the confidential message or credentials you want to seal and choose a strong passphrase.
- Execute Hardware WebCrypto Encryption: Your browser generates a random 128-bit salt and 96-bit IV, derives a 256-bit key via PBKDF2, and seals the payload.
- Share Self-Contained Ciphertext Bundle: Send the Base64 ciphertext safely over Slack or email; only someone with the passphrase can decrypt it.
Why Use VaultTools Zero-Upload Architecture
- True Zero-Knowledge Cryptography: Neither your passphrase nor your plaintext ever leaves your device. Even over untrusted chat channels, your armored ciphertext stays safe.
- Tamper-Proof GCM Authentication: AES-GCM guarantees both confidentiality and integrity—if a single byte of ciphertext is altered, decryption immediately alerts you.
- Instant Local File Checksums: Verify multi-megabyte installers or legal PDFs against published SHA-256 hashes without uploading files.
Frequently Asked Questions
Why is AES-256-GCM superior to older AES-CBC online tools?
AES-GCM (Galois/Counter Mode) provides authenticated encryption with associated data (AEAD). It appends a 128-bit authentication tag that detects any tampering or wrong passphrase immediately.
Can VaultTools recover my encrypted text if I forget the passphrase?
No. Because encryption happens 100% client-side with zero key escrow, there is no backdoor—only your exact passphrase can unlock the ciphertext.
Can VaultTools recover my encrypted text if I forget the passphrase?
No. Because encryption happens 100% in your browser using AES-256-GCM with no server or key escrow, there is no backdoor. Only someone with the exact passphrase can decrypt the payload.
Why does encrypting the same text twice produce different ciphertext?
Every encryption generates a brand-new random 16-byte salt and 12-byte IV via window.crypto.getRandomValues(), preventing rainbow-table and replay attacks.