ROT13 Encoder / Decoder

What this tool is used for

• Hiding a spoiler, puzzle answer or punchline in a public thread so reading it takes a deliberate action.
• Recovering text someone posted rotated, which the very same operation undoes with no second mode needed.
• Demonstrating a substitution cipher where the key is fixed and the mechanism is the entire lesson.
• Producing a string that is unreadable at a glance while needing no key management whatsoever.
• Checking whether a suspicious-looking string is simply rotated rather than genuinely encrypted.

Frequently Asked Questions

Why is ROT13 its own inverse?

Because the Latin alphabet has 26 letters and 13 is exactly half. Applying it twice returns the original, so the same function both encodes and decodes — which is the entire reason it became a convention.

Is it encryption?

No, and it has never claimed to be. It is a Caesar cipher with a fixed shift and no key, breakable by inspection. Its purpose is to hide text from ACCIDENTAL reading — spoilers, punchlines, puzzle answers — not from anyone who wants it.

What happens to numbers and punctuation?

They pass through unchanged, since the rotation is defined only over A-Z and a-z. ROT47 exists to cover the printable ASCII range including digits and symbols, at the cost of producing unreadable output.

Are there words that ROT13 into other words?

Yes, and they are a small curiosity: 'abjurer' becomes 'nowhere', 'chechen' becomes 'purpura', and 'PNG' becomes 'CAT'. They exist because 13 happens to map several common letter pairs onto each other.

Where is it still used?

Usenet convention (where it originated), puzzle and CTF challenges, some forum spoiler tags, and as a joke in security contexts — 'double ROT13 for extra security' is a standing gag precisely because it does nothing.

Does it work on non-English alphabets?

No. It is defined only over the 26 Latin letters, so Cyrillic, Greek and accented characters pass through untouched. A text mixing scripts comes back partly transformed, which makes it useless as obfuscation there.

Is it the same as a Caesar cipher?

It is one — the Caesar cipher with a shift of 13, chosen because 13 is half of 26 and therefore self-inverse. Any other shift needs a separate decode step, which is precisely why 13 became the convention.

Common errors and gotchas

• Treating it as security. The key is published, the operation is public, and anybody can undo it in one step.
• Expecting digits and punctuation to change. Only the 26 letters rotate, so a number in goes a number out.
• Assuming it works on any alphabet. Accented and non-Latin letters pass through untouched, leaving a message half readable.
• Applying it twice and thinking the tool failed. Two applications return the original, since thirteen is exactly half of twenty-six.
• Using it on content that must stay hidden from a determined reader rather than an accidental one.