Skip to content
uencoder
PIPELINE Encoding & Decoding Intermediate 3 steps

Decode nested URL parameter (Base64 JSON)

APIs often transport structured data through query parameters with layered encoding. This chain reverses the layers in order: percent-decoding first, then Base64, then JSON formatting. Each intermediate output is visible, so a failure points at the exact layer.

What it solves

Unwrap a URL parameter that carries URL-encoded Base64 JSON into readable, formatted JSON.

Input → Output

URL Decoder input → JSON Formatter output across 3 steps.

Runs in

1–2 minutes · fully local in your browser.

Before you start

  • A URL parameter value with layered encoding (percent → Base64 → JSON)

The pipeline

  1. 1 URL Decoder url-decode

    Decode percent-encoded URL text back to readable characters. Free, private, and 100% client-side.

  2. 2 Base64 Decoder base64-decode

    Decode Base64 data back to readable text online. Free, private, and 100% client-side.

  3. 3 JSON Formatter json-format

    Format, minify, or sort JSON online. Free, private, and 100% client-side.

Open in Toolchain

Runs locally in your browser. The recipe defines the pipeline only — your input never leaves this tab.

▶Run this workflow

Enter your input below and click Run. All processing happens locally in your browser — nothing is uploaded.

Pipeline progress

  1. URL Decoderurl-decode
  2. Base64 Decoderbase64-decode
  3. JSON Formatterjson-format

Sample input

eyJhIjoxfQ%3D%3D

Expected output

{
  "a": 1
}

This pair is executed against the real tools at build time (tests/unit/recipes.test.ts) — the expected output is verified, not illustrative.

Related tasks

Related workflows

You might also need

Workflows sharing tools or topics with this recipe.

Learn more

Tools used