Encoding

URL Parser & Inspector

Break a URL into protocol, host, port, path, query string, and fragment, and decode its parameters.

Relative paths such as docs/guide#section are parsed when a base URL is provided; without one they are labelled relative.

URL components

Enter a URL to inspect.

Your data stays private

This tool runs directly in your browser. The content you enter is processed locally and is not sent to TechFixGen servers. No account or signup is required.

URLs, explained

What is a URL?

A URL (Uniform Resource Locator) is an exact address for a resource on the web. A typical URL has a scheme (how to reach it), a host (where it lives), an optional path (which resource), a query string (parameters), and an optional fragment (which part of the page).

Breaking a URL into these parts makes redirects, APIs, and broken links much easier to reason about. This tool splits a URL into its components using your browser's own parser, so the results match exactly what the browser would do.

The parts of a URL

  • Protocol — https:, http:, ftp:.
  • Hostname — the domain or IP, such as techfixgen.com.
  • Port — optional; 443 for HTTPS, 80 for HTTP.
  • Path — the resource, such as /tools/url-parser.
  • Query string — starts with ? and holds key/value pairs.
  • Fragment — starts with # and points to a section. Fragments are never sent to the server.

Userinfo (username and password)

URLs can embed credentials before the host, like https://user:secret@example.com/. Keep these rare — they get logged in proxies and leak in bookmarks and referrers. This tool masks the password by default and only reveals it when you ask.

Query parameters

The query string carries data as key=value pairs separated by &. This parser shows each pair in both its raw encoded form and its decoded form, keeps duplicate keys intact (for example tag=a&tag=b), and preserves flag-style parameters with no value. Copy the decoded parameters as JSON to inspect or script with them.

Percent decoding vs plus signs

Decoding replaces %20 with a space. In HTML form payloads a space is sometimes encoded as +, but + is not part of standard percent encoding — this tool leaves it as a literal plus and never substitutes spaces. Values with malformed escapes, such as a lone %, are kept raw and flagged rather than guessed at.

Relative URLs

A relative path such as docs/guide#section has no scheme or host. Provide an absolute base URL and this tool resolves the combination exactly as the browser would (but without fetching anything over the network), or leave the base empty to review the relative parts on their own.

Privacy

Parsing happens locally in your browser — the URL is never fetched, resolved on a network, or sent anywhere. Pasted input is not uploaded to TechFixGen servers and is not included in analytics events. Building or debugging URLs in code? See the URL Encoder & Decoder for escaped values.

Frequently asked questions

What exactly does a URL parser do?

It splits a URL into its parts — protocol, hostname, port, path, query string, and fragment — and lists each query parameter in both raw encoded and decoded form. This tool uses the browser's native URL parser, so the breakdown matches what the browser would actually do.

Why do I see %20 in URLs?

%20 is a percent-encoded space. A raw space is not valid in a URL, so it is represented by %20 which decodes back to a space. Other characters such as é or emoji appear as multi-byte escapes like %C3%A9.

Why isn't plus decoded as a space?

A plus sign in the query string is only a space in HTML form-encoding conventions, not in standard percent encoding. This tool decodes percent escapes only, so a literal + stays a +. That keeps the output honest about what the URL really contains.

Can URLs contain passwords?

Yes, the userinfo segment can embed a password before the host, e.g. https://user:secret@example.com/. This tool masks it by default and shows it only when you click the reveal toggle.

Can this resolver fetch or validate a domain?

No. Parsing is purely syntactic and happens in your browser. This tool never makes a request, pings a server, checks DNS, or confirms whether a domain exists — it only describes the structure of the URL you pasted.

Is my URL sent to a server?

No. The URL is processed locally in your browser and is not uploaded to TechFixGen servers or included in analytics events.