ToolzyLab
Encrypt plain text locally and decrypt it securely in your browser using AES-GCM with PBKDF2. No uploads. No server processing. Just fast, private text protection with a clean ToolzyLab UI.
Paste your text, choose whether to encrypt or decrypt, enter a password, and process everything fully on-device. This upgraded version has a clearer UI, better action status, smarter encrypted-input detection, strong error handling, password visibility controls, file import, output download, and cleaner analysis cards.
Two large square workspaces keep the page clean. Input stays on the left. Result stays on the right with scroll inside the box.
See which format is detected, what metadata is available, and whether your current input looks ready for encryption or decryption.
What this tool does and how to use it correctly.
Encryption is strong, but your password choice still matters a lot.
Encryption can protect text when the algorithm, authenticated mode, key derivation, random salt and nonce, password, and output package are handled correctly. Choose encrypt or decrypt, output format, PBKDF2 iterations, password confirmation, trimming, and auto-detection carefully, then test recovery before deleting any plaintext.
PBKDF2 iterations increase the cost of password guesses, while a random salt prevents identical passwords from producing identical derived keys. Iteration counts are environment-dependent and should follow current project policy. Do not reuse an account password, and send the passphrase through a separate trusted channel when sharing ciphertext.
Those parameters are not secret and can be stored in the JSON or text package, but they must remain intact. Authenticated encryption detects a wrong password or modified ciphertext instead of returning silent garbage. Pretty-printing or copy operations must not alter encoded fields.
Malicious extensions, clipboard history, screenshots, page scripts, downloaded plaintext, and device malware can still capture content. Review loaded third-party libraries and organizational policy before processing sensitive data. Use established encrypted messaging, password managers, or approved storage systems for operational secrets.
Prove that the exact exported package can be decrypted before relying on it.
Technical references: OWASP cryptographic storage guidance MDN Web Crypto overview
No. Base64 only represents bytes as readable characters. Encryption uses a secret key to provide confidentiality and should also authenticate the ciphertext.
They make deriving a key from each password guess more expensive. The suitable count depends on current policy, device performance, hash choice, and compatibility.
Usually no, but they must be random or unique as required and stored accurately with the ciphertext. Reuse rules depend on the encryption mode.
Capitalization, whitespace, Unicode, output corruption, missing parameters, or a different KDF setting can change the key. Use the exact password and complete package.
No. Strong encryption is designed to prevent recovery without the correct key. Keep a secure passphrase record and test decryption before removing plaintext.
It can be useful for controlled local tasks, but device compromise, extensions, clipboard exposure, dependencies, and policy matter. Prefer an approved key-management and encrypted-storage system.