URL & URI tools
A URL breaks in a dozen small ways: a query parameter that should repeat but gets overwritten, a relative path that resolves against the wrong base, or a connection string pasted into a config file that hides its own host and port. Developers land here to pull a URL apart into scheme, host, path and query, encode or decode individual pieces, and build campaign or API links without hand-editing percent-encoded strings.
Pick the URL parser to see how a browser would read a given URL, the URL normalizer when you need to resolve a relative path or control percent-encoding, and the URI template tester for RFC 6570 templates used in API path definitions. The database URL parser is specialized for pulling host, port, credentials and database name out of connection strings. All of these tools process input locally in the browser.
7 tools
All URL / URI Tools tools
-
URI template tester
Expand RFC 6570 URI templates and inspect each expression encoding
-
URL parser
Break down URLs into components and reveal how the runtime normalizes each one
-
URL normalizer & joiner
Normalize URLs, resolve relative paths and control percent encoding
-
UTM link builder
Create campaign links with explicit merge rules from CSV batches
-
Query string builder
Build URL parameters preserving repeated keys and empty values
-
URL encoder
Encode or decode URL components, full URIs and form field values
-
Database URL parser
Extract host, port, credentials and database from connection strings
URL / URI Tools tools FAQ
They're the same mechanism described two ways: percent-encoding replaces reserved or non-ASCII bytes with a % followed by two hex digits. The URL encoder here applies it separately to full URIs, individual components or form field values, since each context reserves a different set of characters.
Resolution depends on the base URL and on how the path uses ./ and ../ segments. The URL normalizer & joiner resolves a relative path against a base exactly as a browser would, so you can check the resolved result before shipping a redirect or a link.
Paste the connection string into the database URL parser to extract the host, port, username, password and database name separately. It handles common connection string styles without you having to write a regular expression to split them yourself.