Multi-Step Decoder – Chain Base32, Base64, ROT13, Atbash & More
Paste your text, arrange the decoding steps in order, and see the result after every layer.
- Step 1
Step format
UTF-8 text; standard or URL-safe Base64 on decode.
Up to 12 steps · 10,000 input characters · 100,000 characters per result.
How to decode a multi-step cipher
- Paste the encoded text and choose the first operation. Undo the outermost layer first.
- Add the next steps, enter any key or shift, and use the arrows to put them in order. Check each intermediate output.
- Copy the final output, or open Share recipe to copy a link with the steps. Include input text only when you want it in the URL.
Base32, Base64, Hex and Binary use UTF-8 text. Base32 uses the RFC 4648 alphabet and padded output; decoding accepts lowercase, whitespace and omitted padding. Atbash, Caesar, Vigenère and ROT13 transform A–Z letters; ROT47 transforms printable ASCII. Reverse text uses BMP characters. A1Z26 encoding accepts uppercase A–Z words with single spaces. Open a step’s format note for its input rules.
Common chains
Try the built-in examples under “Try a chain.” Each message below was written for this page.
| Decode order | Example input | Final output |
|---|---|---|
| Base32 → Atbash | NZ3HMZZAPJTSA3LMNRWQ==== | meet at noon |
| Vigenère (key) → Atbash Key: MAP | Zvks yq ssk kouh tosv. | Meet by the blue gate. |
| Base64 → ROT13 | T2V2YXQgbiB0ZXJyYSBhYmdyb2JieC4= | Bring a green notebook. |
Round-trip checks
Each row encodes a fixed sample and decodes it with the same settings. All 24 checks restore the exact original text. Caesar uses shift 7; Vigenère uses key MAP. These checks cover the samples shown, rather than every possible input.
View all 24 checks
| Step | Sample | Encoded | Decoded | Pass |
|---|---|---|---|---|
| Base32 | Blue gate 7! | IJWHKZJAM5QXIZJAG4QQ==== | Blue gate 7! | Yes |
| Base32 | Café 東京 | INQWNQ5JEDTJ3MPEXKWA==== | Café 東京 | Yes |
| Base64 | Blue gate 7! | Qmx1ZSBnYXRlIDch | Blue gate 7! | Yes |
| Base64 | Café 東京 | Q2Fmw6kg5p2x5Lqs | Café 東京 | Yes |
| Hex | Blue gate 7! | 42 6C 75 65 20 67 61 74 65 20 37 21 | Blue gate 7! | Yes |
| Hex | Café 東京 | 43 61 66 C3 A9 20 E6 9D B1 E4 BA AC | Café 東京 | Yes |
| Binary | Blue gate 7! | 01000010 01101100 01110101 01100101 00100000 01100111 01100001 01110100 01100101 00100000 00110111 00100001 | Blue gate 7! | Yes |
| Binary | Café 東京 | 01000011 01100001 01100110 11000011 10101001 00100000 11100110 10011101 10110001 11100100 10111010 10101100 | Café 東京 | Yes |
| URL | Blue gate 7! | Blue%20gate%207! | Blue gate 7! | Yes |
| URL | Café 東京 | Caf%C3%A9%20%E6%9D%B1%E4%BA%AC | Café 東京 | Yes |
| ROT13 | Blue gate 7! | Oyhr tngr 7! | Blue gate 7! | Yes |
| ROT13 | Café 東京 | Pnsé 東京 | Café 東京 | Yes |
| ROT47 | Blue gate 7! | q=F6 82E6 fP | Blue gate 7! | Yes |
| ROT47 | Café 東京 | r27é 東京 | Café 東京 | Yes |
| Atbash | Blue gate 7! | Yofv tzgv 7! | Blue gate 7! | Yes |
| Atbash | Café 東京 | Xzué 東京 | Café 東京 | Yes |
| Caesar | Blue gate 7! | Isbl nhal 7! | Blue gate 7! | Yes |
| Caesar | Café 東京 | Jhmé 東京 | Café 東京 | Yes |
| Vigenère | Blue gate 7! | Nljq gpfe 7! | Blue gate 7! | Yes |
| Vigenère | Café 東京 | Oaué 東京 | Café 東京 | Yes |
| Reverse text | Blue gate 7! | !7 etag eulB | Blue gate 7! | Yes |
| Reverse text | Café 東京 | 京東 éfaC | Café 東京 | Yes |
| A1Z26 | BLUE GATE | 2-12-21-5 7-1-20-5 | BLUE GATE | Yes |
| A1Z26 | MAP | 13-1-16 | MAP | Yes |
Multi-step decoder FAQ
How do I decode Base32 then Atbash?
Choose Base32 as step 1 and Atbash as step 2, both in Decode mode. Open “Try a chain” and select “Base32 → Atbash” to load a complete example that returns “meet at noon.” You can see the Base32 result before Atbash restores the message.
What order should I decode in?
Undo the last encoding first. If a message was transformed with ROT13 and then Base64, decode Base64 first and apply ROT13 second. When instructions explicitly say “decode Base64, then ROT13,” follow that order. Enter the original key or shift for keyed steps.
Is my text sent to a server?
The decoder processes text locally in your browser. Recipe links include the steps, keys and shifts, but exclude input text by default. If you check “Include input text in the link,” the text becomes part of the URL and can appear in browser history, server logs and services that receive that URL. Share only text and keys you intend to disclose.
Explore individual ciphers
Use the cipher identifier to investigate an unknown layer, or work with Base32, Atbash and Vigenère individually.