Data Pipeline Builder

How to build a pipeline

1. Type or paste your input text into the box at the top.
2. Add a step. Pick a step type from the dropdown (Base64, hex, URL encoding, ROT13, Caesar cipher, reverse, case changes, hash, gzip) and click + Add step.
3. Repeat to chain as many steps as you need, each one runs on the output of the step above it.
4. Reorder or remove steps with the up and down arrows and the X on each step, and adjust any step's settings, like a Caesar shift amount or a hash algorithm.
5. Read the result. The final output box always shows where the pipeline landed, and with "Show output after every step" turned on, each step gets its own preview so you can see exactly what changed at every stage.

Why chain steps instead of using one tool at a time

Most encoding tools, including the individual Base64, hex, URL, Caesar and hash tools on this site, do exactly one job. That is fine when you know precisely what you are looking at, but a lot of real work is not that clean. Someone hands you a mystery string and you genuinely do not know whether it is Base64 wrapped around gzip, or hex wrapped around URL-encoded text, or three layers of something else entirely. Working that out one tool at a time means constantly copying output from one page, opening another tool, pasting it in, copying again, and losing track of what you already tried.

A pipeline builder turns that guesswork into a single, visible recipe. You stack the steps you think are involved, in order, and the tool shows you the result after each one, so a wrong guess is obvious immediately instead of after several manual copy-paste round trips. It is also a genuinely useful way to learn how these transforms compose: watching a plain sentence turn into URL-encoded text and then into Base64, one visible stage at a time, makes the relationship between the two encodings click in a way that running them separately never quite does.

How data moves between steps

Internally, the pipeline treats your data as raw bytes at every stage, and only converts to and from readable text at the edges, when you type your input and when a step's result is displayed. That matters because not every step produces text. Gzip compression, for instance, outputs binary bytes that are not valid readable text at all, so the tool shows binary output as a hex dump instead of trying to force it into characters that do not exist. Steps that only make sense on text, like reversing a string or changing its case, check first that the bytes flowing into them are valid UTF-8 text. If you feed one of those a step's binary output by mistake, for example running Uppercase directly after Gzip compress, it fails with a clear message telling you which step choked and why, rather than quietly producing corrupted, meaningless output that looks like it might be right.

What is included in this MVP

This tool covers a focused set of the transforms people reach for most often: Base64 encode and decode, hex encode and decode, URL encode and decode, ROT13 and an adjustable Caesar cipher, reverse text, uppercase and lowercase, a one-way hash digest (MD5, SHA-1, SHA-256, SHA-384 or SHA-512), and gzip compress and decompress using your browser's own built-in compression support. That is deliberately a small, solid set rather than an attempt to replicate every operation in a full desktop-grade recipe tool. A hash step is one-way by nature, so nothing meaningful can follow it in a chain except maybe another encode step run on the resulting hex text, which the tool allows without stopping you.

Frequently asked questions

Related: Base64 encode/decode · URL encode/decode · Caesar cipher · hash generator · all developer tools.