URL Encoder
Escape the characters a URL cannot carry, either as a single component or as a whole address. The distinction between the two escaping functions is the one that breaks most integrations: a component escapes the separators, a URL keeps them so it still parses. Furtu shows which one it used.
Component mode escapes the path, query and fragment separators, which is right for one value. URL mode leaves them alone so the address still works.
Both forms are legal; some servers accept only one.
How url encoder works
- Paste the value or the URLThe tool warns if the input is already partly encoded.
- Choose component or whole URLThe difference decides whether the separators survive.
- Copy the resultThe function used is named in the read-out, so you know what happened.
What you get
Percent-encode a value or a whole URL, and know which one you needed. Everything happens inside this page: the file is read by your browser, transformed in memory and handed straight back to you as a download. There is no upload queue, no waiting for a server, and nothing left behind when you close the tab.
Supported formats
This tool works on text you paste or type, so there is no file format to worry about. Nothing you type is sent anywhere.
Limitations, stated up front
- This encodes a value you paste. It does not build a query string, choose a parameter order, or add a signature.
- Spaces become %20 rather than a plus, which is right for URLs but not for a form body.
Frequently asked questions
When do I need one escaping function and when the other?
The component function for a value that becomes part of a URL — a search term, a redirect target, one query parameter. It escapes the path, query and fragment separators along with everything else, so the value cannot break the structure. The whole-URL function for an address you are assembling, because it leaves those separators intact and the result still parses. Using the wrong one produces a URL that looks right and does not work.
What about plus signs for spaces?
Percent-encoding turns a space into %20, which is correct for a URL path or fragment. An HTML form submitted as form-encoded data uses a literal plus for a space instead, because that is what that encoding has always done. Furtu encodes to %20 and the decoder can read either.
What does the double-encoding warning mean?
The input already contains percent-escapes. Encoding it again turns %20 into %2520, and the server reads that as the literal text %20 rather than a space. That is the most common cause of a value arriving with an escape still in it. Decode first if that is what you meant.
Does it touch the network?
No. The encoding uses the two functions built into the browser, and the result appears immediately without a request.
Is the text or URL I encode uploaded?
No. Encoding is a pure string operation performed in your browser, so a query parameter containing a token is never transmitted.