Simple online tools for developers, networking, text and conversions.

Developer Tools

URL Decoder

Decode percent-encoded URLs and query values back into readable text instantly.

Tool

Use this free URL Decoder to convert percent-encoded URL text back into readable form. It is useful for inspecting query parameters, debugging redirects, reading encoded API request values, checking tracking links, and understanding what an encoded URL or parameter actually contains. Paste encoded text or a full encoded URL to decode it instantly in the browser.

About this tool

Use this free URL Decoder to convert percent-encoded URL text back into readable form. It is useful for inspecting query parameters, debugging redirects, reading encoded API request values, checking tracking links, and understanding what an encoded URL or parameter actually contains. Paste encoded text or a full encoded URL to decode it instantly in the browser.

Use url decoder when you need a fast browser-based result without extra setup. It works well for quick checks, one-off tasks, and routine formatting or calculation work.

When to use URL Decoder

URL Decoder vs related tools

URL Decoder vs URL Encoder

URL Decoder turns percent-encoded text back into readable form. URL Encoder does the reverse and creates percent-encoded output from raw text. If your input already contains sequences like %20 or %3D, decoding is usually the right first step.

URL Decoder vs Base64 Decoder

URL Decoder is for percent-encoded text used in URLs and query strings. Base64 Decoder is for Base64-encoded data. If your input contains percent sequences, use URL decoding. If it looks like an encoded block of letters and equals signs, it may belong to Base64 instead.

Helpful next steps

If you need to encode the readable result again, use URL Encoder. If you want to inspect the structure of a decoded link, open URL Parser. If the decoded value turns out to be JSON text, you may also want JSON Formatter.

Common mistakes when decoding URLs

Learn more

Why use this tool

How to use

  1. Paste the encoded text, query value, or URL into the input box
  2. Click Run Tool to decode the input
  3. Review the readable output in the result area
  4. Use the decoded result to inspect parameters, redirect targets, or request values
  5. If needed, use the URL Encoder page to convert it back into encoded form

Examples

Example

Input

hello%20world

Output

hello world

Useful when you need to read plain text that was encoded for a URL.

Example

Input

name%3DJohn%20%26%20role%3Dadmin

Output

name=John & role=admin

Helpful when a parameter value contains equals signs, ampersands, and spaces.

Example

Input

https%3A%2F%2Fexample.com%3Fa%3D1%26b%3D2

Output

https://example.com?a=1&b=2

Useful when one URL is embedded inside another as a parameter value.

Example

Input

https%3A%2F%2Fexample.com%2Flogin%3Fnext%3D%2Fdashboard

Output

https://example.com/login?next=/dashboard

Helpful when debugging redirect flows or next-return URLs.

Example

Input

email%3Duser%40example.com%3Fx%3D1%26y%3D2

Output

email=user@example.com?x=1&y=2

Useful for inspecting what special characters looked like before encoding.

Example

Input

%D0%9F%D1%80%D0%B8%D0%B2%D0%B5%D1%82%20%D0%BC%D0%B8%D1%80

Output

Привет мир

Helpful when checking encoded non-English or Unicode text.

Example

Input

%7B%22name%22%3A%22John%22%2C%22role%22%3A%22admin%22%7D

Output

{"name":"John","role":"admin"}

Useful when JSON is transported through query parameters or redirect values.

Example

Input

line%20one%0Aline%20two

Output

line one
line two

Helpful for understanding how multiline text was represented in encoded form.

Common errors

Decoding a value more than once

Fix: Check whether the text has already been decoded before running the tool again.

Assuming every encoded-looking string is valid URL encoding

Fix: Confirm that the source actually uses percent-encoding and is not Base64 or another format.

Using URL decoding for Base64 or JWT data

Fix: Use Base64 or JWT tools when the input belongs to those formats instead of percent-encoded URL text.

Pasting partial encoded values from logs or browser tools

Fix: Copy the full encoded value so the decoded result makes sense in context.

Confusing a decoded full URL with a decoded parameter value

Fix: Decide whether you are decoding a whole embedded URL or just one encoded parameter string.

FAQ

What does a URL decoder do?

A URL decoder converts percent-encoded URL text back into readable text so you can inspect its real contents.

When should I use URL decoding?

Use URL decoding when a link, query parameter, redirect target, or request value contains percent-encoded characters that you want to read clearly.

What is the difference between URL Decoder and URL Encoder?

URL Decoder turns percent-encoded text back into readable form, while URL Encoder converts readable text into a percent-encoded format.

What is the difference between URL decoding and Base64 decoding?

URL decoding reverses percent-encoding used in URLs, while Base64 decoding reverses Base64-encoded data. They solve different problems.

Why does my URL look broken after decoding?

The most common reasons are double-decoding, partial copied input, or decoding a value that was not supposed to be decoded as a whole.

Can I decode a full embedded URL?

Yes. This is a common use case when one URL is passed as a parameter inside another URL.

Can I decode Unicode or non-English text?

Yes. URL decoding is useful for restoring encoded Unicode characters back into readable text.

Can I decode JSON with this tool?

Yes. If JSON text was URL-encoded for transport in a query or redirect value, this tool can restore it.

Why do I see %20, %2F, or %3D in encoded text?

Those are percent-encoded representations of characters such as spaces, slashes, and equals signs.

When should I use URL Encoder after decoding?

Use URL Encoder when you want to re-encode the readable result for safe reuse inside a URL or query parameter.

Use cases

Related tools