URL Encoder
Encode or decode URL components and full URLs.
About URL Encoder
URL Encoder percent-encodes and decodes URL components and full URLs, making text safe to drop into a query string or pulling a human-readable value back out. Reach for it when a link breaks on spaces or special characters, or when you need to read what an encoded parameter actually says. It all runs in your browser, so nothing you paste is sent anywhere.
- Category
- convert
- Input
- Accepts: text/plain.
- Output
- Outputs: text/plain.
- Cost
- Free, runs in your browser
- Memory
- low
Common uses
- Encode a search term with spaces and ampersands so it survives inside a query string
- Decode a messy %20- and %3D-laden URL to read the parameter values plainly
- Safely build a redirect URL that carries another URL as a parameter
- Fix a tracking link that breaks because a value contains reserved characters
- Decode an OAuth or callback URL to inspect what it's passing along
- Prepare a value with unicode or symbols for use in an API request path
Frequently asked questions
What's the difference between encoding a component and a full URL?
Encoding a component escapes reserved characters like & and = so they stay literal inside one value. Full-URL encoding leaves the structural characters that separate the scheme, host, and query intact.
Does it handle unicode and emoji?
Yes. Non-ASCII characters are percent-encoded using their UTF-8 byte sequence and decode back to the original text.
Is my input sent to a server?
No. Encoding and decoding run entirely in your browser, so URLs containing tokens or personal data stay on your device.
Why did encoding leave some characters unchanged?
Characters that are already safe in a URL, such as letters, digits, and a few symbols, are left as-is. Only reserved or unsafe characters get percent-encoded.
Can it fix a double-encoded URL?
Decode once to undo a single layer; run it again to peel a second layer if a value was encoded twice.
Keywords
- url
- encode
- decode
- percent
- uri
- query
- string