No recently used tools
No favorite tools yet

Free URL Encoder Decoder Online - Percent Encoding Tool

182 uses

Common URL Encoding Reference

CharacterEncodedDescription
Space%20 / +Most common URL escape character
!%21Exclamation mark
#%23Hash, URL anchor symbol
%%25Percent sign (must be escaped)
&%26URL parameter separator
=%3DURL parameter assignment
?%3FQuery string start
/%2FPath separator

URL Encoding Facts

What is URL Encoding?
URL encoding converts special characters to %XX format, ensuring URLs transmit safely across the web without being misinterpreted.
Unicode in URLs
Non-ASCII characters (accented letters, CJK, emoji) are converted to UTF-8 bytes then percent-encoded, e.g. ä becomes %C3%A4.
encodeURIComponent
Encodes all special characters including : / ? # — ideal for URL parameter values.
encodeURI
Preserves URL structure characters (://?#@) — use this for encoding a complete URL while keeping its structure intact.
URL-Safe Characters
Letters A-Z, a-z, digits 0-9, and -_.~ are URL-safe and never need encoding.
Space Encoding
Spaces can be encoded as %20 or + in URLs. %20 is standard for paths; + is used in form submissions. Modern practice prefers %20.

Frequently Asked Questions

Q Do I need to manually encode URL parameters in JavaScript?
A Modern APIs like fetch and axios handle encoding automatically. But when manually building URL strings, always use encodeURIComponent for parameter values.
Q How do I correctly encode UTM tracking parameters for social media campaigns?
A Social media platforms require URLs to be properly encoded to ensure tracking parameters (like utm_source, utm_medium, utm_campaign) are transmitted correctly. Use `encodeURIComponent` for each parameter's *value* (e.g., `utm_campaign=My Campaign & Product`) to prevent spaces, ampersands, or other special characters from breaking the URL or misinterpreting your tracking data. This tool helps ensure your UTMs are always valid for accurate analytics.
Q How do I correctly encode multilingual text or special characters like umlauts and Kanji for a URL?
A When creating URLs with non-ASCII characters, such as German umlauts (ä, ö, ü), French accents (é, ç), or Japanese Kanji, proper URL encoding is essential. This tool converts these characters into their percent-encoded form, like `%C3%A4` for 'ä'. This prevents display errors ("mojibake"), ensures your URLs are universally valid, and maintains data integrity across different web systems and browsers, especially for international content.
Q My spreadsheet contains URLs with percent-encoded characters like %20 or %2F. How can I quickly decode them to make them readable for analysis?
A This tool is perfect for cleaning up such data! Copy the percent-encoded URL (or a list of them) from your spreadsheet into the decoder. It will convert characters like `%20` back to spaces and `%2F` to slashes, making the URLs human-readable. This is crucial for verifying links, extracting specific parameters, or preparing data for reports without manual text editing.
Q How do I properly encode URL parameters when making a REST API request?
A When building URLs for REST API calls, it's crucial to encode parameter values to prevent issues with special characters like spaces, ampersands, or slashes. These can break your request or lead to incorrect data interpretation. Use the `encodeURIComponent` mode of this tool for each parameter's value before appending it to the URL, ensuring your API requests are valid and reliable.
Q When building dynamic URLs from user input or database entries, how do I ensure special characters are correctly encoded?
A For dynamic URLs, especially those constructed from user-submitted text or database queries, it's crucial to use `encodeURIComponent` for each path segment or query parameter value. This tool helps by converting spaces, ampersands, slashes, and other special characters into their safe percent-encoded forms. This prevents broken links, ensures correct parsing by browsers and servers, and maintains URL integrity, which is vital for SEO and user experience.
Q How can I quickly encode multiple separate URL query parameters or paths for a new website launch?
A This tool is designed for efficiency! You can paste multiple distinct URL path segments or query parameter values (each on a new line) into the encoder. It will process each line independently, converting special characters into their correct percent-encoded format. This saves significant time when preparing numerous new URLs for sitemaps, internal links, or API calls, ensuring all links are valid and robust from day one of your launch.
Q Can I encode text using different character sets directly?
A This tool focuses on URL encoding, not character set conversion. It assumes your input text is already in a standard set like UTF-8. If you have text in a different encoding, you'll need to convert it to UTF-8 first before using this encoder to ensure proper percent-encoding. For example, if you have a string with non-ASCII characters, make sure it's represented as UTF-8 bytes before feeding it here.
Q Why does encodeURI leave some characters like ? and = untouched?
A encodeURI is meant for encoding whole URLs, not parameter values. It preserves characters with special meaning in URLs — like ?, #, /, and =. Use encodeURIComponent instead if you need those characters encoded. For example, encodeURI leaves ? alone, but encodeURIComponent turns it into %3F. Pick the right mode in this tool based on what part of the URL you're encoding.
Q Why does my encoded URL look different in the browser address bar versus what I typed?
A Browsers often normalize URLs automatically. For example, typing a space in the address bar gets converted to %20, but some browsers display it as a space again. Our tool shows you the raw percent-encoded output, which is what actually gets sent over the network. Paste your browser's address into the decoder to see the real underlying characters. This mismatch catches many developers off guard.

How to Use

Related Tools