Text Encryptor

Three separate things live behind these tabs: genuine AES encryption with a passphrase, Base64 encoding that anyone can undo, and ROT13, a letter rotation that hides nothing.

What is the Text Encryptor?

Only one of the three modes is cryptography, and the page is better used with that understood. The AES tab runs the CryptoJS library in passphrase mode, which derives a key and an initialization vector from whatever sits in the Secret Key field using the legacy OpenSSL derivation, encrypts in CBC mode, and returns an OpenSSL-style Base64 block beginning with U2FsdGVk. That is real AES, but the key stretching is a single old-fashioned pass rather than a modern slow function, and the output carries no authentication tag, so it will keep a note from a casual reader and should never hold passwords, financial records or anything whose exposure would genuinely hurt. Base64 offers no secrecy whatsoever, and ROT13 is a fixed thirteen-place letter shift that any reader reverses by applying it a second time.

Key Features

• AES tab encrypts with a passphrase you choose, and decrypts back
• Base64 encode and decode that handle accented and non-Latin characters correctly
• ROT13 tab converts live as you type, with no button
• Swap buttons move an AES or Base64 result back into the input
• A separate copy button sits under each of the three outputs

Common Use Cases

• Wrapping a note in a passphrase before pasting it into a shared document
• Decoding a Base64 blob pulled from a config file, token or data URI
• Hiding a puzzle answer or plot spoiler behind ROT13 in a forum post
• Teaching a class the difference between encoding, classical ciphers and real encryption

How to Use the Text Encryptor

1. Choose the AES Encryption, Base64 or ROT13 tab across the top of the tool.
2. In AES mode, replace the prefilled Secret Key with a passphrase of your own before anything else.
3. Type or paste your message into the input box for the mode you selected.
4. Press Encrypt or Decrypt in AES mode, Encode or Decode in Base64 mode; ROT13 updates by itself.
5. Copy the output, and record the AES passphrase somewhere safe, because nothing here can recover it.

Tips for Best Results

• The Secret Key field ships with a sample passphrase, and leaving it in place offers no protection at all.
• Clearing the key entirely falls back to the literal word default, which is worse than the sample.
• Encrypting the same message twice yields different ciphertext, because a fresh random salt is generated.
• A wrong passphrase produces an error message rather than plausible text, so a failed decrypt is obvious.

Why Use WiserWork's Text Encryptor?

Plenty of pages promise encryption and quietly deliver Base64. Putting all three methods on one screen, clearly labeled, makes the hierarchy visible: ROT13 is a party trick, Base64 is a transport format, and AES with a strong passphrase is the only one of the three that resists someone determined to read your text. Your message and your key are processed by JavaScript inside the page and are never sent to a server, although the AES tab does load the CryptoJS library from a public CDN when the page opens.

Who Uses the Text Encryptor?

Developers who need to decode a Base64 payload without opening a terminal, forum regulars posting ROT13 spoilers, and students learning exactly where the line between encoding and encryption falls. People sometimes use the AES tab to obscure a note inside a shared file, which is reasonable for low-stakes text and unwise for credentials.

Frequently Asked Questions

Is Base64 a form of encryption?

No. Base64 is a reversible encoding built to move binary data through text-only channels. Anyone who recognizes the output can decode it in seconds, including with the Decode button on this page.

How strong is the AES mode?

The cipher itself is standard AES in CBC mode through the CryptoJS library. The weakness is key handling: the passphrase is stretched with the legacy OpenSSL derivation instead of a modern slow function, and there is no authentication tag, so it suits casual privacy rather than valuable secrets.

What happens if I leave the Secret Key box empty?

The code falls back to the literal string default. Anyone aware of that can decrypt your output instantly, so always set a passphrase of your own.

Why does the same text produce different ciphertext each time?

A fresh random salt is generated for every encryption and embedded in the output, so identical inputs give different Base64 blocks. All of them decrypt with the same passphrase.

Can I recover my text if I forget the passphrase?

No. Nothing is stored and there is no reset path, so a forgotten passphrase leaves the ciphertext permanently unreadable.

What does the U2FsdGVk prefix on the output mean?

It is the Base64 rendering of the bytes Salted__, the OpenSSL container marker that precedes the random salt. It signals that the output came from an OpenSSL-compatible passphrase encryption.

Is ROT13 secure in any sense?

Not at all. It shifts each letter thirteen places, and because the alphabet holds twenty-six letters, applying it again restores the original. It exists to hide spoilers from a casual glance.

Does ROT13 change numbers or punctuation?

No. Only the characters A to Z and a to z are rotated. Digits, spaces, punctuation and accented letters pass through untouched.

Does my text or key leave the browser?

No. Encryption, encoding and rotation all run in page JavaScript. The page fetches the CryptoJS library from a public CDN when it loads, but nothing you type is ever sent anywhere.

Can I decrypt ciphertext produced by another AES tool?

Only if that tool used the same OpenSSL-compatible passphrase format CryptoJS produces. Output from a tool that takes a raw key and a separate initialization vector will not decrypt in this tab.

Treat the three tabs as three different jobs: rotate letters to hide a spoiler, encode Base64 to move text through a channel that expects plain characters, and reach for AES with a real passphrase only when the content genuinely warrants it.