URL Encoder / Decoder
Percent-encodes and decodes text for URLs.
Split a URL into its parts: scheme, host, port, path, query parameters, and fragment. Edit the parameters in a table and get the rebuilt URL straight away.
| Part | Value |
|---|
../img/logo.png, also fill in Base URL.The URL is parsed with your browser's WHATWG URL parser, the same rules browsers use to follow links:
scheme://user:password@host:port/path?query#fragment
xn--...) that DNS uses next to them.URLSearchParams, so + means a space and repeated names such as tags=a&tags=b are kept as separate rows.https://user:pass@münchen.example.de:8443/shop/items/42?sort=price&tags=a&tags=b#reviews:
https, host münchen.example.de (Punycode xn--mnchen-3ya.example.de), port 8443./shop/items/42, 3 segments.sort=price, tags=a, tags=b. Fragment reviews.../img/logo.png with base https://example.com/docs/guide/ resolves to https://example.com/docs/img/logo.png.
#) is never sent to the server; it only matters in the browser.Scheme (https), host (example.com), optional port, path (/page), query string (?a=1), and fragment (#section). Some URLs also have a username and password before the host.
The ASCII form of an international domain name, starting with xn--. DNS only handles ASCII, so münchen.de is looked up as xn--mnchen-3ya.de.
Usually the scheme is missing (add https://), the port isn't a number from 0 to 65535, or the host contains a space or another character hosts can't have.
No. It is parsed in your browser, and the address is never requested.
Often used together with the URL Parser.
Percent-encodes and decodes text for URLs.
Builds copy-ready cURL commands with headers, auth, and a body, quoted for your shell.
Pulls every link out of text or HTML source.