Relative URL Resolver
Resolve a relative reference against a base URL to produce the absolute target in the browser.
Resolve relative references against a base URL
HTML, CSS, and RFC 3986 hyperlinks often use relative paths such as ../assets/app.css or
?page=2#reviews. Browsers resolve these against the current document URL.
This tool applies the same algorithm as the built-in URL constructor so you can preview the absolute
href before deploying sitemaps, canonical tags, or API documentation.
Supported reference types
- Path-relative references (
../sibling,child/file) - Root-relative paths (
/static/logo.svg) - Query-only and fragment-only updates (
?q=test,#section) - Absolute URLs, which replace the base when the reference includes a scheme
Inspect full HTTP messages with the HTTP Message Parser or normalize hosts and paths using related URL utilities on the site.
Frequently Asked Questions
Which base URL should I use?
Use the URL of the document that contains the relative link, for example the final canonical page URL including trailing slashes if your server expects them.
Does resolution match Node or curl?
The result matches modern browsers and the WHATWG URL specification, which aligns with Node.js new URL(relative, base).
Are internationalized domain names supported?
Punycode hostnames in the base URL are resolved correctly. Enter IDNs in their ASCII (xn--) form for predictable results.