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.

웹 & SEO소속: 웹 & 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 매개변수 추출기