Free URL Encoder & Decoder — Full-Featured URL Tool

URL encoding, also called percent encoding, converts characters that are not allowed or have special meaning in a URL into a safe format. Each unsafe character is replaced by a percent sign (%) followed by its two-digit hexadecimal ASCII code — for example, a space becomes %20, an ampersand becomes %26, and a euro sign becomes %E2%82%AC. This is required because URLs can only contain a defined set of ASCII characters. Without encoding, special characters like &, =, and ? would be misinterpreted as URL syntax rather than data.

encodeURI() is designed for encoding a complete URL. It leaves structural characters such as :, /, ?, &, =, @, and # untouched so the URL remains valid. Use it when you have a full URL and only want to clean up unsafe characters. encodeURIComponent() encodes everything except A–Z, a–z, 0–9, -, _, ., ~, and * — including structural characters. Use it for individual query parameter keys and values, path segments, or any user-supplied string being inserted into a URL. Our "Full Component" toggle switches between these two modes.

Double encoding happens when a URL-encoded string is encoded a second time. For example, a space first becomes %20, then encoding that again turns %20 into %2520. This can occur when URLs pass through proxies, CDNs, redirect handlers, or frameworks that encode values without checking whether they are already encoded. Recursive Decode unrolls each layer one round at a time — up to 16 rounds — until no further %XX sequences can be decoded. Enable it whenever you see patterns like %2520, %253A, or %2526 in your encoded strings.

When the input (in Encode mode) or the output (in Decode mode) is a valid, parseable URL, the Breakdown panel appears automatically below the text areas. It color-codes the URL into five segments: Protocol (blue), Host (green), Path (slate), Query string (orange), and Hash (purple). Clicking any segment copies its value to the clipboard. The Query Parameters table below lists every key=value pair in the query string as editable inputs. You can modify values, add new parameters with the Add Param button, or delete rows. Pressing Apply to Input rebuilds the complete URL and places it in the input field ready to encode.

Each-Line mode processes your input line by line instead of as a single string. This is useful when you have a list of values that each need to be independently encoded or decoded — for example, a list of search keywords, a list of paths, or a batch of redirect targets. Without this mode, newline characters themselves would be encoded, turning your multi-line input into a single mangled string. With it, the structure of your list is preserved and each line gets its own clean result.

By default, JavaScript's encodeURIComponent produces lowercase hex digits — for example %2f, %3a, %20. The Uppercase Hex toggle converts all hex pairs to uppercase: %2F, %3A, %20. Both forms are functionally identical according to RFC 3986, but some APIs, code style guides, or security scanners require uppercase. Toggle it on to match your codebase or API specification.

No data is sent anywhere. All encoding, decoding, and URL parsing runs entirely in your browser using the built-in JavaScript functions encodeURI, encodeURIComponent, decodeURIComponent, and the WHATWG URL API. Nothing leaves your device. This means it is completely safe to use with sensitive URLs, API keys in query strings, authentication tokens, or any confidential data that requires URL encoding. The tool also works fully offline once the page has loaded.