Overview
Applies six classic text transformations to any input: ROT13, ROT47, character reversal, Base64 encoding, Base64 decoding, and 8-bit binary — all computed live in the browser. One click on the output copies it. Useful for quick encodings, puzzle-solving and casual obfuscation, and equally clear that it is not encryption.
How It Works
Paste text into the input box, then click one of the six mode buttons: ROT13, ROT47, REVERSE, BASE64, BASE64-DECODE or BINARY. The output textarea re-renders instantly for each mode with the same input, so you can flip between transformations to compare. Click anywhere on the output to copy it. Base64 decode reports 'Invalid Base64' rather than throwing when the input is not valid Base64.
Step-by-Step Usage Guide
- Paste the text into the input textarea.
- Click a mode button — ROT13, ROT47, REVERSE, BASE64, BASE64-DECODE or BINARY.
- Compare modes freely; the input stays intact as you switch.
- Click the output area to copy the transformed text.
Technical Specifications & Standards
Each mode is a distinct mechanism worth knowing. ROT13 rotates the 26 letters — the standard spoiler convention. ROT47 is its wider sibling: it rotates all 94 printable ASCII characters from ! to ~ by 47, so digits and punctuation are scrambled too, and like ROT13 it is its own inverse because 47 is half of 94. Reverse is a literal character-order flip. Base64 wraps the input with encodeURIComponent/unescape before btoa, the classic trick to make the atob/btoa pair safe for non-Latin-1 text — without it, btoa throws on any character above U+00FF. Binary emits each character's code via charCodeAt, padding to eight digits: byte-accurate for ASCII, but a character above U+00FF emits its full 16-bit code-unit value rather than UTF-8 bytes, so it is not a true byte encoder — for genuine UTF-8 bytes use the site's dedicated text-binary tool. None of these modes provides confidentiality: ROT13, ROT47 and reverse are trivially reversible by anyone, and Base64 is a transport encoding that announces its own presence.
Targeted Use Cases
- Encoding a string as Base64 for a config value, data URL or basic-auth debug check.
- Decoding a ROT13 or Base64 string found in a puzzle, CTF or old forum post.
- Scrambling a string (ROT47 or reverse) so it is not readable at a glance in a screenshot.
- Quickly viewing the character-code pattern of short ASCII strings.
Notes & Gotchas
- Never treat any of these modes as security; they are reversible transformations, not encryption.
- Use the dedicated text-binary tool when you need correct UTF-8 byte encoding of non-ASCII text.
- If Base64 decode fails, check for missing padding (=) or whitespace added by the source that copied it.
- ROT47 changes digits and punctuation as well as letters — do not use it when you need numbers readable.
Frequently Asked Questions
Is this encryption?
No. ROT13, ROT47 and reverse are trivially reversible by anyone, and Base64 is a standard transport encoding. This tool is for encoding, puzzles and light obfuscation, never for protecting secrets.
What is the difference between ROT13 and ROT47?
ROT13 shifts only the 26 letters; ROT47 shifts all 94 printable ASCII characters (including digits and punctuation) by 47 positions. Both are self-inverse — applying either twice restores the original.
Why did Base64 encoding fail on my emoji?
It should not: this tool pre-encodes the input to UTF-8 bytes before Base64, unlike a naive btoa call that throws on non-Latin characters. If you see errors, check that the input pasted cleanly.
Which Base64 variant is used?
The standard RFC 4648 alphabet with padding, as implemented by the browser's built-in btoa/atob functions, applied over UTF-8 bytes so international text round-trips correctly.