Encrypt and decrypt text using DES (Data Encryption Standard) and Triple DES algorithms.
Triple DES (3DES) strengthens the original Data Encryption Standard by applying the DES block cipher three times to each 64-bit block, giving a much larger effective key than single DES. This tool encrypts and decrypts text with Triple DES in CBC mode using PKCS7 padding and a 192-bit key. It is a symmetric cipher, so the same passphrase both encrypts and decrypts your message.
Single DES, with its 56-bit key, is considered insecure and can be brute-forced with modern hardware, so it is intentionally not offered here — only the stronger Triple DES variant. Everything runs locally in your browser: your passphrase is stretched into a key with PBKDF2 (SHA-256, 250,000 iterations) over a fresh random salt, and a new random IV is generated for every encryption so the same input never produces the same output twice. The salt and IV are prepended to the ciphertext and the whole blob is Base64-encoded, so nothing you type is ever uploaded.
Triple DES is legacy technology. It remains widely encountered in older financial systems and hardware, which is why a tool like this is useful for interoperability, but it is slow and has a small 64-bit block size that limits how much data can safely be encrypted under one key. For any new system you should prefer AES, which is faster and more secure. Use this tool to work with existing 3DES data or to learn how the cipher behaves, not to protect new high-value secrets.
Triple DES is far stronger than single DES but is now considered legacy. Its small 64-bit block size limits safe usage, and it is slower than modern ciphers. For new systems, prefer AES.
Single DES uses a 56-bit key that can be brute-forced with modern hardware, so it is insecure. This tool intentionally offers only the stronger Triple DES variant.
Mainly for interoperability with older systems — some financial, payment, and legacy hardware platforms still rely on Triple DES — or to learn how block ciphers work.
No. Key derivation, encryption, and decryption all run locally in JavaScript, so your passphrase and plaintext never leave your device.
No. A random salt and IV are generated per encryption and prepended to the ciphertext, so decryption only needs the same passphrase you used to encrypt.