URL / URI Tools
Normalize an address, resolve a reference or append a path.
Computed in this browser. The entered address is never opened or requested.
HTTP(S) only. Host and scheme casing, default ports and dot segments follow the browser. Reserved escapes stay encoded; no SEO canonical guarantee.
Input and active base: 100,000 UTF-16 units each. Output: 1,000,000 units.
Ready · 59 units · Query parameters: 3
A URL normalizer helps when a copied API endpoint has mixed host casing, redundant dot segments or inconsistent escape spelling. Start with the supplied example to see which parts change before using your own address.
A base ending in /api/v1 can mean a document location or a directory to append to. Choose the operation explicitly; a slash at the join boundary is a different decision from resolving a browser link.
The URL normalizer makes a common endpoint mistake visible. With base https://example.com/api/v1, resolving users yields /api/users, while joining yields /api/v1/users. Switch modes to check which interpretation your application needs.
Repeated tag keys stay in their original order. A flag without = stays different from an empty value, and + is not rewritten as %20. Encoding choices are separate from deletion, so you can inspect an escape spelling without sorting the query.
Select Normalize for an explicit http:// or https:// URL. The base field is inactive in this mode. For relative references, select Resolve and supply the page address from which the link should be interpreted.
Resolve treats a base without a trailing slash as a file location. Join appends to the complete base pathname and retains its query and fragment. Join accepts one path, including nested folders; references containing ? or # belong in Resolve.
Automatic mode waits 350 ms after edits. Turn it off to run with Ctrl/Cmd + Enter. A changed input or option disables exports until the result is fresh. Preview replacement shows counts; applying it switches to Normalize and clears the base. Undo restores the previous state.
URL normalization uses the browser URL parser for lowercase scheme and host, default-port removal and dot-segment resolution. HTTP :80 and HTTPS :443 disappear; other ports remain. International domain names become ASCII/Punycode, while Unicode path characters receive percent encoding.
Keep the parsed escape spelling, uppercase hexadecimal pairs, or decode ASCII unreserved characters: letters, digits and -._~. In the last mode, remaining escapes are uppercased. Reserved %2F, %3F and %23 stay encoded, and %252F is never recursively decoded.
The URL path joiner appends a path after the whole base pathname and adjusts only the joining seam. Internal // segments remain. To resolve relative URLs, use the separate browser-style mode, which understands parent paths, root paths, query-only and fragment-only references.
Use Resolve with the absolute page URL as the base and the relative reference as input. The URL constructor applies directory, parent and root rules. Use Join only when you intend to append a path after every segment of the base, regardless of its trailing slash.
A base ending in /a/b has current directory /a/. Resolving c therefore produces /a/c. Add a trailing slash to make /a/b/ the directory, or choose Join to get /a/b/c. The difference comes from reference resolution, not from a missing string concatenation step.
The hexadecimal letters inside a percent escape are case-insensitive: %7e and %7E represent the same byte. This does not make the whole URL case-insensitive. A path segment named File can differ from file; the tool preserves path casing.
Do not assume so. A literal / separates path segments, while %2F represents an encoded reserved character. Servers and routers can interpret these differently. Even Decode unreserved leaves %2F encoded, preventing an encoding cleanup from introducing a new path separator.
A text transform cannot determine search-engine canonical selection or whether two pages have identical content. Query order can also affect signatures or application behavior. This tool preserves the sequence by default; decide a canonical policy using your site behavior and indexing configuration.
Something looks wrong?
Use the URL normalizer to compare the current spelling with the result. Confirm the chosen operation and deletion counts before copying the link or applying it to the input.