URL input
Encode, decode, or parse
Ready.
Web tool
URL Encoder Decoder
Encode full URLs, encode URL components, decode percent-encoded text, parse URL parts, and inspect query parameters. Useful for APIs, redirects, analytics links, forms, and debugging.
Parsed URL
URL parts
Protocolhttps:
Hostexample.com
Pathname/search
Search?q=free tools&lang=en
Hash#top
Originhttps://example.com
Query parameters
| Name | Value | Encoded name | Encoded value |
|---|
Reserved and common encoded characters
| Character | Meaning | Encoded |
|---|---|---|
| space | Word separator | %20 or + in form data |
| % | Percent-encoding marker | %25 |
| & | Query parameter separator | %26 |
| = | Query name/value separator | %3D |
| ? | Query string start | %3F |
| # | Fragment start | %23 |
| / | Path separator | %2F |
| : | Scheme separator | %3A |
| + | Plus sign or form space | %2B |
Encoding notes
Full URLUse full URL mode when you want to preserve URL syntax such as : / ? & = #.
URL componentUse component mode for one query value, path segment, or fragment value.
Form encodingHTML form encoding usually represents spaces as + instead of %20.
Double encodingIf % becomes %25, the URL may have been encoded twice.
Popular URL encoding examples
FAQ
What is URL encoding?
URL encoding, also called percent-encoding, replaces unsafe URL characters with a percent sign followed by two hexadecimal digits.
Should I encode a full URL or a component?
Encode a full URL only when you want to preserve the URL structure. Encode a component when you are inserting a value into a query parameter, path segment, or fragment.
Why does a space sometimes become +?
In application/x-www-form-urlencoded form data, spaces are represented as +. In normal URL percent-encoding, spaces are usually %20.