About The URL Encoder and Decoder

The URL Encoder and Decoder converts text with spaces, symbols, and reserved characters into percent-encoded URL components, then decodes percent-encoded values back to readable text.

The tool uses browser URL component encoding locally. It is best for query parameter values, path segment values, callback fragments, and log inspection.

How to Encode or Decode URL Components Online

1. Paste a value into the Text or URL box.
2. Click Encode URL Component when preparing text for a query parameter or path segment.
3. Click Decode URL Component when inspecting percent-encoded text.
4. Use Load sample for a realistic component value, then copy the output into your request, redirect, or debugging notes.

Choosing Options Correctly

Encode URL Component:
- Use this for parameter values like search terms, redirect targets, and callback state values.
- Do not encode an entire URL unless you intentionally need the full URL as a single parameter value.

Decode URL Component:
- Use this for values copied from logs, query strings, or network traces.
- If decoding fails, the percent escapes may be incomplete or malformed.

Common Use Cases

• Preparing query parameter values for API calls.
• Debugging encoded redirect URLs.
• Reading percent-encoded values from logs.
• Checking whether a value has been double-encoded.

Quick FAQ

Should I encode the whole URL?
Usually no. Encode individual components such as query values, path segments, or form values so reserved URL characters keep their meaning.

Can I decode repeatedly?
Yes, but only when the text was encoded repeatedly. Decoding too many times can turn safe text back into reserved characters.

Is my URL uploaded?
No. Encoding and decoding are designed to run in the browser.

What happens if I double-encode a component?
Characters such as percent signs get encoded again, so the receiving system may see the wrong value until it decodes twice.