The cipher that decodes itself
ROT13 shifts every letter 13 positions forward in the alphabet. A becomes N. B becomes O. N becomes A. Since the English alphabet has 26 letters, applying it twice gets you back to the original. So encoding is decoding. There’s no separate decrypt step.
“Hello World” becomes “Uryyb Jbeyq”. Paste “Uryyb Jbeyq” back in and you get “Hello World” again. Numbers, spaces, and punctuation? Untouched. Case preserved.
Let me be clear: this is not encryption. It’s obscuration. Anyone who recognizes ROT13 (and most tech-literate people do) can decode it instantly. But that’s kind of the point.
What it does
- Shifts A-Z letters by 13 positions, self-reversing, so one function handles both encoding and decoding
- Preserves case (uppercase stays uppercase, lowercase stays lowercase)
- Leaves numbers, spaces, punctuation, and symbols unchanged
- Output appears instantly as you type
- One-click copy
- All processing in your browser
Using it
Type or paste your text. The ROT13 version appears immediately. Want to decode? Just paste the encoded text in, the same transformation reverses it.
That’s the elegance of ROT13. One operation, both directions.
Where ROT13 actually shows up
Spoiler hiding: this is the classic use case. Post a movie spoiler on a forum and ROT13 it so people have to actively choose to decode it. The Usenet newsgroups of the 1980s standardized this convention, and it stuck.
Puzzle games: scavenger hunts, escape room clues, trivia quizzes. ROT13 is simple enough that people can decode it manually with a reference table, making it a fair puzzle rather than an impossible one.
Online communities: some forums still use ROT13 by convention for hiding answers, NSFW content descriptions, or off-topic jokes.
Teaching cryptography: it’s the perfect first cipher for students. Simple enough to understand immediately, but it introduces the concept of substitution ciphers. From here you can move to Caesar ciphers with arbitrary shift values, then to Vigenere, then to modern encryption.
Email address obfuscation: encoding email addresses to reduce scraping by bots. Provides basically zero real protection, but it’s a common practice anyway.
For actual security, the kind where someone can’t just reverse your encoding on the spot, use the Text Encryption tool, which does AES-256-GCM. Real encryption, not a party trick.
For other encoding methods, check out Morse Code and Binary Text on Toolsvu.
FAQ
Is ROT13 secure?
Not even slightly. It’s a trivial cipher. Anyone can reverse it by applying the same transformation. It’s for obscuring text (hiding spoilers, for example), not for protecting anything.
Does it change numbers?
No. Only letters A-Z and a-z get shifted. Everything else passes through unchanged.
How do I decode ROT13 text?
Apply ROT13 again. Shift by 13 + shift by 13 = shift by 26 = back to the original. No separate decode needed.
Where did ROT13 come from?
Usenet newsgroups in the early 1980s. People needed a way to hide spoilers and offensive content that was trivially reversible. ROT13 became the standard because it was dead simple and self-reversing. The name literally means “rotate by 13 places.”
Is my text stored?
No. All processing happens in your browser. Nothing sent anywhere.