The Text Encryptor uses Web Crypto AES-256-GCM. It derives a key with PBKDF2-SHA256, 600,000 iterations, a fresh 16-byte salt and a fresh 12-byte nonce for each encryption.
Try a harmless round trip
Enter a test message and a passphrase of at least twelve characters. Encrypt and save the complete JSON envelope. Switch to decrypt, paste the envelope and enter the same passphrase. The original Unicode text should return exactly. An incorrect passphrase or modified ciphertext should produce an error rather than plausible garbage.
What to save
The envelope includes version, algorithm identifiers, iteration count, salt, nonce and ciphertext. Keep these together. Salt and nonce are not passwords; the passphrase is the secret. Store it separately rather than sending it alongside the encrypted message through the same channel.
Repeated encryption of identical input produces different envelopes because fresh randomness is used. That does not change the recovered plaintext.
Limits that still matter
Encryption cannot protect text already exposed on a compromised device. Weak or reused passphrases remain vulnerable to guessing; the minimum length check is not a strength guarantee. There is no key-recovery service. Legacy XOR output from the previous implementation is not a v1 authenticated envelope.
Do not paste messages or keys into the separate AI assistant. See MDN Web Crypto documentation for authenticated encryption. This is a local utility, not an audited secret-management system.