URL Parser
Inspect URL structure and raw query fields
The full guide also includes pitfalls, worked examples, snippets, FAQs, and related tools for checking results or troubleshooting.
About this tool
Inspect protocol, host, port, path, query, fragment, and credentials in your browser. Compare raw query fields with decoded values, keep repeated parameters in order, and remove known tracking fields without sorting or re-encoding the rest. Copy parsed URLs or query JSON/CSV, edit URL parts, and extract links from text. Parsed output is not a recommendation for your site’s canonical URL. Drafts are stored in this browser; Clear removes them.
Suggested Workflow
Slug and URL SEO Basics for Real Production Pages
Reproduce Unicode slug suggestions, preserve URL context, and check changes before migrating a published page.
URL Parameter Encoding Playbook for Tracking and Redirect Safety
Compare raw and decoded query fields using repeatable examples for Chinese text, plus signs, repeated keys, empty values, and signed links.
Production Snippets
Inspect an encoded callback value before changing it
text
https://app.example.com/callback?next=%2Forders%3Fstatus%3Dopen&state=a%2Bb
Raw next: %2Forders%3Fstatus%3Dopen
Decoded next: /orders?status=open
Raw state: a%2Bb
Decoded state: a+bScenario Recipes
Find which part of a callback URL differs
Goal: Compare an observed callback with the address registered in your application.
- Paste the complete callback URL and inspect Origin and Pathname separately.
- Use the raw and decoded query columns to check the next and state values without treating their encoded delimiters as new parameters.
- If you edit URL parts, apply the change and inspect the rebuilt URL before copying it.
Result: The component table isolates host, path and query differences. It does not contact the endpoint or check the application’s allowed callback list.
Frequently Asked Questions
Why are + and %2B decoded differently?
Query parameters use form-style decoding: + becomes a space, while %2B becomes a literal plus. %252F becomes %2F after one decoding pass, not /.
What happens to repeated keys and empty values?
All query rows remain in order, including repeated keys and empty values. JSON groups repeated values into arrays; CSV keeps the row order. The raw column distinguishes flag from flag=.
What does cleaning change?
It removes known tracking fields such as utm_* and gclid. Remaining query bytes and order, trailing slash, credentials, and fragment are preserved relative to the browser-parsed URL. Removing any field can still invalidate a signed link.
Does parsed output determine my SEO canonical?
No. The browser normalizes URL syntax, including internationalized hostnames, default ports, and some path syntax. Canonical selection depends on your site’s redirects, content, and routing rules.
Can I extract links from text?
Yes. Open Examples and extraction, paste text, and copy the deduplicated HTTP(S) or www links. This is a text extractor, not a full Markdown or HTML parser.
Are URLs uploaded or saved?
URL processing stays in your browser. The input is saved as a local draft and Clear removes it; avoid leaving credential-bearing drafts on shared devices. Website usage analytics is separate from the URL input.
Keep browsing