ROT13 Encoder / Decoder

What Is ROT13?

ROT13 (Rotate by 13) is a simple letter substitution cipher that replaces each letter with the letter 13 positions ahead of it in the alphabet. Because the alphabet has 26 letters and 13 is exactly half of 26, ROT13 has a unique property: it is its own inverse. Apply ROT13 to text and you get encoded output. Apply ROT13 again to the encoded output and you get the original text back. Encoder and decoder are identical operations.

Our free online ROT13 encoder handles both ROT13 and the extended ROT47 (which covers all printable ASCII characters, not just letters). Type or paste any text and the encoded version appears instantly. The Swap button lets you use the output as new input for chaining or decoding. ROT13 is not security — it is a light obfuscation convention widely used in internet communities for hiding spoilers, puzzle solutions, and opt-in content.

ROT13 History: From Usenet to Modern Communities

ROT13 emerged in the early 1980s on Usenet — the distributed discussion network that was the internet's primary social platform before the web. Usenet groups covered every topic from technical discussions to entertainment, and participants needed a simple way to mark content that some readers would want to avoid: plot spoilers, puzzle solutions, crude jokes, or information that could ruin surprises. ROT13 became the standard convention.

The choice of 13 as the shift value was no accident. A shift of 13 in a 26-character alphabet makes encoding and decoding the same operation — you only needed one implementation, one command, one mental algorithm. On text-based Usenet systems, this was practically convenient. The convention spread, became cultural, and persists today on Reddit, Discord, and forums that carry the internet cultural traditions of the Usenet era.

ROT13 vs ROT47: When to Use Each

ROT13 transforms only letters (A–Z and a–z), leaving digits, spaces, and punctuation unchanged. This means a ROT13-encoded message like "Gur sbyybj-hc vf ng 9:30 PM, ebbz 101" still reveals that it contains a time (9:30 PM) and a room number (101) to a reader who does not decode it. Only the letters are hidden. ROT47 extends the transformation to all 94 printable ASCII characters (!, ", #... through ~), including digits and punctuation. The same message in ROT47 would hide the time and room number too.

For pure text spoilers where only the words matter, ROT13 is sufficient and more recognizable. For content where numeric or symbolic information should also be obfuscated, ROT47 is more thorough. Note that space (ASCII 32) is outside ROT47's range and is preserved unchanged — word boundaries remain visible in ROT47 output even when the letters and digits are scrambled.

The Mathematics of Self-Inverse Ciphers

The self-inverse property of ROT13 comes from modular arithmetic. The English alphabet has 26 letters, indexed 0–25. ROT13 adds 13 to each index modulo 26. Applying ROT13 twice adds 13 twice: (index + 13 + 13) mod 26 = (index + 26) mod 26 = index mod 26 = index. The number 26 mod 26 = 0, so adding 26 is the same as adding nothing — the original index is recovered.

ROT47 works by the same logic with a 94-character range and shift of 47. Since 47 × 2 = 94 and 94 mod 94 = 0, applying ROT47 twice returns to the original. The only general shift values with this property are 0 (trivial — no change) and half the range size. ROT13 (half of 26) and ROT47 (half of 94) are special because of this arithmetic. A Caesar cipher with any other shift requires different operations for encoding and decoding.

ROT13 in Cybersecurity and CTF Challenges

ROT13 is a classic beginner challenge type in CTF (Capture the Flag) competitions. Participants receive encoded text and must identify and reverse the encoding to find the flag. ROT13 recognition comes with experience — the letter frequency and word structure of English are preserved (only shifted), so experienced players often recognize ROT13 output on sight. Common tells: the word "gur" (= "the"), single-letter words "n" (= "a") or "V" (= "I").

For CTF beginners: when you see scrambled text that looks like it might be English with all letters systematically replaced, try ROT13 first before more complex analysis. After ROT13, try base64 decoding, then hex decoding, then more exotic encodings. ROT13 appears in beginner CTF categories like "cryptography easy" and "miscellaneous" — it is a gateway challenge to more complex substitution and transposition ciphers.

Implementing ROT13 in Code

ROT13 is a standard programming exercise that appears in coding courses and interview preparation. The algorithm: for each character, check if it is a letter. If it is in the first half (A–M or a–m), add 13 to shift it forward. If in the second half (N–Z or n–z), subtract 13 (equivalently, add 13 and take mod 26). Non-letters pass through unchanged.

Python treats ROT13 as a first-class codec: codecs.encode(text, 'rot_13') uses the built-in implementation. Unix/Linux systems include ROT13 via tr: echo text | tr 'A-Za-z' 'N-ZA-Mn-za-m'. JavaScript, Java, and C all implement it straightforwardly with character arithmetic. Implementing ROT13 from scratch teaches character encoding, modular arithmetic, ASCII values, and string manipulation — exactly the concepts a beginner programmer needs to internalize.

Spoiler Culture and Community Norms

The social convention around ROT13 is as interesting as the technical mechanism. When a community adopts ROT13 for spoilers, it creates a shared protocol that requires a small amount of effort to breach — just enough to make the choice conscious. It is not security theater; everyone knows ROT13 is trivial to decode. The social meaning is: "I am flagging this as content you should only view intentionally."

Modern platforms have partly replaced ROT13 with native spoiler markup (Reddit's >!text!<, Discord's ||text||, and similar). But ROT13 persists in cross-platform contexts, in communities with strong Usenet cultural heritage, and in situations where the ROT13 encoding itself is part of the content's charm. It also remains the only spoiler convention that works in pure plain-text email, SMS, and any medium where markdown is not rendered.

ROT13 and Text Security: Clear Limitations

No discussion of ROT13 is complete without being explicit about what it cannot do. ROT13 provides zero security against anyone who wants to read the content. It is not encryption, does not require a key, and is reversible by anyone with basic knowledge of the encoding. It does not protect sensitive data, does not hide information from determined readers, and should never be used where actual data protection is needed.

For actual data security: use AES-256 for symmetric encryption, RSA or ECDSA for asymmetric encryption, bcrypt or Argon2 for password hashing, and TLS for data in transit. ROT13 is appropriate precisely for use cases where the goal is light, opt-in obfuscation rather than security — hiding content that readers might prefer to avoid accidentally, not hiding content from adversaries who want to access it. Understanding this distinction is fundamental security literacy.

Fun with ROT13: Notable Examples

Several ROT13 facts that delight programmers and internet culture enthusiasts: The sentence "Gur dhvpx oebja sbk whzcf bire gur ynml qbt" encodes "The quick brown fox jumps over the lazy dog" — the famous English pangram. "Uryyb Jbeyq" decodes to "Hello World." Some words are their own ROT13 — called "ROT13 fixed points" — though for complete words this is rare. True ROT13 word pairs (where ROT13 produces another valid English word) include: "abjurer" ↔ "nowhere", "chevy" ↔ "puryl", "terra" ↔ "green." The unix fortune command had ROT13 as a built-in option for filtering potentially offensive fortunes — demonstrating the cultural depth of ROT13 in Unix tradition.

ROT13 in Online Communities and Forum Culture

ROT13 became embedded in internet culture specifically through Usenet newsgroups in the 1980s and 1990s, and its legacy continues in modern online communities. The original purpose was entirely practical: Usenet had no spoiler-tag feature, no content warnings, and no way to hide text from readers who had not asked to see it. ROT13 provided a convention — a social contract — where posting ROT13-encoded content signaled to readers that they needed to actively choose to decode it, preventing accidental spoiler exposure.

Reddit adopted ROT13 spoiler tags in its early years before adding native spoiler-tag markup. Users in movie subreddits would encode plot details in ROT13 and note "ROT13 below" for those who wanted to discuss specifics. Communities like /r/books and /r/games developed strong ROT13 spoiler etiquette. Even today, ROT13 is used in comment threads where native spoiler markup is unavailable or unreliable.

Programming forums and communities use ROT13 for challenge answers. When a community posts a weekly coding challenge, some participants post ROT13-encoded solutions so others can check their answer without having the solution spoiled. The Stack Overflow community has discussed ROT13 extensively — it appears in answers about character encoding, Caesar ciphers, and obfuscation as a clear, well-understood example.

4chan and imageboards have a long history of ROT13 for hiding offensive or shocking content behind a decode step. The extra friction — needing to copy text and run it through a decoder — ensures only actively interested readers see the content, creating a form of opt-in that the platforms otherwise do not support.

Implementing ROT13 in Popular Programming Languages

ROT13 is a standard implementation exercise that appears in beginner and intermediate programming curricula. Each language has idiomatic approaches, and comparing them illustrates the language's string-handling philosophy.

Python: the simplest implementation uses the built-in codecs module — import codecs; encoded = codecs.encode('Hello World', 'rot_13'). Python is the only mainstream language with ROT13 as a built-in codec. Manual implementation using str.translate: table = str.maketrans('ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz', 'NOPQRSTUVWXYZABCDEFGHIJKLMnopqrstuvwxyzabcdefghijklm'); text.translate(table). This approach is efficient for bulk text processing.

JavaScript: no built-in ROT13 support, but the implementation is concise — const rot13 = str => str.replace(/[a-zA-Z]/g, c => String.fromCharCode((c <= 'Z' ? 90 : 122) >= (c = c.charCodeAt(0) + 13) ? c : c - 26)). A cleaner version using modular arithmetic: const rot13 = str => str.split('').map(c => { const code = c.charCodeAt(0); if (code >= 65 && code <= 90) return String.fromCharCode(((code - 65 + 13) % 26) + 65); if (code >= 97 && code <= 122) return String.fromCharCode(((code - 97 + 13) % 26) + 97); return c; }).join('').

Java: public static String rot13(String text) { StringBuilder sb = new StringBuilder(); for (char c : text.toCharArray()) { if (c >= 'a' && c <= 'z') sb.append((char)('a' + (c - 'a' + 13) % 26)); else if (c >= 'A' && c <= 'Z') sb.append((char)('A' + (c - 'A' + 13) % 26)); else sb.append(c); } return sb.toString(); }. The modular arithmetic approach (c - base + 13) % 26 + base is the elegant mathematical core of all ROT13 implementations.

C: void rot13(char *s) { for (; *s; s++) if (isalpha(*s)) *s = (*s & 0x20) + (((*s & 0x1f) + 12) % 26) + 1 + (*s & ~0x3f); — a compact bit-manipulation version that handles both cases simultaneously. The standard implementation uses ctype.h's isalpha() and toupper()/tolower() for clarity.

ROT13 Versus Other Text Obfuscation Techniques

ROT13 is one of many text obfuscation techniques used on the internet. Comparing it to alternatives clarifies when ROT13 is the right tool and when other approaches serve better.

Base64 encoding: encodes binary-safe data as printable ASCII characters. Unlike ROT13, base64 is not immediately recognizable as obfuscated text — a base64 string looks like random characters to most readers. Base64 is used for data transport (email attachments, data URLs) not obfuscation. Decoding base64 requires knowledge that it is base64, while ROT13 is self-identifying to programmers. Neither provides real security.

HTML entities: encoding text as HTML entities (&lt; for <, A for "A") obfuscates the source code of a web page while browsers render it normally. Used by email harvesting countermeasures — encoding email addresses as HTML entities in HTML source to defeat simple regex scrapers. Less effective against modern scrapers that parse the DOM.

Zero-width characters: inserting invisible Unicode characters (U+200B zero-width space, U+200C zero-width non-joiner) into text creates copies that look identical visually but differ at the character level. Used for digital watermarking — each copy of a document has a unique pattern of zero-width characters identifying the recipient. Completely invisible to readers, unlike ROT13 which is visibly scrambled.

Homoglyph substitution: replacing Latin characters with visually identical characters from other Unicode blocks (Cyrillic 'а' replacing Latin 'a', for example). Used for domain squatting (punycode attacks) and bypassing content filters. Visually identical to readers but detectable by character-level analysis.

ROT13's unique position: it is the only text transformation that is simultaneously obvious to technical readers (clearly encoded), reversible with a single shared tool, tradition-sanctioned by internet culture, and carries no negative connotations. It is the socially acceptable face of text obfuscation — used by convention, not deception.

Using ROT13 for Educational Cryptography Demonstrations

ROT13 is an ideal teaching tool for introducing cryptography concepts to beginners because its simplicity makes abstract concepts tangible. Starting with ROT13 and building toward modern cryptography creates a natural learning progression.

Concept 1 — Encryption and decryption: ROT13 demonstrates that encryption is a reversible transformation and decryption is the reverse process. Students immediately understand that the ciphertext "Uryyb" is not the original data, and that the key (13) plus the algorithm (Caesar shift) together produce the decryption.

Concept 2 — Key space and brute force: a Caesar cipher has 26 possible keys (ROT0 through ROT25). Brute force means trying all 26. Students can manually brute-force a short ROT13 ciphertext by trying each shift. This demonstrates why key space matters — modern AES has 2¹²⁸ possible keys, making brute force computationally impossible.

Concept 3 — Frequency analysis: take a paragraph-length ROT13 text, count the frequency of each character, and compare against known English letter frequencies (E, T, A, O, I, N, S, H, R, D). The most frequent ciphertext letter should map to E, revealing the rotation. This demonstrates that linguistic patterns survive simple substitution — a key weakness that modern ciphers address through diffusion and confusion.

Concept 4 — Symmetric vs asymmetric: ROT13 is symmetric — the same key (13) encodes and decodes. This contrasts with RSA's asymmetric approach where a public key encrypts and only the paired private key decrypts. Students who understand ROT13 can grasp why symmetric key exchange requires a secure channel, motivating the invention of public-key cryptography.

Our ROT13 tool is suitable for classroom demonstrations: students paste text, see the output, recognize the scrambled pattern, and paste the output back to verify the self-inverse property. This hands-on experience makes cryptographic fundamentals memorable and intuitive.

ROT13 Encoding in File Formats and Data Systems

Beyond text and online communication, ROT13 has appeared in specific technical contexts as a light obfuscation layer within file formats and data systems.

Configuration files: some legacy software stored sensitive-looking configuration values (passwords that were not actually secret, API keys for internal services) in ROT13 to prevent casual reading. The Microsoft .ini format has no encryption support — ROT13 was occasionally used to obscure passwords from over-the-shoulder viewers in a pre-security-conscious era. This practice is obsolete and insecure by modern standards.

Software licensing: some legacy license key verification systems used ROT13 as part of a multi-step obfuscation to make reverse engineering slightly harder. Combined with base64 and custom character substitutions, ROT13 was one layer in a weak multi-layer obfuscation scheme. Again, this provided no real security against determined reverse engineers.

Test data and fixtures: developers sometimes ROT13-encode personal or sensitive-looking data in test fixtures and seed files to prevent dummy data from looking like real data in version-controlled repositories. A seed file might contain ROT13-encoded fake email addresses ("grfg@rknzcyr.pbz" for "test@example.com") to make it clear the values are obfuscated and should not be used as real emails.

Database stored procedures: a few legacy database systems have ROT13 implemented as a stored function for use in generating obfuscated output in reports — obscuring sensitive column values in read-only reports accessible to staff who should not see raw sensitive data but need to see that data exists. Our encoder and decoder handles any text you need to work with in these contexts.

ROT13 Frequency Analysis: Why It Fails Against Cryptanalysis

One of the most valuable educational aspects of ROT13 is demonstrating why simple substitution ciphers fail against frequency analysis — the most powerful classical cryptanalytic technique. Understanding this failure mode explains why modern ciphers are designed the way they are.

In any sufficiently long English text, letters do not appear with equal frequency. The distribution is well-characterized: E appears approximately 12.7% of the time, T at 9.1%, A at 8.2%, O at 7.5%, I at 7.0%, N at 6.7%, S at 6.3%, H at 6.1%, R at 6.0%, D at 4.3%. The ten least common letters — Q, Z, J, X, K, V, W, Y, B, F — account for a combined 8.5% of letters.

When you apply ROT13 to English text, the letter frequency distribution shifts by 13 positions but is otherwise preserved. E (the most common letter) becomes R. T becomes G. A becomes N. O becomes B. An attacker who intercepts ROT13 ciphertext and counts character frequencies will find that R appears most often, G second most often, N third most often, B fourth most often. Mapping these to E, T, A, O (the known English distribution) reveals the rotation is 13, breaking the cipher in seconds without any brute force.

For longer texts (200+ characters), frequency analysis is essentially deterministic — the distribution matches the expected English frequencies closely enough to identify the rotation uniquely. For very short texts (under 20 characters), brute force is still trivial (25 rotations to try). ROT13 is breakable by either method in under a minute with no computing power.

What modern ciphers do differently: AES uses multiple rounds of substitution, permutation, and mixing operations specifically designed to destroy statistical patterns in the plaintext. After AES encryption, ciphertext characters appear with equal frequency regardless of the plaintext's language or patterns — a property called "confusion and diffusion" (Claude Shannon's terms). ROT13 has confusion (substitution) but zero diffusion — patterns in the plaintext are fully preserved in the ciphertext.

ROT13 and Content Moderation: Practical Social Media Uses

Content moderation on social platforms and community forums has adopted ROT13 and similar techniques to allow communities to discuss sensitive, controversial, or disturbing content while respecting members who wish to avoid exposure. Understanding these use cases helps community managers and content creators use our tool effectively.

Spoiler management in entertainment communities: r/gameofthrones during its original run, film subreddits during opening weekends, and book club forums regularly used ROT13 for plot discussions. The convention: post your discussion point, then encode the specific spoiler detail in ROT13. Readers who want to engage with the spoiler copy-decode it; others skip the ROT13 block. This allowed vibrant discussion threads without forcing all readers to encounter unwanted spoilers.

Trigger warning content: communities discussing trauma, mental health, abuse, or disturbing historical events sometimes use ROT13 to hide the most graphic descriptions while allowing the discussion to proceed. The ROT13 encoding acts as an explicit trigger warning — readers must actively choose to decode, signaling awareness of the content type.

Puzzle and alternate reality game (ARG) communities: ARG designers frequently embed ROT13 clues in forums, websites, and social media posts as puzzle elements. The ROT13 text is left visible, and players who recognize the pattern decode it as part of the game. Reddit's /r/SolveCult, /r/oddities, and various ARG subreddits frequently discuss ROT13 as a puzzle layer. Our encoder/decoder is the standard tool for checking potential ROT13 clues in these communities.

Discord and Slack communities: many Discord servers use ROT13 bots (simple bots that respond to !rot13 text commands) to enable community members to encode and decode text within chat. Slack does not have a built-in ROT13 command, so Slack community managers point members to web tools like ours for occasional spoiler encoding. The friction of using an external tool versus a bot command slightly reduces ROT13 usage in Slack communities versus Discord.

Optimizing Your ROT13 Workflow for Repeated Use

For users who encode and decode ROT13 frequently — community moderators, ARG players, developers testing obfuscation code — an optimized workflow saves significant time compared to repeated copy-paste to a web tool.

Browser bookmark with auto-focus: bookmark our ROT13 tool and add it to your browser's bookmark bar for one-click access. The text input auto-focuses on page load, so you can immediately start typing or paste with Ctrl+V after clicking the bookmark. Total time from intent to result: 2-3 seconds.

Custom keyboard shortcuts: on macOS, you can create a system-wide text substitution that encodes ROT13 on a trigger. In System Settings → Keyboard → Text Replacements, add "rot13:" as a trigger and the ROT13 encoding of a common phrase as a replacement. For JavaScript developers, a bookmarklet provides ROT13 inline: create a bookmark with URL javascript:void(prompt('ROT13:',prompt('Enter text:').replace(/[a-zA-Z]/g,c=>String.fromCharCode((c<='Z'?90:122)>=(c=c.charCodeAt(0)+13)?c:c-26)))).

Terminal alias for power users: add to your .bashrc or .zshrc: alias rot13="tr 'A-Za-z' 'N-ZA-Mn-za-m'". Then use: echo "Hello World" | rot13 → "Uryyb Jbeyq". Or read from clipboard on macOS: pbpaste | rot13 | pbcopy (read clipboard, ROT13, write clipboard). This workflow enables ROT13 without opening a browser tab, ideal for terminal-centric developers.

VS Code extension: the "ROT13" extension for VS Code adds a command palette entry (Ctrl+Shift+P → "Encode/Decode ROT13") that encodes or decodes selected text in-place. Ideal for developers who frequently work with ROT13 in test fixtures or code comments.

Integration into writing workflows: authors and content creators who use ROT13 for workshop spoiler management can add a ROT13 keyboard shortcut to their writing tool. In Scrivener, custom macros can be created. In Ulysses or iA Writer, the terminal alias approach (clipboard-based) is most practical. In Google Docs, a Google Apps Script can be added to the document with a menu item for ROT13 encoding of selected text.

The Cultural Legacy of ROT13 in Hacker and Open Source Communities

ROT13 occupies a unique cultural position in the hacker and open-source community — a term of art recognized by virtually every programmer, an inside joke that doubles as a practical tool, and a touchstone for discussions about the difference between security and obfuscation. Its cultural significance extends well beyond its technical simplicity.

The Jargon File (also known as "The Hacker's Dictionary"), compiled by Eric S. Raymond and a community of contributors, documented ROT13 extensively as part of hacker culture. The Jargon File defined ROT13 as "a simple caesar-cipher encryption that replaces each English letter with the one 13 places forward or back along the alphabet" and noted its primary use for "mildly offensive humor which some readers might want to avoid." The fact that ROT13 earned an entry in the definitive hacker cultural lexicon demonstrates its importance in the community's shared vocabulary.

The GNU coreutils include rot13 as a command in some distributions, and the Python standard library's codecs module has rot_13 as a built-in codec alongside actual encoding standards like UTF-8 and base64. The inclusion of ROT13 in these foundational tools reflects its cultural significance — it was implemented not because it provides practical utility that could not be achieved otherwise, but because the community expected it to be there.

Open-source software humor: ROT13 appears throughout open-source project humor. Readme files encode puns in ROT13. Code comments include ROT13 easter eggs. Variable names are sometimes ROT13 references to inside jokes. The Emacs text editor's Doctor mode (a Rogerian psychotherapy simulation) uses ROT13 internally for some response generation — an Easter egg baked into one of computing's most storied applications.

Security culture: in the information security community, ROT13 is shorthand for "trivially weak security theater." Saying "this system uses ROT13-level security" is a damning indictment of an organization's security posture. The metaphor is universally understood: ROT13 as the benchmark of minimum possible security effort. This shared reference point allows security professionals to communicate clearly about security failures without technical jargon.

ROT13 Decoder and Encoder: Tips for Accurate Results

Our ROT13 tool handles the encoding and decoding automatically, but understanding the nuances of the encoding ensures you get accurate results for edge cases and unusual inputs.

Character handling: our tool applies ROT13 to English alphabet characters (A-Z, a-z) only. All other characters — numbers, spaces, punctuation, emoji, accented characters, CJK characters — pass through unchanged. This is the standard ROT13 behavior as defined by convention. If you want to encode numbers, switch to ROT47 (available via the command line: tr '!-~' 'P-~!-O').

Newline and whitespace preservation: line breaks, tabs, and multiple spaces in your input are preserved exactly in the output. This is important for encoding multi-paragraph text — each paragraph's structure is maintained. If you are encoding a poem or a numbered list, the line structure survives intact.

Large text encoding: there is no practical size limit on text you can encode or decode with our tool. The encoding operates character by character in linear time, so very long texts (thousands of words) encode in milliseconds. For extremely large inputs (hundreds of thousands of characters), the paste and render steps may take a second, but the encoding itself is instant.

Verification: because ROT13 is self-inverse, the simplest way to verify correct encoding is to encode the output again — if you get back the original text, the encoding was correct. Paste your ROT13 output back into the input field, encode again, and compare with your original text. Any discrepancy indicates a problem with the input (perhaps a copy-paste that truncated text, or a character encoding issue in the pasted text).

ROT13 vs Base64 vs URL Encoding: Choosing the Right Text Transformation

ROT13, base64, and URL encoding (percent-encoding) are all text transformations used to represent text in a different form. Each serves a different purpose, and choosing incorrectly creates compatibility problems or unnecessary complexity.

ROT13: applies to human-readable text only. Output remains human-readable (mostly — it looks like scrambled English). Best for: spoiler hiding in text forums, educational cryptography demonstrations, cultural/community conventions. Use when: your audience is human, the content is English-language text, the goal is light optional obfuscation not security. Not for: binary data, machine-to-machine data transfer, security-sensitive content.

Base64: encodes any binary data (including text encoded as bytes) to a safe ASCII character set. Output is not human-readable. Best for: embedding binary data in JSON, XML, or HTML; email attachments (MIME); data URLs (data:image/png;base64,...); encoding arbitrary bytes for safe transport over text-only protocols. Use when: data includes binary content (images, files), the output will be processed by a machine, or you need guaranteed safe transmission across text systems. Not for: human-readable spoilers — base64 output is obviously machine-encoded and provides no opt-in convention.

URL encoding (percent-encoding): encodes special characters in URLs so they can be safely included in HTTP requests. Spaces become %20, ampersands become %26, equals signs become %3D. Best for: encoding query string parameters, encoding file names in URLs, form submission data. Use when: you are constructing URLs or HTTP requests and need to include arbitrary text in a URL component. Not for: general text obfuscation or binary data transport.

Summary decision guide: for human text that needs opt-in viewing in an online community — ROT13. For binary or arbitrary data that needs to travel through text-only systems — base64. For text that needs to be safely embedded in a URL — URL encoding. Our tool handles ROT13; use our base64 encoder for base64 needs and our URL encoder for percent-encoding.

Quick Reference: ROT13 Alphabet Substitution Table

The complete ROT13 substitution mapping for quick reference. Each letter maps to the letter 13 positions ahead in the alphabet. Because of the self-inverse property, the mapping is bidirectional — the same table encodes and decodes:

Uppercase: A↔N, B↔O, C↔P, D↔Q, E↔R, F↔S, G↔T, H↔U, I↔V, J↔W, K↔X, L↔Y, M↔Z. Lowercase: a↔n, b↔o, c↔p, d↔q, e↔r, f↔s, g↔t, h↔u, i↔v, j↔w, k↔x, l↔y, m↔z.

Reading the table: to encode "Hello", find H→U, e→r, l→y, l→y, o→b → "Uryyb". To decode "Uryyb", apply the same table: U→H, r→e, y→l, y→l, b→o → "Hello". The identical forward and reverse operation is what makes ROT13 its own inverse. All numbers, spaces, punctuation, and characters outside A-Z and a-z remain unchanged through ROT13 encoding. Our online tool applies this mapping instantly to any length of text you paste into the input field.