Why ROT13 is its own inverse and other shifts are not#
The alphabet has 26 letters, and ROT13 shifts by exactly half of that — 13. Applying it twice adds 13 + 13 = 26, which wraps all the way back around to the original letter. That is the one shift value where encoding and decoding are the identical operation, which is why ROT13 tools traditionally have a single button instead of separate encode and decode modes. Any other shift needs the complementary value (shift 5 needs shift 21 to reverse it, since 5 + 21 = 26) to undo it — this tool computes that automatically for the decode direction.
What this is actually good for — and what it is not#
ROT13's traditional use is hiding a spoiler, a puzzle answer, or a punchline in plain sight in a forum post or email — readable only if a reader deliberately chooses to decode it, which discourages accidentally spoiling something for someone scrolling past. It has been used this way on Usenet and web forums for decades specifically because it is trivial and has no pretense of being secure. It provides no actual security — a Caesar cipher with any shift is broken in seconds by hand, let alone by a computer, since there are only 25 possible shifts to try. Never use this for anything that needs genuine confidentiality.
Why numbers and punctuation stay exactly as typed#
The Caesar cipher, as classically defined, only operates on the 26 letters of the alphabet — a number, a space, or a punctuation mark has no defined shift because it was never part of the original scheme. This tool leaves anything that is not an ASCII letter completely untouched, so a shifted sentence keeps its original spacing, capitalization pattern, and punctuation, only the letters themselves move.