Is ROT13 secure?
No. ROT13 provides zero cryptographic security. It is a fixed substitution cipher with no key — anyone who knows the algorithm (which is public) can decode it instantly. Never use ROT13 to protect passwords, personal data, source code secrets, or anything that needs real confidentiality. For genuine encryption use AES-256-GCM, ChaCha20-Poly1305, or another modern authenticated cipher with a properly managed key.
Why is ROT13 self-reversible?
The English alphabet has 26 letters and 13 is exactly half. Rotating a letter forward by 13 and then forward by 13 again moves it 26 positions — back to the original. This means encoding and decoding are the same operation, which is why the tool only needs a single Apply button.
What is ROT13 used for today?
ROT13 is used to lightly obscure text where the goal is to prevent accidental reading rather than to protect secrets — spoiler tags on Usenet and forums, joke punchlines, puzzle hints, geocaching coordinates, and CTF (capture-the-flag) warm-up challenges. It is also a teaching tool for introducing substitution ciphers and modular arithmetic.
Does ROT13 work on numbers and punctuation?
No. Standard ROT13 only transforms the 26 letters A–Z and a–z. Digits, punctuation, whitespace, and non-Latin Unicode characters pass through unchanged. A variant called ROT47 covers more printable ASCII characters but is rarely used outside of niche puzzles.
Where did ROT13 come from?
ROT13 became famous on Usenet in the 1980s as a convention for hiding spoilers, offensive jokes, and puzzle answers. The newsreader software included a built-in ROT13 toggle so readers had to deliberately reveal the text. The technique itself is just a Caesar cipher with shift 13 — the underlying idea is over 2,000 years old.
Is my text uploaded to your server?
No. The ROT13 transformation runs entirely in your browser via JavaScript. Nothing leaves your device — you can verify by opening DevTools → Network and clicking Apply ROT13. No requests fire.
Can ROT13 be combined with real encryption?
No — applying ROT13 before or after a modern cipher adds zero security and only wastes CPU. Modern ciphers like AES-GCM are designed to handle arbitrary plaintext; obscuring it first does not strengthen them. If you need confidentiality, use the cipher correctly with a strong key and a unique nonce.
How is ROT13 different from a Caesar cipher?
ROT13 is a Caesar cipher with the shift hard-coded to 13. A general Caesar cipher accepts any shift from 1 to 25, so it has 25 possible keys (still trivially breakable by brute force). The shift of 13 is special only because it makes the cipher self-inverse.