What components does the URL parser extract?

It decomposes any URL into its standard WHATWG components: protocol (scheme), host/hostname, port, pathname, search string (query), hash (fragment), username, and password.

Can I add, edit, or delete query parameters interactively?

Yes. Every query key-value pair is displayed in an editable table. You can modify keys, update values, add new parameters, or remove existing ones, and the reconstructed URL updates automatically in real time.

Does it handle URL-encoded and Unicode characters?

Yes. Query keys and values are automatically decoded for easy human reading and editing, and re-encoded properly according to RFC 3986 when generating the final URL.

Can it parse relative URLs?

Standard URL specifications require an origin for relative paths. DevCodivo safely uses a placeholder base if a relative path is provided, allowing you to parse path segments and query strings without errors.

Is my URL transmitted over the network?

No. All URL parsing and reconstruction utilizes standard browser URL and URLSearchParams APIs locally. No API endpoints or external servers receive your URLs or sensitive query tokens.

URL-Parser

Zerlege URLs in Protokoll, Host, Pfad und bearbeite Query-Parameter interaktiv in Echtzeit.

Läuft in deinem Browser; deine Daten verlassen dein Gerät nieKostenlos, ohne Anmeldung

Full URL

Protocolhttps:

Hostnamedevcodivo.com

Port(default)

Pathname/tools/json-formatter

Query Parameters (3)

Anchor / Hash: #features

So funktioniert es

The DevCodivo URL Parser reads any uniform resource locator and deconstructs it according to RFC 3986 and WHATWG URL specifications into individual parts: protocol scheme, authority (credentials, hostname, port), path segments, query string, and fragment anchor.

The query parameters are split into an interactive key-value table. When you edit, add, or remove parameter rows, the parser reassembles the full URL dynamically with proper percent-encoding.

Funktionen

Complete URL component breakdown (protocol, origin, host, port, path, hash)
Interactive query parameter editor with live add, modify, and delete actions
Automatic URL-decoding for readability with clean re-encoding
One-click copy for the full URL or individual components
100% client-side: URLs with private tokens never leave your browser

So wird es verwendet

Paste your URL into the top input field or click a sample URL.
Review the decomposed breakdown cards showing protocol, host, port, and path.
Use the query parameters table to tweak values, add new parameters, or remove keys.
Copy the reassembled URL or any individual property with one click.

Beispiel

Input URL:
https://api.devcodivo.com:8443/v1/search?query=json&page=2#results

Deconstructed:
Protocol:  https:
Host:      api.devcodivo.com:8443
Hostname:  api.devcodivo.com
Port:      8443
Pathname:  /v1/search
Query:     query=json&page=2
Hash:      #results

Häufig gestellte Fragen

What components does the URL parser extract?: It decomposes any URL into its standard WHATWG components: protocol (scheme), host/hostname, port, pathname, search string (query), hash (fragment), username, and password.
Can I add, edit, or delete query parameters interactively?: Yes. Every query key-value pair is displayed in an editable table. You can modify keys, update values, add new parameters, or remove existing ones, and the reconstructed URL updates automatically in real time.
Does it handle URL-encoded and Unicode characters?: Yes. Query keys and values are automatically decoded for easy human reading and editing, and re-encoded properly according to RFC 3986 when generating the final URL.
Can it parse relative URLs?: Standard URL specifications require an origin for relative paths. DevCodivo safely uses a placeholder base if a relative path is provided, allowing you to parse path segments and query strings without errors.
Is my URL transmitted over the network?: No. All URL parsing and reconstruction utilizes standard browser URL and URLSearchParams APIs locally. No API endpoints or external servers receive your URLs or sensitive query tokens.