Skip to content

URL Parser

URL Parser parses a single URL or relative path locally into protocol, credentials, host, port, path, hash, and query parameter rows, lets you edit them, and previews the rebuilt URL.

Input URL

Auto add https:// when missing scheme

Characters

0 / 500,000

Details

Protocol

Hostname

Port

Username / Password

Username

Password

Pathname

Hash

Query parameters

0

No parameters

Output URL

URL Parser

Quick Start

1
Paste a full URL, host, relative path, ?query, or #hash; auto parsing runs after typing, or use Re-parse.
2
In "Details", edit protocol, username/password, hostname, port, pathname, and hash.
3
In "Query parameters", add, remove, or edit key-value rows; rows with empty keys are ignored in the rebuilt output.
4
"Output URL" updates from the current fields and query rows and can be copied as text, with no file export.
5
Keep "Auto add https:// when missing scheme" enabled for bare domains or host:port; enter ftp:, mailto:, or custom schemes explicitly.

Common Scenarios

API debugging

break down endpoint URLs, inspect or adjust query parameters, and quickly pinpoint parameter issues.

Link analysis

unpack complex marketing or tracking URL text to inspect UTM parameters, referrer values, and target paths.

Parameter tuning

quickly add, remove, and edit paging, filtering, sorting, and other query parameters with less manual URL concatenation.

Link cleanup

remove unnecessary tracking parameters before sharing a cleaner URL.

Redirect troubleshooting

inspect redirect URL text and confirm the target host, port, path, and parameters without following the redirect.

Deep-link inspection

paste custom-scheme links to preview rebuilt text, with limited field editing for non-hierarchical schemes.

Usage Advice

When input has no scheme and looks like a domain or host:port, keeping "Auto add https:// when missing scheme" enabled is recommended. To test a specific scheme, enter the full scheme prefix directly.
Query key/value rows are percent-encoded on output and safely decoded on parse; spaces output as %20, while literal + stays +.
If the regular query before # is empty and the fragment contains ?foo=1, the tool treats it as query parameters inside the hash.
Relative paths are supported (for example, /api/users?page=2). The internal base is only used for parsing, so protocol and hostname stay empty in relative output.
After editing, copy from "Output URL" with one click to avoid manual concatenation errors.
Need standalone encoding/decoding for a value? Use the companion tool "URL Encoder/Decoder".

Parsing & Rebuild Boundaries

Single input: this is one URL/text parser, not file upload, URL list import, log batch cleanup, or a background queue.
Query rows: duplicate keys stay as separate rows, empty keys are omitted from output, and nested object/array formats are not converted.
Large query strings: more than 100 query rows are paged in the UI, while the rebuilt output still includes all rows.
Encoding: spaces are written as %20; literal + stays + and is not treated as a form-urlencoded space.
Network boundary: the tool does not request the URL, follow redirects, check DNS/TLS/HTTP status, or verify reachability.
Output boundary: copy the rebuilt URL from the editor; there is no JSON, CSV, file export, share link, QR code, or short URL creation.

Limitations & Compatibility

This tool relies on the browser's built-in URL API; some non-standard URL formats may fail to parse. Field-based editing and reassembly of opaque or non-hierarchical schemes like mailto:, data:, and file: are limited.
This is not an application/x-www-form-urlencoded serializer: it does not turn + into spaces, choose charsets, or build request bodies.
Input limits: visitors can process up to 500,000 characters, signed-in users 2,000,000, and subscribers 5,000,000; split long URL lists or logs before parsing.

Privacy & Security

All processing happens locally in your browser. The current input is kept as a session draft on this device, and the auto-HTTPS preference is saved as a device setting.
Username/password in URLs are displayed in plain text. Copying the rebuilt URL also includes credentials if those fields remain filled.
This tool only parses and assembles URLs. It does not send HTTP requests or visit target addresses.

FAQ

6

Continue with these related tools for the next step.

All tool processing happens locally in your browser.