URLs can only contain a limited set of characters. Spaces, accented letters, emoji and symbols like &, ? and # have to be percent-encoded: a space becomes %20, "é" becomes %C3%A9, and so on. Get it wrong and links break, form values get cut off at the first ampersand, or tracking parameters stop working. This free URL encoder and decoder converts in both directions as you type. Choose component mode (like JavaScript's encodeURIComponent) to encode a single value you're putting into a query string, where every reserved character such as / ? & = is escaped. Choose full URL mode (like encodeURI) to tidy a whole address while keeping its structure intact. Tick "spaces as +" for HTML form-style encoding. Decoding handles both %20 and +, and tells you if a sequence is malformed instead of silently failing. Paste a full link and the URL parser breaks it into protocol, host, path, hash and a table of decoded query parameters. That's handy for debugging UTM tags, redirect URLs and API calls. Everything runs in your browser, so the URLs you paste, including ones with tokens, never leave your device.
Encode or decode
URL parser
How to use it
- Choose Encode or Decode and a mode.
- Type or paste; the result updates live.
- Paste a full link into the parser to see its parts and query values.
Component vs full URL
| Input | Component | Full URL |
|---|---|---|
| a b&c/d | a%20b%26c%2Fd | a%20b&c/d |
FAQ
When should I use component mode?
When encoding a single value, like a search term or redirect URL, that goes inside a query string.
What is the difference between %20 and +?
Both mean a space in query strings from HTML forms; %20 is valid everywhere in a URL, + only in the query.
Why do I get “malformed” when decoding?
The text has a % not followed by two valid hex digits, or an invalid UTF-8 sequence.
Are my URLs sent anywhere?
No. Everything runs locally.
Comments
Post a Comment