ROT13 Encoder

What ROT13 Encoder helps you do

Apply ROT13 to letters or ROT47 to printable ASCII, two simple substitution ciphers that are each their own inverse. Because applying the same operation twice restores the original, the same tool encrypts and decrypts. It is an obfuscation trick, not a security measure.

The cipher is applied locally in your browser; no text is transmitted to Haivix.

How it works

These tools transform characters rather than meaning. Some map letters to other Unicode glyphs, some insert combining marks, and some encode bytes into a text-safe representation. The result is still text, so it can be copied into a document or chat, but the visual effect depends on the font and platform that renders it. Nothing is uploaded, and some transformations are not reversible; keep the original when that matters. The output is a snapshot of the pasted text, so changing the source afterwards does not update it.

How to use ROT13 Encoder

1. Paste the text you want to transform.
2. Choose ROT13 for letters or ROT47 for printable characters.
3. Copy the result, and apply the same mode again to reverse it.
4. Check a known word against the expected output.

When to use it

• Obscure a spoiler or a punchline so it is not read by accident.
• Demonstrate a basic substitution cipher in a lesson.
• Ambiguously hide text that is not security-sensitive.
• Create a simple puzzle clue.
• Show why a self-inverse cipher is easy to reverse.
• Prepare a harmless prank message.

When not to use it

• Do not use it to protect passwords, tokens or private data.
• Do not expect it to change digits or punctuation in ROT13 mode.
• Do not use it as a substitute for encryption.

Example

Applying ROT13 to the word hello produces uryyb, and applying it again returns hello. ROT47 changes all printable ASCII, so it also affects digits and punctuation. Characters outside the selected range are left untouched.

What you can do with ROT13 Encoder

• Apply ROT13 to Latin letters.
• Apply ROT47 to printable ASCII characters.
• Preserve case and unaffected characters.
• Reverse the transformation by running the same mode again.
• Copy the result.
• Run the cipher locally with no upload.

Example: preview the transformation before sharing

Paste a short sample and inspect the result in the place it will be used. A fancy style that looks right in one app can show as boxes or plain letters in another.

Check whether the transformation is reversible. Escapes, Morse and binary can be decoded; styled letters and Zalgo usually cannot be restored perfectly.

Copy the result and keep the original if the text will be edited later or read by a screen reader. Styled characters are separate code points, so a search for the plain word will not find them.

If the text is for accessibility, prefer plain characters. A screen reader may read styled letters one by one or skip the combining marks entirely.

If the output will go into a field with a character limit, count the characters before and after. Styled letters often use more code points than the plain form, so a caption that fit before may no longer fit.

For a reversible encoding, test the round trip on a short sample. Encode, decode, and compare; if the result differs, the tool is not the right one for that data.

Keep the plain source in a note next to the styled version. When the effect stops rendering or a reader cannot parse it, the plain text is the only accessible fallback.

What to know before you start

• ROT13 and ROT47 are trivially reversible and provide no real security.
• They only handle the characters in their defined ranges, leaving others untouched.
• There is no key or configuration beyond the mode.
• The output is not safe for sensitive data.

Common mistakes

• Treating ROT13 as encryption.
• Expecting digits to change in ROT13 mode.
• Applying ROT13 twice and thinking the tool failed.
• Using ROT47 on text that contains non-ASCII letters and expecting them to change.

Troubleshooting

If the text is unchanged, it may contain no characters in the selected range.

If only some characters changed, the cipher's range explains it.

If the result looks like the original, it may already have been encoded once.

If a second application does not restore the text, confirm that the same mode was used both times.

Related standards and documentation

• Styled letters are separate Unicode code points, not formatting; search and spell-check may not recognize them.
• Combining marks attach to the preceding character and can affect cursor movement and accessibility.
• Base64, binary and escapes are encodings, not encryption.
• Character counts can change after a transformation because Unicode code points differ from visible glyphs.