URL Encoder

Percent-encode text for URLs, or decode a messy link back to readable characters.

How URL Encoder works

Encode text as a URL component or a full URL, and decode percent-encoded links back to plain text. Everything happens inside this page: the tool reads your input, runs the calculation or conversion locally, and hands the result back to you. Nothing is transmitted, because there is no backend to transmit it to.

That design choice is deliberate. Most free tool sites upload your files to a server, process them there, and quietly keep a copy. Toolcin cannot do that — the site is a set of static files. If your connection dropped the moment the page finished loading, every tool would still work.

Two modes, two different jobs

Component mode encodes everything that is not unreserved, so a space becomes %20 and a slash becomes %2F. That is what you want for a single query value.

Full-URL mode leaves the structural characters alone — colon, slash, question mark, hash, ampersand and equals — so an entire URL can be made safe without breaking its structure. Use it when the URL itself is the value being passed along.

When encoding is not optional

A query value containing & will silently truncate the parameter list if it is not encoded. A value containing # will be read as a fragment and everything after it disappears from the server's view. A space may survive in a browser and fail in a proxy.

Non-ASCII text is always encoded: Urdu or Chinese characters become percent-encoded UTF-8 byte sequences, which is why an encoded URL looks much longer than the text it represents.

CharacterComponent modeWhy
space%20Not allowed unencoded in a URL
&%26Would split the query string
#%23Would start a fragment
/%2FWould be read as a path separator
é%C3%A9UTF-8 bytes, two of them

Decoding is not the same as cleaning

Decoding turns %20 back into a space. It does not validate the URL, strip tracking parameters or fix a malformed query string — those are separate jobs. A decoded URL that still does not work has a structural problem, not an encoding one.

Malformed percent sequences cause the decoder to throw, which is the correct behaviour: guessing what was meant is how stray characters end up in a database.

Good to know

  • Works offline once loaded, including on flights and in locked-down networks.
  • No file size limit beyond your device's own memory.
  • Free to use, with no account and no usage counter.
  • Results are produced locally, so they are not logged or shared with anyone.

Questions

What is the difference between the two modes?

Component mode encodes slashes and question marks too; URL mode keeps them so the link structure survives.

Why does + appear in decoded text?

Form encoding uses + for spaces, so it is converted back to a space when decoding.

Should I encode a whole URL or just the parameters?

Encode the values, not the structure. Use full-URL mode only when the URL is being passed as a single value.

Does + mean space?

In form submissions, yes. In a path or fragment, no — only %20 is a space there.

Keep going

More encoding tools