URL Encoder & Decoder Online — Free, No Upload
Encode strings for safe use inside URLs, decode percent-escaped input back to text, and break a full URL into scheme, host, path, and query parameters.
- Use component mode for a value that goes inside a query parameter.
- Use full-URL mode to keep ?, /, and & structural while escaping the rest.
- Decoding a URL in full mode also lists every query parameter as name/value rows.
Encoding, decoding, hashing, and UUID generation all run in your browser. The text and tokens you paste are never uploaded, stored, or logged.
Component vs full-URL encoding
Encoding a query value is not the same as encoding a whole URL. A value like hello world&more=true must have its & and = escaped, or the receiving server parses it as extra parameters. Component mode escapes everything reserved — that is the right choice for anything you are placing inside a URL.
Full-URL mode does the opposite: it keeps the structure characters (?, /, &, :, #) doing their structural jobs and escapes only the content. Use it when you have a mostly-valid URL with a few unsafe characters in it.
Debugging percent-encoding problems
Double-encoding is the classic failure: %2520 in a URL is a space that got encoded twice, because %25 is itself the escape for %. Decode the string once here to see what a server would actually receive, and check whether one more layer of %25 is hiding inside.
The + character is a second, older space convention used by HTML forms — some servers decode it as a space, others literally. If a + survives decoding and should be a space, enable the + → space option.
Frequently asked questions
When should I use component mode instead of full-URL mode?
Component mode for values placed inside a URL (query parameter values, path segments you build yourself). Full-URL mode when the input is already a URL and you only want the unsafe characters escaped without breaking its structure.
Why do I see %25 in my URL?
%25 is the percent-encoding of the % character itself. It usually means the string was encoded twice — decode it once here to confirm.
Does this tool send my URLs anywhere?
No. Parsing and encoding happen locally in your browser. URLs often contain tokens or internal hostnames, so nothing leaves your device.