Data Encryptor
NewEncrypt and decrypt text using AES-256-GCM with PBKDF2 key derivation — all client-side.
AES-256-GCM with PBKDF2 (SHA-256, 100,000 iterations). The IV is prepended to the ciphertext before Base64 encoding.
Frequently Asked Questions
Is the Data Encryptor secure?
Yes. All cryptographic operations use the browser's built-in Web Crypto API, a FIPS-approved implementation. Everything runs client-side — no keys, passwords, or tokens are ever sent to a server.
How does encrypt work in this tool?
This tool leverages the browser's native Web Crypto API to perform encrypt operations. The algorithm executes entirely inside your browser's JavaScript engine so your sensitive data is never exposed to any external service.
What is the difference between aes and encryption?
Aes typically produces a fixed-length output that cannot be reversed, making it ideal for verification and integrity checks. Encryption is a two-way process that allows the original data to be recovered with the correct key.
Can I use Data Encryptor offline?
Yes. When you install Web Developer Toolbox as a Progressive Web App (PWA), the Data Encryptor works fully offline — the service worker caches all assets so no internet connection is required.
How long should my aes be?
Current industry best practices recommend at least 128 bits (16 bytes) for tokens and at least 256 bits for cryptographic secrets. Longer values provide significantly stronger security guarantees against brute-force attacks.