Skip to content
Converters

URL Decoder

Decode percent-encoded URLs and query strings back to plain text.

Quick answer

Decode percent-encoded URLs and query strings back to plain text.

How do I use the URL Decoder?

  1. 1

    Paste your percent-encoded URL or fragment into the input box.

  2. 2

    See the decoded text appear instantly.

  3. 3

    Copy or download the decoded result.

What is the URL Decoder?

The URL Decoder reverses percent encoding to give you back the original text. Paste an encoded URL, query string or form value and see the decoded version instantly.

It is the perfect debugging companion when inspecting server logs, redirect URLs or captured API traffic.

Who is the URL Decoder for?

Developers debugging redirect URLs, security analysts reading logs, marketers checking UTM parameters, and technical writers preparing readable examples.

Why use the URL Decoder?

  • Instant decoding.
  • Optional + as space (form-encoded) toggle.
  • Clear error messages on invalid input.
  • UTF-8 aware for any language.
  • Runs 100% in the browser.

When should I use the URL Decoder?

  • Reading a redirect URL logged by an app.
  • Inspecting UTM tags in a shared campaign link.
  • Debugging OAuth callback parameters.
  • Cleaning URLs for a report or spreadsheet.
  • Learning how percent encoding works.

Is the URL Decoder safe and private?

Yes. This tool runs entirely inside your browser - your text is never uploaded, stored on our servers or shared with third parties. You can even disconnect from the internet after the page loads and it will keep working. That makes it safe for confidential notes, drafts, private messages and unpublished work.

How do I get the best results from the URL Decoder?

  • If decoding fails, check for unescaped % signs.
  • Use the + as space toggle for x-www-form-urlencoded payloads.
  • Verify the round-trip with the URL Encoder to check symmetry.
  • Never trust decoded values without validating them.

Frequently asked questions

What if the input has invalid escapes?

A clear error message is shown and the decoded field is left empty until the input is corrected.

Does it handle + as a space?

Yes - you can toggle whether + should be treated as a space (for form-encoded data).

Does it support non-English characters?

Yes. Decoded bytes are treated as UTF-8.

Is it private?

Completely - decoding happens in your browser.

Last updated: