Skip to content
uencoder
PIPELINE Encoding & Decoding Beginner 2 steps

URL double decode

Some legacy systems or misconfigured proxies apply URL encoding more than once, producing strings like %2520 instead of %20. Running the decoder twice peels both layers and restores the original value. Always inspect the intermediate output after the first decode to confirm a second layer is actually present.

What it solves

Decode a URL-encoded string that has been encoded twice, recovering the original plaintext.

Input → Output

URL Decoder input → URL Decoder output across 2 steps.

Runs in

1–2 minutes · fully local in your browser.

Before you start

  • A string that has been URL-encoded two or more times

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 URL Decoder url-decode

    Decode percent-encoded URL text back to readable characters. 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. URL Decoderurl-decode

Sample input

%2541%2542%2543

Expected output

ABC

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

Related workflows

You might also need

Workflows sharing tools or topics with this recipe.

Learn more

Tools used