URL Encoder and Decoder

URL-component encoding (encodeURIComponent) escapes every character that has a special meaning in a URL — slashes, question marks, ampersands, equals signs, hash marks — so the text can be embedded safely as a single value. Full-URL encoding (encodeURI) preserves the URL's structure and only escapes characters that are truly illegal in a URL, such as spaces and most non-ASCII characters. Use component mode for a value going inside a URL; use full-URL mode for an already-complete URL that just needs fixing up.

Choose the Encode direction, pick the URL component scope if your text is a single value such as a search term or a query parameter, type or paste it in the top box, and copy the encoded result. The conversion updates live as you type.

Switch to the Decode direction, paste the percent-encoded string, and choose the same scope it was encoded with — component for encodeURIComponent output, full-URL for encodeURI output. If the input contains a malformed sequence, like a percent sign not followed by two hex digits, you will see a plain-English explanation instead of an error dump.

That is percent-encoding: any character that cannot appear literally in a URL is replaced by a percent sign followed by two hexadecimal digits representing its UTF-8 bytes. For example, a space becomes %20, a slash becomes %2F, and the emoji 🎉 becomes %F0%9F%8E%89 because it takes four bytes in UTF-8.

Both mean a space, but they come from different conventions. encodeURIComponent — which this tool uses in component mode — always produces %20 and never +. The + convention comes from HTML form submissions (application/x-www-form-urlencoded), where spaces in form data are sent as +. This tool's decoder treats a literal + as a plus sign (the strict standard), while the query-string parser converts + to a space, matching how real web servers read form data.

Paste a full URL (for example, https://example.com/search?q=codex%20tools&lang=en) or just its query part (?q=codex%20tools&lang=en) and the parser splits it into a table of parameter names and decoded values. It handles repeated keys, empty values, and percent-encoded characters automatically.

Each occurrence gets its own row in the table, in the order it appears. Nothing is merged or overwritten, so ?tag=a&tag=b shows two rows — tag = a and tag = b. Parameters with no value, like ?flag, or an empty value, like ?q=, are shown as (empty).

Decoding fails when a percent sign is not followed by exactly two hexadecimal digits — for example, %2, %zz, or a stray % at the end of the string. A literal percent sign must itself be encoded as %25. The tool checks this before decoding and reports the problem in plain language.

No. Everything happens in your browser with JavaScript only. Nothing you type is sent to a server, stored, or logged.