URL Parser
Split any URL into protocol, host, path segments and a query-param table with encoded/decoded pairs.
When an API call misbehaves, the URL is the crime scene: did the parameter get encoded twice, is the path segment right, which port is actually in play. This tool lays the URL out — protocol, host, port, numbered path segments, a query table with the raw encoded value next to its decoded form, fragment, credentials — all in one view.
Parsing uses the browser's native URL API, the exact same interpretation fetch and axios will apply. The params table converts to JSON with one click for pasting into code or docs. Everything stays local, so URLs carrying tokens or signed parameters are safe to inspect.
Why encoded and decoded side by side
%E4%B8%AD is unreadable to humans, but server logs store the encoded wire form while URLSearchParams in code reads the decoded one. Showing both kills the classic "the parameter looks different" confusion — first decide which layer's value you are comparing against.
Embedded credentials are deprecated
https://user:[email protected] embeds secrets in the URL — browsers are removing support (fetch ignores them) and security reviews flag it. When a credentials segment is detected, the tool says so plainly: it still parses, but it should not appear in new code.
Frequently asked questions
- Does it handle relative paths?
- No. A relative path (/api/items) has no host to dissect — absolute URLs with a scheme only. For relative paths, resolve them against a base with the URL constructor first.
- Does the result match the browser address bar?
- Yes — same URL API underneath, including default-port elision (https drops 443) and preserved non-standard ports (:8443).
- Are tokens in the URL uploaded?
- No. Parsing is local and the page has no backend. Signed links are safe to paste.