Does it support relative URLs?

It expects absolute URLs with a protocol for best results. For relative URLs like /path?param, prepend a base such as https://example.com to make parsing meaningful.

Does it decode percent-encoded values?

Yes. Query parameter values are shown in their decoded form alongside the raw encoded form, so you can verify the original input and spot double-encoded strings.

What if the URL includes a hash fragment?

The hash fragment is extracted and displayed as a separate parsed field, alongside the path and query string. Note that hash fragments are never sent to the server.

Is my URL data sent to your server?

No. URL Parser runs entirely in your browser. Tokens, session IDs, or any sensitive parameters never leave your device — no log, no upload, no analytics on the URL contents.

Can the parser handle URLs with international characters?

Yes. Both UTF-8 paths and Punycode (xn--) hostnames are parsed correctly. The decoded human-readable form is shown alongside the raw encoded form.

What is the difference between a path parameter and a query parameter?

Path parameters are named segments inside the URL path (for example /user/:id/posts/:postId resolving to /user/123/posts/45) — they're a convention of your routing framework, not a part of the URL standard. Query parameters come after the question mark (?sort=date). URL Parser surfaces the full path string and the query parameters; named path segments are application-defined, so we don't try to guess your routes.

How does the parser detect double-encoded URLs?

When a percent-encoded sequence appears inside an already-decoded value (for example %2520 instead of %20, or %253F instead of %3F), the parser raises a warning. Double-encoding usually means a URL was encoded twice somewhere upstream — a real production bug. Most other online parsers decode once and hide the problem; we flag it explicitly so you can trace the source.

Which tracking parameters does the parser label automatically?

All five UTM parameters (utm_source, utm_medium, utm_campaign, utm_term, utm_content) plus Google's gclid and gclsrc, Facebook's fbclid, Microsoft's msclkid, TikTok's ttclid, and a few platform-specific IDs. Each labeled parameter shows a short tag next to the value so you can scan a long URL and spot which platform owns each piece.

What does the JSON output include?

A structured object with href, protocol, host, hostname, port, pathname, search, hash, origin, a params array (each entry has key, value, decoded label, and a tracking flag), and a warnings array for issues like double-encoding. Copy it directly into a bug report, a script, or a test fixture.

How do I get just the domain without the protocol or path?

After parsing, copy the hostname field directly. To include the port, copy the host field instead. The protocol is always shown separately so you can recombine as needed.

Why does my URL fail to parse?

Most parse failures come from a missing protocol (no http:// or https://) or invalid characters in the hostname. The parser tries to auto-prepend https:// when no scheme is present; if it still fails, the hostname likely contains spaces or characters not allowed by the URL standard.

Web & SEO所属： Web & SEOツール →

URLパーサー

URLをプロトコル・ホスト・パス・クエリ部分に分解します。

データは端末内に残りますアップロードなし、サーバーなしオフラインで動作

URL

Normalized URL

Protocol

https

Host

toolgrid.app

Path

/tools/json-formatter

Origin

https://toolgrid.app

Hash

faq

Query params

Query entries

lang = zh-CN
view = compact
utm_source = google [Source]
utm_medium = cpc [Medium]

JSON output

{
  "href": "https://toolgrid.app/tools/json-formatter?lang=zh-CN&view=compact&utm_source=google&utm_medium=cpc#faq",
  "protocol": "https:",
  "host": "toolgrid.app",
  "hostname": "toolgrid.app",
  "port": "",
  "pathname": "/tools/json-formatter",
  "search": "?lang=zh-CN&view=compact&utm_source=google&utm_medium=cpc",
  "hash": "#faq",
  "origin": "https://toolgrid.app",
  "params": [
    {
      "key": "lang",
      "value": "zh-CN",
      "label": null,
      "tracking": false
    },
    {
      "key": "view",
      "value": "compact",
      "label": null,
      "tracking": false
    },
    {
      "key": "utm_source",
      "value": "google",
      "label": "Source",
      "tracking": true
    },
    {
      "key": "utm_medium",
      "value": "cpc",
      "label": "Medium",
      "tracking": true
    }
  ],
  "warnings": []
}

このツールを使う理由

解析されたコンポーネントとクエリサマリーでURL構造を素早く確認します。

URLパーサーはリンクとリクエストターゲットのデバッグに役立ちます。

URLの主要な部分とクエリエントリを抽出して表示します。

使い方

01URLを入力欄に貼り付けます。

02解析されたフィールドとクエリの内訳を確認します。

コピー前のクイックチェック

Confirm the input is the format you intended.

Scan the result before using it in a document, URL, config, or message.

Copy only the output you need.

よくある質問

相対URLに対応していますか？

最適な結果を得るには、プロトコルを含む絶対URLを使用してください。

パーセントエンコードされた値はデコードされますか？

はい。クエリパラメーターの値はデコードされた形式と生のエンコード形式の両方で表示されます。

URLにハッシュフラグメントが含まれる場合はどうなりますか？

ハッシュフラグメントは抽出され、別のフィールドとして表示されます。

URLパーサー

このツールを使う理由

使い方

コピー前のクイックチェック

よくある質問

関連ツール

クエリストリングビルダー

URL エンコーダー / デコーダー

URLパラメーター抽出ツール

URLパーサー

クエリストリングビルダー→

URL エンコーダー / デコーダー→

URLパラメーター抽出ツール→

クエリストリングビルダー

URL エンコーダー / デコーダー

URLパラメーター抽出ツール