URL Encoder & Decoder
Percent-encode text for use in a URL, or decode an encoded URL back into readable form. Choose between encoding a single component – a query value or path segment – and encoding a complete URL, which preserves the characters that give it structure.
Everything happens in your browser, so query strings containing tokens or personal data stay local.
How to use the url encoder & decoder
Paste your URL or text.
Choose encode component, encode full URL, or decode.
Copy the result.
Why use the Convert Now url encoder & decoder
Both encoders
Component and full-URL modes, clearly explained.
Decoder included
Turn percent-encoded strings back into readable text.
Unicode safe
Correct UTF-8 handling for any language.
Private
Query strings with tokens stay on your device.
Why URLs need encoding
URLs may only contain a limited set of ASCII characters, and several of those have structural meaning: ? starts the query, & separates parameters, = joins a key to its value, # begins the fragment. If a value contains any of them – a search for "tea & coffee", say – it must be percent-encoded, or the server will read it as the start of a new parameter. Spaces must be encoded too, which is why they appear as %20.
encodeURI versus encodeURIComponent
This is the distinction that causes most bugs. encodeURIComponent escapes everything that is not safe in a value, including / ? & = and #, and is what you want for a single query parameter or path segment. encodeURI leaves those structural characters alone because it assumes you are handing it a whole URL. Use the wrong one on a complete URL and you get https%3A%2F%2F…; use the wrong one on a value containing an ampersand and your parameter silently splits in two.
Non-ASCII characters and internationalised domains
Characters outside ASCII are converted to UTF-8 bytes and then percent-encoded, so a single accented letter becomes two escape sequences and many CJK characters become three. Domain names work differently: they use Punycode rather than percent-encoding, which is why an internationalised domain appears as xn-- followed by an encoded form rather than as percent escapes.
Read the guide: How to Create a Strong Password (That You Can Remember)
Frequently asked questions
What is URL encoding?
Also called percent encoding: replacing characters that are unsafe or structurally meaningful in a URL with a % followed by their hexadecimal byte value.
What is the difference between encodeURI and encodeURIComponent?
encodeURIComponent escapes structural characters like / ? & = and is for individual values. encodeURI preserves them and is for encoding a complete URL.
Why do spaces become %20?
Spaces are not permitted in URLs, so they are encoded as %20. In query strings a plus sign is sometimes used instead, a legacy of HTML form encoding.
How do I decode a URL?
Paste the encoded string and click Decode to get the readable version back.
Does it handle non-English characters?
Yes. They are converted to UTF-8 and percent-encoded, and decode back correctly.
Is my URL sent to a server?
No, encoding and decoding happen in your browser.
Developer Tools — all free
Every tool on Convert Now runs in your browser. No account, no limits, nothing uploaded.
Browse all developer tools