Free URL Encoder & Decoder Online

What URL Encoding Is and When You Need It

URL encoding, also called percent encoding, converts characters that are not safe inside a web address into a format built from a percent sign and two hex digits. A URL is only allowed to contain a limited set of characters — letters, digits, and a few symbols — so anything else has to be escaped. This tool encodes text into that safe form and decodes it back to readable text. Developers building API calls, front-end engineers placing values into HTML attributes, SEO specialists inspecting messy tracking links, and everyday users fixing a link copied from a document all reach for it. The moment a link contains a space, an accented letter, or a symbol like & or ?, encoding is what keeps it from breaking. The mechanism is precise. Each unsafe character is replaced by its byte value in hexadecimal, prefixed with a percent sign: a space becomes %20, an ampersand becomes %26, a question mark becomes %3F, and a forward slash becomes %2F. Non-ASCII characters are first converted to their UTF-8 bytes, so an accented é becomes %C3%A9 — two bytes, two percent codes. Decoding simply reverses the lookup, turning each %XX group back into the character it represents. This matters because browsers and servers read structural characters like ? and & as instructions; if a parameter value contains a literal one, it must be encoded or the server will misread where the value ends and the next instruction begins. Here is a concrete case. Suppose you want to pass the search phrase "tea & coffee" as a query value. Left raw, the URL /search?q=tea & coffee breaks, because the ampersand looks like the start of a new parameter and the space is illegal. Encode just that value and it becomes /search?q=tea%20%26%20coffee, which transmits perfectly and decodes back to "tea & coffee" on the server. The three unsafe characters — two spaces and one ampersand — turned into %20, %26, and %20. Run it in reverse and the tool takes /search?q=tea%20%26%20coffee and hands back the original phrase, which is how you read what a mystery link is actually asking for. The practical uses are constant. A back-end developer encodes every dynamic query value so a request never fails or returns the wrong data. A front-end engineer encodes a string before dropping it into an href attribute to avoid breaking the markup. An analyst decodes a long tracking URL to read exactly what each UTM parameter contains. A support agent fixes a link a customer pasted from a Word document where a space sneaked into the address. A publisher checking why a Hindi or Tamil article URL looks like a stream of percent codes decodes it and confirms the slug is correct, just UTF-8 encoded. Someone debugging a failing webhook decodes the callback URL and spots that a colon was escaped when it should not have been. One rule prevents most mistakes: encode individual values inside a query string, not the whole URL at once, or you will accidentally escape the slashes and colons that give the address its structure. Know the limits too — encoding does not encrypt or hide anything, since anyone can decode it just as easily, so never treat it as security for passwords or tokens. If a value looks doubly garbled, it may have been encoded twice; just decode again. Watch the plus sign as well: in a query string the older form-encoding standard reads + as a space, so a genuine plus in a value has to be sent as %2B or it silently disappears. Everything here runs locally in your browser, so private query strings and tokens are never uploaded to a server.

Learn More — URL Encoder / Decoder Guide

🔥 Trending Tools