URL Encoder Decoder

A URL encoder decoder converts text to and from percent-encoding — the %XX form that lets a link safely carry spaces, accents, emoji and reserved characters like &, ? and #. Paste a value to encode it, or paste an encoded string to decode it back into readable text. Everything runs in your browser, so API keys, tokens and private links never leave your machine.

The most common URL-encoding mistake is picking the wrong mode, and this tool makes the choice obvious. Component encoding (encodeURIComponent) escapes every reserved character — use it for a single query-parameter value. Full URL encoding (encodeURI) keeps the structure of a complete link intact, escaping only unsafe characters like spaces. Form mode encodes the way an HTML form does, turning spaces into a plus sign. A short hint under each mode tells you which to reach for, so you never break a link by over-encoding it, and an Auto option picks the right one for you.

Decode URLs and query parameters

Decoding turns %20 back into a space, %C3%A9 back into an accented letter, and so on. When you decode a full URL, a live breakdown appears underneath: the scheme, host, port, path, fragment, and a table of every query parameter with its value already decoded. That makes this a fast way to read a messy tracking or callback link — you can see exactly what q, utm_source or a nested redirect actually contains, without picking the string apart by hand.

Recursive decoding for double-encoded links

Sometimes a value has been encoded more than once, so a space shows up as %2520 instead of %20. Turn on recursive decoding and the URL encoder decoder keeps unwinding the string until the text stops changing, then tells you how many levels it peeled back. It is the quickest way to untangle a link that has passed through several systems, each one adding another layer of encoding on top of the last.

When do you need to encode a URL?

You reach for a URL encoder whenever data has to travel inside a link. Building an API request, you encode search terms, IDs and filters so a stray & or = cannot corrupt the query string. Sharing a link that contains a space or a non-English character, you encode it so it survives every browser, server and CDN along the way. Debugging a redirect, you decode the URL to read what it really points to. Marketing teams encode UTM values and campaign names so commas and spaces make it through the redirect chain unchanged. In every case the rule of thumb is the same: encode a component when in doubt, and only use full-URL encoding on a complete, already-valid link.

Batch, files, and clean output

Work on one value or many. Batch mode encodes or decodes each line on its own, so a whole list of URLs or query values is converted in a single pass, with any malformed line clearly flagged. You can upload a .txt file or drop one onto the box, copy the result, or download it. Character, byte and encoded-sequence counts sit under the output, so you always know precisely what changed — handy when a single stray character is breaking a request.

Pulled a pile of links out of a document first? Extract URLs from Text does that, and once you have a clean list, the Broken Link Checker tells you which ones still work. A URL encoder decoder is usually one step in that chain — encode a value for an API call, or decode a link to see where it really points.