Multi-Step Encode / Decode & Hash Chain (Recipe Builder)
Line up conversion steps (a recipe) and they are applied to your input from top to bottom. Do multi-stage jobs such as Base64 decode → URL decode, or text → Base64 → SHA-256, in one go. For a single conversion, the Base64 Encoder/Decoder or the Hash Generator is quicker.
🔒 Runs in your browser · Your data is never sent to a server
Recipe (applied top to bottom)
No steps yet. Pick an operation and press "Add".
The result contains bytes that are not valid UTF-8 text (shown as �). Add "Hex encode" at the end to inspect it.
How to use
- Enter the text to convert in "Input".
- Pick an operation under "Operation to add" and press "Add". Repeat for as many steps as you need.
- Reorder with "Up" / "Down" and drop unwanted steps with "Remove". Each step shows its intermediate "Output".
- Check the "Final result" and take it with "Copy".
Notes
- Each step passes its output straight to the next step as input. Encoding operations treat text as UTF-8.
- Base64 decode also accepts Base64URL (- and _), line breaks and missing padding. Hex decode accepts spaces, commas and 0x prefixes.
- Base64 and URL encoding are not encryption. MD5 and SHA-1 have known collisions and are unsuitable for security uses such as password storage.
- Case conversion, reverse, ROT13 and HTML/Unicode escaping read the previous output as UTF-8 text. Invalid UTF-8 bytes become �, so for binary data, or when a Base64 decode yields non-UTF-8 bytes, put "Hex encode" or "Base64 encode" before them.
- The recipe is lost when you close the page (saving and share links are not supported).
Glossary
Recipe
An ordered list of conversion steps. Each step output becomes the next step input, so several conversions run in a single action.
Hash
A one-way function that turns any data into a fixed-length value. It cannot be reversed, and the same input always gives the same value, which is why it is used to detect tampering.
ROT13
A simple substitution that shifts each letter by 13. Applying it twice restores the original, but it offers no real security.
FAQ
Does the order of the steps change the result?
Yes. Each step output becomes the next step input, so the order matters. For example "Base64 encode → SHA-256" and "SHA-256 → Base64 encode" give different results. Reorder with "Up" / "Down" and inspect each step "Output" to see the intermediate values.
How do I get a hash as Base64?
The hash steps here output a hex string. To get Base64 of the raw hash bytes, add "Hex decode" and then "Base64 encode" after the hash step.
Why does a step in the middle show an error?
The previous output is not in the format that step expects. For example, putting "URL encode" before "Base64 decode" leaves % characters that are not valid Base64. Check the step number in the message and review the order or type of the steps.
Can I convert images or files?
This tool only accepts text input. For image-to-Base64 use the Image to Base64 converter, and for file hashes use the File Hash Calculator.
Share this page