URL Inspector & Query Editor

How to inspect and edit a URL

1. Paste a complete http:// or https:// URL and choose Inspect URL.
2. Review the host, path and fragment separately from the query parameters.
3. Edit a name or value, keep repeated names in the intended order, and add or remove rows as needed.
4. Choose Build edited URL, then copy or download the result.

The tool never opens the address. It uses the browser’s URL and URLSearchParams parsers. Invalid input, unsupported protocols and embedded credentials produce a message instead of a navigable link. Input is limited to 20,000 characters and 500 parameters to keep editing manageable.

A query example you can verify

For https://example.com/search?q=coffee+beans&tag=guide&tag=travel#results, the host is example.com, the path is /search and the fragment is #results. The query has three rows: q with the decoded value coffee beans, then two separate tag values.

Editing a value to tea & cake does not require typing its percent encoding. Rebuilding encodes it as a query value. A literal plus sign should be entered as + in the decoded editor; the serializer can represent it as %2B, while a space can serialize as +.

Normalization, tracking keys and important limits

Rebuilding preserves parameter order and repeated names but normalizes encoding. That can change the original byte sequence even when a decoded value is the same. It is unsuitable for reproducing a signed URL byte for byte. Keep the original before editing anything used for authentication, signature validation or a payment flow.

Tracking removal is off by default. It removes only the displayed list when you explicitly check it and rebuild. A parameter outside that list can still identify a user, and removing a known key is not a security assessment.

The tool does not resolve redirects, verify a certificate, check DNS or certify that the site is safe. Unicode host names may appear in their encoded ASCII form. Read the parsed host carefully, and do not assume that a familiar word in a path identifies the destination.

Local processing and a practical privacy boundary

URL input and edited values stay in the open page; this tool does not store them or put them in this page’s address. Clearing or leaving the tab removes the working state. A downloaded file or clipboard copy is your own retained copy and may be visible to other software on your device.

Remove passwords and avoid pasting confidential access tokens when they are not needed for the task. The tool rejects embedded username/password syntax. It does not detect every secret that someone could place inside a query parameter.

If JavaScript is disabled, the explanation remains readable and the action buttons stay disabled. You can use the static example above to understand the components without implying that the editor has run.

Boundary and failure cases

Rebuilding a URL normalizes encoding. That is helpful for readability and disastrous for signed URLs, HMAC query strings and some payment return links whose signatures cover the exact original bytes. Keep a copy of the untouched URL before editing.

Tracking-key removal only deletes the listed marketing parameters. Session ids, email hashes and custom campaign keys can still identify a person. Treat the cleaned URL as partially sanitized, not anonymized.

Credentials embedded in userinfo (https://user:pass@host/) are rejected or warned rather than turned into a clickable navigation target. Internationalized domains and uncommon schemes may also fail the browser URL parser even when another tool accepts them.

Frequently asked questions