Format JSON, turn it into a clean slug, then Base64-encode the result — three tools chained into one repeatable pipeline.
1
Format the JSON for readability
2
Turn the formatted text into a URL-friendly slug
3
Base64-encode the slug (URL-safe alphabet)
Try it — Turn a JSON field into a URL-safe Base64 slug
Recipes/saved locally
SOURCE
▼
RESULT
SOURCE
▼
RESULT
Start from a recipe
Chain any of the 196 tools into one pipeline. Pick a starting point below, drag a tool in from the left, or click one to start blank.
#STEPTYPEOPTIONSSTATUSACTIONS
No steps yet — search for a tool on the left to start the pipeline.
INPUT
OUTPUT
Recipe error
A common small chore: you have a JSON object — a record, a config entry, an API response — and you
need a short, URL-safe identifier derived from one of its fields. Doing this by hand means three
separate tools and three copy-paste hops. This recipe chains them into one pipeline: paste JSON in,
get a Base64 slug out.
What each step does
Format the JSON.JSON Formatter re-indents the input so it's readable
— this doesn't change the data, just how it looks, which matters if you're eyeballing the
intermediate result.
Slugify it.Slug Generator strips punctuation, collapses whitespace,
and lowercases everything into a URL-friendly string — the same transformation you'd want for a
blog post title or a file name.
Base64-encode the slug.Base64 Encoder turns the slug into a
compact, URL-safe token using the -/_ alphabet instead of +//.
Try it
Paste a JSON object into the input above (a sample is pre-filled) and watch the pipeline run live —
each step's own result shows underneath its card, and the final Base64 string appears in the Output
panel on the right.
When this is useful
Short, reversible, URL-safe tokens derived from structured data show up constantly: a cache key built
from a request's identifying fields, a shareable link suffix generated from a record's title, or a
deterministic filename derived from a document's metadata. This recipe gives you a repeatable,
inspectable version of that transformation instead of a one-off script.
Frequently asked questions
Each tool does one thing well — format, slugify, encode — and no single tool combines all three. Chaining them into a named recipe means you never have to remember the order or re-paste between steps again.
Not for the final Base64 output — Slug Generator strips punctuation and whitespace either way. It matters if you want the intermediate slug step to read cleanly, since an unformatted single-line JSON blob produces a much longer, messier slug.
Standard Base64 uses + and /, both reserved in URLs. The URL-safe variant swaps them for - and _, so the result can sit directly in a path or query string without percent-encoding.
Not yet — API-runnable recipes are landing in a later stage of this feature. For now, run it in the browser via the "Run this recipe" panel below, or save it to your own recipe library and reuse it any time.