URL Encoder / Decoder

A link with spaces breaks in an email. A query parameter containing “&” silently splits into two parameters. A UTM-tagged URL from an analytics report is full of %20, %3D and %26 and you just want to read it. All of these are URL-encoding problems.

This tool percent-encodes and decodes text for URLs in your browser. “Encode component” escapes everything that isn't safe inside a single query value or path segment; “Encode full URL” escapes only characters that are illegal anywhere in a URL, leaving :/?&=# intact; “Decode” turns percent sequences (and + signs) back into readable text.

A fourth button breaks a URL down into protocol, host, port, path, fragment and a decoded list of query parameters — handy for checking what a tracking link actually contains before you click or share it.

Unicode is handled correctly: text such as “ärger”, “کراچی” or emoji is encoded as UTF-8 bytes, which is what every modern browser and server expects.

Each line is processed separately, so you can paste a whole column of values or URLs from a spreadsheet and encode or decode them all at once, keeping one result per line.

How It Works

1. Paste text or URLs — one per line if you have several; each line is processed on its own.
2. Choose an action — encodeURIComponent for values, encodeURI for whole URLs, decodeURIComponent for decoding, or the URL breakdown, which uses the browser's WHATWG URL parser.
3. Copy the result — invalid percent sequences (like a lone “%”) produce a clear error instead of a garbled result.

Compatibility & Support

Supported Input → Output Formats

• Input: any text, URLs, query strings, form-encoded data (+ as space)
• Output: percent-encoded or decoded text, UTF-8; URL component breakdown
• Standards: RFC 3986 percent-encoding, WHATWG URL parsing

Unsupported Formats

This is percent-encoding only. Base64 is a different scheme — use the Base64 Encoder/Decoder. HTML entities such as & are not decoded here. Internationalized domain names are shown as the browser parses them (Punycode such as xn-- may appear in the host).

File Size Limits

No practical size limit for pasted text; each line is processed independently, so thousands of URLs convert instantly.

Keep in mind the limits on the other end: browsers handle URLs of tens of thousands of characters, but many servers, proxies and CDNs reject anything over about 8,000, and some older systems stop at 2,048. Encoding makes text longer — every non-ASCII character becomes six to twelve characters — so long encoded query strings are a common cause of mysterious “414 URI Too Long” errors.

Who Should Use This Tool?

• Students: A student building a search form in a web-development course checks how spaces and ampersands in a query should be encoded.
• Freelancers & Designers: A marketer builds UTM-tagged campaign links and encodes campaign names that contain spaces and ampersands.
• Office Professionals: An analyst decodes long tracking URLs from an ad report to read the campaign, source and medium values.
• Developers: A developer debugging an OAuth redirect decodes the redirect_uri parameter to find a double-encoding bug.

Why This Tool Beats the Alternatives

• Explains the difference between component and full-URL encoding instead of guessing.
• Built-in URL breakdown with decoded parameters.
• Clear errors for malformed input.
• No upload — useful for links that contain session tokens.
• Free and instant.

Pro Tips

• Encode each parameter value, not the whole URL, when building links by hand — otherwise & and = inside values break the query.
• If you see %2520, the text was encoded twice (the % of %20 was itself encoded as %25); decode twice to recover it and fix the code that double-encodes.
• Before clicking a suspicious shortened or tracking link, expand it and use the breakdown to see where it really goes — the host line shows the real destination domain, whatever the link text claimed.

Paste your text or URL above and choose Encode, Decode or Break down.