AIStacker
Web

Overview

URL Decoder

Decode percent-encoded URL strings back to human-readable plain text.

What isHow to useExampleCommon use casesFrequently asked questions

Category hub

Web

Problems

6

FAQ

2

Quick links

Browse hub
#decode-encoded-url#url-decode-spaces#percent-decoding#percent-decode#query-string

What you can solve

How to decode a URL encoded string?

Yes. Paste the entire URL including the domain and query string — only the encoded components will be decoded, not the structural characters (/, ?, &, =).

How to read percent-encoded text?

When an already-encoded string gets encoded again — %20 becomes %2520. Click Decode twice to fully decode a double-encoded string.

How to decode %20 in a URL?

URL decoding reverses percent-encoding, converting sequences like %20 back to spaces and %E6%97%A5 back to 日.

How to decode double-encoded URLs?

When an already-encoded string gets encoded again — %20 becomes %2520. Click Decode twice to fully decode a double-encoded string. If the string was double-encoded, click Decode again to strip the second layer. Yes. Paste the entire URL including the domain and query string — only the encoded components will be.

How to read encoded query parameters from logs?

It is commonly needed when reading URL parameters from logs, analyzing redirects, or inspecting OAuth flows.

How to decode a URL redirect?

Yes. Paste the entire URL including the domain and query string — only the encoded components will be decoded, not the structural characters (/, ?, &, =). It is commonly needed when reading URL parameters from logs, analyzing redirects, or inspecting OAuth flows. Can it decode a full URL at once? Everything runs.

Typical workflow

URL DecoderURL DecoderJSON Formatter – Beautify & Pretty Print JSON OnlineBase64 Encoder / Decoder

Guides for this workflow

Supporting guides that connect this tool to the broader category workflow.

Open category hub
Web guide

encodeURI vs encodeURIComponent for redirect_uri and Query Params

A practical guide to choosing the right encoding boundary for redirect_uri, nested URLs, and query parameter values before a small encoding mistake turns into a redirect bug.

Web guide

Nested Redirect URL Debugging Checklist: Duplicate Params, Empty Trackers, and Decode Boundaries

A practical workflow for debugging redirect URLs that hide duplicate query keys, empty tracking params, and half-decoded nested values.

Web guide

Why Your redirect_uri Breaks: Nested Params, + Signs, and Double Encoding

A practical guide for redirect_uri bugs caused by nested query strings, plus-sign handling, and accidental double encoding across browser and server layers.

Web guide

How to Debug Redirect URLs, Query Params, and Encoded Targets

A web debugging guide for decoding redirect targets, checking nested query parameters, and spotting double-encoded URLs.

What is

What is URL Decoder?

URL decoding reverses percent-encoding, converting sequences like %20 back to spaces and %E6%97%A5 back to 日. It is commonly needed when reading URL parameters from logs, analyzing redirects, or inspecting OAuth flows.

How to use

How to use URL Decoder

Paste a percent-encoded URL or query string. Click Decode to see the original text. If the string was double-encoded, click Decode again to strip the second layer.

Example

Example

Input:  hello%20world%3F%20lang%3D%E6%97%A5%E6%9C%AC%E8%AA%9E
Output: hello world? lang=日本語

Double-encoded:
Input:  hello%2520world
First:  hello%20world
Second: hello world

Common use cases

Common use cases

1. Reading URL parameters from access logs and analytics dashboards.

2. Debugging encoded redirect chains in OAuth and SSO flows.

3. Extracting readable data from encoded API webhook payloads.

4. Reverse-engineering encoded tracking parameters.

Frequently asked questions

Frequently asked questions

What is double-encoding?v
When an already-encoded string gets encoded again — %20 becomes %2520. Click Decode twice to fully decode a double-encoded string.
Can it decode a full URL at once?v
Yes. Paste the entire URL including the domain and query string — only the encoded components will be decoded, not the structural characters (/, ?, &, =).