URL Encode Decode
Encode URLs, decode URL components, and inspect query parameters in one clean tool.
- Encode URLs
- Decode URLs
- Query Params
- Copy Output
- No Upload
Choose an action to generate output.
Context-aware URL encoding and decoding
URL percent-encoding is context dependent. A complete URI must preserve structural delimiters, while a component or query value must encode delimiters when they represent data.
The query inspector parses full and relative URLs without opening them, separates URL parts, preserves repeated parameters, and shows a normalized result for review.
How to encode, decode, or inspect a URL
- Choose Encode or Decode and select URL component, Full URI, Path segments, Query value, or Form field context.
- Paste text, open or drop a local text file up to 1 MB, or load an example; optional line mode processes each line separately.
- For decoding, keep one pass for the safest result or explicitly select additional passes for nested input.
- Review live output, exact malformed percent or Unicode diagnostics, byte counts, escapes, lines, and size change.
- Copy or download the exact output, or inspect a full or relative URL and its query parameters without visiting it.
Use the correct encoding rules and inspect exact results
- Use component mode for one data value, Full URI for existing URL structure, or path mode to preserve slash separators.
- Choose query value for percent-encoded spaces or Form field for application/x-www-form-urlencoded plus semantics.
- Reject malformed percent escapes, invalid UTF-8 byte runs, and unpaired Unicode surrogates with exact line and column positions.
- Inspect absolute, protocol-relative, and relative URLs with masked credential presence, decoded parameters, repeated keys, empty values, and malformed escape flags.
- Keep input private in the browser with no navigation, URL request, or server upload.
URL Encoding FAQ
What is the difference between full URI and component encoding?
Full URI mode preserves delimiters that define URL structure. Component mode escapes those delimiters because the entire input is treated as data.
Does plus always mean a space?
No. Plus represents a space in application/x-www-form-urlencoded query or form data. In a generic URL component, a literal plus remains a plus unless encoded as %2B.
Why did decoding stop with an error?
Every percent sign must have two hexadecimal digits and encoded byte runs must form valid UTF-8. The tool reports the first detectable invalid position instead of returning partial output.
Is decoding multiple times safe?
One pass is safest. Additional passes can reveal nested encoding but may also transform security-sensitive sequences, so the pass count is explicit.
Does the inspector open the entered URL?
No. It uses the browser URL parser locally and never navigates to or requests the address.
Help us improve this tool
Please share what we should improve, add, or fix. You can write in the language you are comfortable with. We only save your suggestion and IP address to prevent misuse.