CodeKitHubWhat Is This Tool?
ROT13 ("rotate by 13 places") replaces every letter with the one 13 positions further along the alphabet, wrapping back to the start after Z. A becomes N, B becomes O, and so on. Numbers, punctuation and spaces are left untouched.
It provides zero real security — it's not encryption, just obfuscation. Its actual use case has always been social, not cryptographic: hiding a spoiler or joke punchline from your eyes until you deliberately choose to decode it, common on old Usenet groups and puzzle forums.
Why Use It?
- Hide (and reveal) spoilers, puzzle answers, or joke punchlines in forum posts and messages.
- Encode and decode are the same operation — paste ROT13'd text back in to get the original.
- Instant, works on any length of text.
- 100% private: your text is transformed locally, nothing is uploaded.
- Free, no sign-up, no character limit.
How to Use
- Paste or type your text into the input box.
- Click "Apply ROT13".
- Copy the result — to reverse it later, paste that result back in and click the button again.
Example
Input
Hello, World!Output
Uryyb, Jbeyq!Running "Uryyb, Jbeyq!" through the same tool again returns "Hello, World!" exactly — that's the whole point of ROT13 being its own inverse.
Practical tips
- To hide a spoiler in a forum post, ROT13 it and add a note like "(ROT13'd: spoilers)" so readers know it's deliberate, not garbled text.
- ROT13 preserves case: uppercase letters stay uppercase after shifting, lowercase stays lowercase.
- If you need actual security (protecting something from a motivated reader), ROT13 is the wrong tool entirely — use real encryption instead.
- Because it's self-inverse, you never need to remember whether a piece of text is "already encoded" — running it through twice always gets you back to plain text.
ROT13 vs other simple ciphers
ROT13 is a special case of the general "Caesar cipher" (any fixed letter shift), and it's the only shift amount that's its own inverse — ROT1 through ROT25 all require a separate decode step with the opposite shift, which is exactly why ROT13 became the standard for casual text obfuscation instead of any other shift value.
If you're working with actual encoded data formats rather than a text obfuscation trick, Base64 encoding and hashing serve a genuinely different purpose (representing binary data as text, and creating one-way fingerprints, respectively) and aren't reversible the way ROT13 is.
Frequently Asked Questions
Is ROT13 secure? Can someone crack it?
No — ROT13 provides no real security at all. There are only 26 possible letter shifts, and ROT13 specifically has no key to guess; anyone who recognizes ROT13 text can decode it instantly, by hand or with any ROT13 tool. It was never designed to keep a determined reader out, only to require a deliberate extra step before reading (which is exactly its point for spoilers).
Why does the same button both encode and decode?
Because 13 is exactly half of the 26-letter alphabet, shifting forward by 13 twice lands you back where you started (13 + 13 = 26 = a full loop). That makes ROT13 a self-inverse (also called an "involution") — applying it once encodes, applying it again on the result decodes, with no separate mode needed.
Why doesn't ROT13 touch numbers or punctuation?
The classic ROT13 algorithm only maps the 26 Latin letters. Numbers, spaces, and punctuation pass through completely unchanged, which is why "Hello, World!" keeps its comma and exclamation point after conversion.
What's ROT13 actually used for today?
Mostly the same thing it's always been used for: hiding spoilers, puzzle solutions, or joke punchlines in forum posts, comment sections and README files, so a reader has to make a small deliberate choice to decode and see it rather than reading it by accident.
Does this tool store or send my text anywhere?
No. The letter-shifting happens in JavaScript running in your browser. Nothing you type is uploaded, logged, or sent to a server.