ROT13 Encoder & Decoder
Apply the ROT13 or ROT47 Caesar cipher to any text. ROT13 is its own inverse — the same operation both encodes and decodes.
ROT13 shifts each letter 13 positions in the alphabet. Non-letter characters are unchanged. Applying it twice restores the original text.
ROT47 shifts all printable ASCII characters (33–126) by 47 positions, including letters, digits, and symbols. Like ROT13, applying it twice restores the original.
Shift the alphabet by any number (1–25). ROT13 is shift 13. To decode, enter the same text with the inverse shift (26 − N).
Frequently Asked Questions
About This ROT13 Tool
This free ROT13 tool encodes and decodes text using the ROT13 substitution cipher, which shifts each letter 13 positions forward in the alphabet. Because the Latin alphabet has 26 letters, applying ROT13 twice returns the original text — encoding and decoding are identical operations.
ROT13 provides no real security but is used to hide spoilers in forum posts, obscure mildly sensitive content, and as a simple programming exercise. Non-letter characters pass through unchanged.
When to use this tool
- Hiding spoilers or puzzle solutions in forum posts
- Decoding ROT13-obfuscated text found online
- Understanding simple substitution ciphers
- Programming exercises involving character manipulation
Standards & References
How It Works
Choose a Cipher
Select ROT13, ROT47, or Custom Caesar Cipher. ROT13 rotates letters; ROT47 also rotates digits and punctuation; Custom lets you pick any shift.
Type or Paste
Enter text in the input area. The cipher is applied live as you type. Non-applicable characters (spaces, punctuation in ROT13) pass through unchanged.
Copy the Output
The ciphertext appears in the output box. To decode ROT13 or ROT47, simply paste the ciphertext back into the input — the same operation reverses it.
Common Use Cases
Spoiler Hiding
Hide movie or game spoilers in forum posts or emails using ROT13. Readers who know the convention can decode it; others see unreadable text.
Puzzle & Game Clues
Encode hints for escape rooms, treasure hunts, or ARGs using ROT13 or a custom shift. Players must know the cipher to decode the clue.
Cryptography Education
Teach the concept of substitution ciphers and why they're not cryptographically secure. ROT13 is the simplest possible example of a shift cipher.
String Obfuscation in Code
Apply ROT47 to obscure API-response strings or config values in source code comments, making them unreadable without being full encryption.
Forum & IRC Tradition
ROT13 has a long history on Usenet and IRC as a convention for voluntary content warnings. Post ROT13-encoded text when the plain version might be unwanted.
Password Obfuscation
Use a custom Caesar shift to lightly obfuscate a password hint in a notebook. Not secure storage, but better than plain text for casual note-keeping.
Related Text Tools
Related Articles
View all articles
Why ROT13's Encode Button and Decode Button Do the Same Thing — and Why That's the Point
ROT13 shifts each letter by 13, and shifting by 13 again returns you to the start — because 13 is exactly half of 26, and the English alphabet has 26 letters. This self-inverse property means "encode" and "decode" are literally the same operation, which is exactly why ROT13 became the standard for Usenet spoilers and forum answers: one button, symmetric, no separate decode tool needed. Here's the math, the variants (ROT5, ROT18, ROT47), and where self-inverse operations appear elsewhere.
ROT13 in Puzzle Design: Why Escape Rooms and ARGs Use a Cipher That's Deliberately Not Secure
ROT13 in an escape room or puzzle hunt isn't there for security — it's there because recognizing "this is a substitution cipher" IS the puzzle, and decoding it afterward is trivial by design. Here's how puzzle designers use ROT13 as a "calibration" cipher, why shift-amount discovery becomes its own puzzle layer, and ROT13's self-inverse property for spoiler-text use.
ROT13, Internet Culture, and Why Obfuscation Is Not Encryption
ROT13 is useless for security but was extensively used in Usenet for spoilers — and this illustrates the difference between obfuscation (hiding in plain sight) and encryption (computationally secure). Here's ROT13's internet history, why frequency analysis defeats simple ciphers, and what makes modern encryption actually work.
From Caesar Cipher to AES: The History of Why Substitution Ciphers Fail
ROT13 is a specific case of the Caesar cipher, which was broken by frequency analysis described in 800 AD. Here's the history from Caesar to Vigenère to Enigma to AES — and what each cipher's failure revealed about what real security requires.
ROT13 Encoder — Encode & Decode Text Instantly with the Classic Cipher
Learn how ROT13 works, why it was invented for spoiler protection, how it differs from real encryption, and the variations (ROT5, ROT18, ROT47) — with a free ROT13 encoder/decoder tool.