Decode nested URL-encoded parameters (Base64 JSON in a query string)
Unwrap the common API pattern where a URL parameter carries URL-encoded Base64 JSON — one chain, three tools, zero copy-pasting between pages.
- 1
APIs often transport structured data through URLs like ?data=eyJhIjoxfQ%3D%3D. Reading it requires unwrapping layers in reverse order: first percent-decoding, then Base64 decoding, then JSON formatting. Doing this by hand across three pages is where mistakes creep in — run it as one chain instead.
- 2 URL Decoder →
Single-layer case: paste just the encoded value and get the decoded text.
- 3 url-decode → base64-decode → json-format
Paste the full encoded parameter value as the chain input. Each intermediate output is visible, so if a layer fails you see exactly which one and why.
- 4
If the decoded Base64 payload is not JSON but another encoding (e.g. another Base64 layer or percent-encoding inside), extend the chain with the matching tool — the pipeline accepts any order and you can re-run from any node after adjusting it.
Frequently asked questions
- Why does %3D appear at the end of the value?
- %3D is the percent-encoding of '=' — the Base64 padding character. URL-decode restores it before the Base64 layer runs.
- Can I encode in the reverse direction?
- Yes — reorder the chain with the encode tools (json → base64-encode → url-encode) using the same builder. Save it as a workflow so the reverse task is one click next time.
Workflows that solve this
Learn more
Want to understand why?