URL Decoder

Make encoded links readable. Paste a URL or query string full of %20 and %3D codes and see the plain text instantly.

  • Files stay on your device
  • Free, no sign-up
  • Instant
Quick guide · 3 steps

How to use the URL Decoder

When to use the URL Decoder

Reading tracking links

Turn long, unreadable marketing and redirect links into plain text to see where they go.

Debugging web apps

Read encoded query parameters from server logs and analytics reports.

Search terms in analytics

Decode keyword reports that show searches as %20 and + characters.

Non-English URLs

See the real Urdu, Arabic or emoji text behind percent-encoded addresses.

Features and benefits

  • Decodes all UTF-8 percent sequences, including emoji
  • Optional + to space conversion
  • Points to the exact position of malformed % codes
  • Instant, private decoding

Example

Input
https://example.com/search?q=caf%C3%A9+%26+tea
Output
https://example.com/search?q=café & tea

How the URL Decoder works

ConvertNest reads each %XX sequence as a byte and joins the bytes into UTF-8 text, so multi-byte characters such as é (%C3%A9) or emoji come out correctly. With “Treat + as a space” on, plus signs become spaces, which is right for form-style query strings. If a % is not followed by two hexadecimal digits, the tool shows exactly where the problem is instead of failing silently.

A real-life example

A marketing manager sees a referral in analytics that looks like %D9%84%D8%A7%DB%81%D9%88%D8%B1%20restaurants. Decoding it shows the search was “لاہور restaurants” – Lahore written in Urdu. This tells her that customers are searching in Urdu as well as English, so she adds Urdu text to her restaurant’s landing page.

Good to know

Encoded URLs appear in analytics reports, redirect chains, email tracking links and server logs. Decoding them reveals the real destination and parameter values.

If decoding fails, the text contains a % that is not followed by two hexadecimal digits, or a sequence that is not valid UTF-8. The error message tells you where to look.

Tips for the best results

  1. If the result still contains %XX codes, it was encoded twice – decode it again.
  2. Turn off the + option for values where a plus sign is meaningful, such as phone numbers or Base64.
  3. Use the URL Parser to split a full address into its parts after decoding.
  4. Be careful clicking decoded links from unknown sources – check the domain first.

Common mistakes to avoid

Decoding Base64 with a URL decoder

They are different formats. Use the Base64 Decoder for Base64 strings.

Converting + to spaces in a phone number

+92 becomes “ 92”. Turn the option off.

Copying a URL with a trailing %

A cut-off % sequence is malformed. Copy the complete link.

URL Decoder – frequently asked questions

Why does my decoded text still contain % signs?

It may have been encoded twice. Paste the result in again to decode a second time.

When should “Treat + as a space” be off?

When the + is a real plus sign, for example in a phone number or a Base64 value inside a URL.

Is URL decoding the same as Base64 decoding?

No. URL decoding converts %XX codes. Base64 is a different encoding – use the Base64 Decoder for that.

Can I see each part of a URL separately?

Yes – the URL Parser splits a URL into host, path and decoded query parameters.

What does %20 mean?

It is an encoded space character.

Can I decode several URLs at once?

Yes. Put one per line; line breaks are kept in the output.

Why does my decoded link look different from the address bar?

Browsers show a friendly decoded version but send the encoded version to the server. Both point to the same page.

Is it safe to decode a suspicious link here?

Yes. Decoding only converts text on your device – the link is never opened, so you can inspect it safely before deciding whether to visit.