Resolve a reference against a known base
Enter a relative reference and a complete HTTP or HTTPS Base URL, then choose Resolve reference. The browser URL parser combines them and returns normalized URL text. It does not fetch the result, confirm that a resource exists or open a new tab.
Example: move up one directory
The default base is https://example.com/docs/page?tag=red&tag=blue. Resolving ../images/icon.png?size=2#preview produces https://example.com/images/icon.png?size=2#preview. The base path's final segment is treated as a file-like segment because it lacks a trailing slash. A base ending in /docs/page/ would resolve the same reference differently.
Different reference forms
A leading slash replaces the path from the host root. A query-only reference replaces the query while retaining the base path. A fragment-only reference retains the base query. An absolute HTTP URL replaces the base entirely; a protocol-relative reference can change the host. Check the displayed origin before using a resolved URL elsewhere.
An empty reference resolves to the base URL under standard URL behavior, normally without its fragment. Leading or trailing parser whitespace and dot segments can normalize. This is browser URL resolution, not filesystem path joining, HTML base-element discovery or a redirect checker.
Input boundaries
The base and result are restricted to HTTP/HTTPS URLs without embedded credentials. Non-web schemes such as javascript, data and file are rejected. Keep references and bases within 10,000 characters. Unpaired surrogate input is rejected. The output TXT is a normalized URL, not a promise of an accessible or trustworthy destination.
Use URL Query Editor for explicit query changes, or URL Query Difference Viewer to compare the resolved query with another URL.
Changing any input or option clears the prior result and download. Processing stays in this browser; no source file is changed.





