Skip to content
Orbilyra
EncodingAvailableFreeRuns locally

URL Parser & Query String Inspector

Parse URL components and inspect decoded query parameters locally in your browser.

Inspect a URL or query string

Parse URL components and decoded query parameters locally in your browser.

0 characters

URLs and query strings are parsed locally in your browser and are not sent to a server.

Overview

What is a URL parser?

A URL parser turns a serialized URL into named components that are easier to inspect. Orbilyra uses the browser's WHATWG URL implementation for full URLs andURLSearchParams for query data, so the output follows browser behavior rather than a handwritten approximation.

Use the full URL mode for an absolute URL with a scheme. Use query string mode when you only have the portion after ? and want to inspect decoded name-value pairs.

Workflow

How to parse a URL

  1. Keep Full URL selected and paste an absolute URL.
  2. Select Parse URL or press Ctrl/Command + Enter.
  3. Review the normalized value, individual components, parsing notes, and query table.
  4. Copy either the redacted normalized value or a structured JSON report.

Anatomy

URL components explained

ComponentExampleMeaning
SchemehttpsIdentifies the protocol or URL scheme.
Hostapi.demo.invalid:8443Hostname plus an explicit non-default port.
Pathname/v1/usersLocates a resource within the origin.
Query?status=activeCarries application-defined parameters.
Fragment#resultsIdentifies a secondary resource or document location.

Parameters

How query string parsing works

Query mode accepts a leading ? but does not require one. Names and values are parsed using the application/x-www-form-urlencoded algorithm behindURLSearchParams. Percent-encoded UTF-8 is decoded, and plus signs represent spaces. Use %2B for a literal plus sign.

Repeated names are not collapsed. For example, tag=api&tag=debug produces two rows in the same order. An absent equals sign and an explicitly empty value both become an empty string under these browser semantics.

Example

URL parser example

Input

https://api.demo.invalid:8443/v1/users/%E9%9B%AA?tag=api&tag=debug#results

Selected output

Scheme: https
Hostname: api.demo.invalid
Port: 8443
Decoded pathname: /v1/users/雪
Parameters: tag=api, tag=debug

Related tasks

URL parsing vs URL encoding

Parsing separates an existing URL into components. Encoding prepares text for a particular component. The parser does not automatically repair or encode your input, and parsing does not prove that a URL is trustworthy.

To percent-encode a component value, use theURL Encoder / Decoder.

Safety

URL security and privacy notes

  • All parsing happens in the current browser tab; the entered value is not uploaded.
  • Password text embedded in URL user information is redacted from displayed and copied results.
  • Potentially executable schemes are shown only as inert text and receive a warning.
  • Parsing does not follow redirects, resolve DNS, fetch the host, or verify ownership.
  • Inputs are limited to 100,000 characters and 2,000 parameters to protect the interface.

Technical scope

Browser URL parsing semantics

The implementation follows the browser's WHATWG URL API. It requires an absolute URL in full URL mode and intentionally does not invent a base URL for relative input. Default ports may be omitted by URL serialization, internationalized hostnames may appear in ASCII form, and forgiving query decoding can preserve malformed percent text or produce replacement characters.

Technical references: WHATWG URL Standardand MDN URLSearchParams.

Keep exploring

Encoding

URL Encoder / Decoder

Encode URL components with percent encoding or decode encoded text directly in your browser.

View tool
Encoding

Base64 Encoder / Decoder

Encode UTF-8 text to Base64 or decode Base64 back to readable text directly in your browser.

View tool
Development

Regex Tester

Test JavaScript regular expressions, inspect matches, and review capture groups directly in your browser.

View tool
JSON & Data

JSON Formatter

Format, beautify, validate and minify JSON directly in your browser.

View tool

Learn more

Published guide

URL Encoding Explained

Learn how percent encoding works, when to use encodeURI or encodeURIComponent, and how to handle query parameters safely.

Read guide Published guide

encodeURI vs encodeURIComponent

Learn when to use encodeURI or encodeURIComponent, how reserved characters behave, and how to avoid double-encoding URLs and query values.

Read guide

FAQ

Frequently asked questions

What does a URL parser show?

A URL parser separates an absolute URL into its scheme, origin, host, hostname, port, path, query string, fragment, and decoded query parameters.

Can this tool parse a query string without a full URL?

Yes. Choose Query string mode and enter a value such as ?status=active&tag=api. A leading question mark is optional.

How are repeated query parameters handled?

Repeated names are preserved as separate entries in their original order, which is useful for patterns such as tag=api&tag=debug.

Why does a plus sign become a space?

URLSearchParams parses query strings using application/x-www-form-urlencoded rules, where a plus sign represents a space. Use %2B when the value must contain a literal plus sign.

Does URL parsing decode the path?

The tool shows both the serialized pathname and a best-effort decoded pathname. Query names and values are decoded separately through URLSearchParams.

Does parsing a URL make it safe to open?

No. Parsing reveals structure but does not establish trust or safety. Treat unfamiliar hosts, credentials, redirects, and executable schemes cautiously.

Are passwords in URLs displayed or copied?

No. If URL user information contains a password, the result and copied JSON report replace it with a redacted marker.

Is my URL sent to a server?

No. Parsing uses the browser URL and URLSearchParams APIs locally, and Orbilyra does not send the entered URL or query string to a server.