Skip to main content

Web Tools

URL Encode / Decode

Convert URL text to and from percent encoding.

URL Encode / Decode tool

Loading tool…

Jump to a section

About This Tool

Encode spaces, symbols, query parameters, redirect URLs, and other URL text into percent-encoded form, or decode encoded values back into readable text. When the input is a valid URL, the tool also shows its protocol, host, path, query, and hash so you can confirm which part of the URL changed.

How To Use It

  1. Choose Encode component for a query value or path segment, Encode full URL for a complete URL, or Decode for percent-encoded text.
  2. Paste or type the URL text.
  3. Review the converted output and parsed URL parts when available.
  4. Use Encode component before inserting a value into a larger URL, and use Encode full URL only when the input is already a complete URL.
  5. Copy the result or use the output as the next input to reverse-check the conversion.

Examples

Encode a query value

online tools becomes online%20tools when encoded as a URL component.

Decode a redirect URL

Decode https%3A%2F%2Fhanakash.com%2Ftools to read the original URL.

Decode query text

Decode q=online+tools%2Bguides as q=online tools+guides, treating unescaped plus signs as spaces while preserving %2B as a literal plus.

Encode a redirect parameter

Encode https://hanakash.com/tools?q=url tools as a component before placing it inside a redirect= query parameter, so its ?, =, &, and spaces cannot break the outer URL.

Useful Notes

Component vs full URL

Encode component escapes characters such as :, /, ?, =, #, and &, which is useful for individual query values or path segments. Encode full URL preserves structural URL characters such as :, /, ?, #, and & while escaping unsafe characters inside the URL.

Plus signs in query strings

Many web forms and query-string builders encode spaces as plus signs. Decode mode converts unescaped + characters to spaces before percent-decoding, while encoded %2B values remain literal plus signs.

Single-pass decoding

Decode mode decodes one layer of percent encoding. If an already-decoded result still contains values such as %20, that usually means the original text was double-encoded or contains an encoded value inside another URL.

Malformed input

Invalid percent escapes or unpaired Unicode surrogate characters are rejected instead of producing misleading output.

Common use cases

Use URL encoding for query strings, redirect parameters, API debugging, analytics links, and values that contain spaces or special characters.

Local processing

Encoding, decoding, and URL parsing run in browser JavaScript. The tool does not need to upload the text to perform the conversion.

FAQ

When should I use Encode component?

Use it for a single query value, path segment, or parameter value that will be inserted inside a larger URL.

When should I use Encode full URL?

Use it when the input is already a complete URL and you want to encode unsafe characters while preserving URL structure.

Is this the same as Base64?

No. URL encoding escapes characters for safe URLs, while Base64 represents bytes as text.

Why did %2520 become %20 instead of a space?

%2520 is a double-encoded space. One decode pass turns %25 into the percent sign, leaving %20 visible for a second decode if that is truly what you need.

Is this the same as HTML entity encoding?

No. URL encoding is for URL paths, query strings, and fragments. HTML entities are for displaying literal characters inside HTML.

Is my URL text uploaded?

No. Conversion and parsing are handled locally in the browser.