Esta página ainda não foi traduzida para o português, por isso aparece em inglês.

URL Parser — Break a URL into Its Parts

Paste a URL to see every component and decoded query parameter — then edit, add or remove parameters and copy the rebuilt URL.

Atualizado em

Query parameters

Seus dados nunca saem do seu computador. Todo o processamento acontece localmente no navegador.

Como usar: URL Parser

  1. Paste a URL — the scheme is optional.
  2. Read the components: protocol, host, port, path, query and fragment.
  3. Edit, add or remove query parameters; the rebuilt URL updates instantly.
  4. Remove UTM and click-ID tracking with one click, then copy the clean URL.

Anatomy of a URL

https://user@shop.example.com:8443/en/products?sort=price&q=keyboard#reviews
└─┬─┘   └┬─┘ └──────┬───────┘ └┬─┘└─────┬────┘ └────────┬───────────┘ └──┬──┘
scheme  user      host       port    path            query           fragment
PartNotes
Schemehttps:, http:, ftp:, mailto:…
HostDomain or IP; internationalized domains are shown in Punycode (xn--…)
PortOmitted when it is the default (443 for HTTPS, 80 for HTTP)
PathCase-sensitive on most servers
Querykey=value pairs joined by &; keys can repeat
FragmentAfter #; never sent to the server

Encoding

Spaces and special characters in query values are percent-encoded (%20) or, in form encoding, written as +. The parameter table shows the decoded values; the rebuilt URL re-encodes them correctly, so you can edit values in plain text. For encoding single strings, use the URL encoder.

Cleaning tracking parameters

Marketing links often carry utm_*, gclid, fbclid or mc_eid parameters. They do not change the page content, so remove them before sharing links or using them as canonical URLs. To create tracked links on purpose, use the UTM builder.

Credentials in URLs (user:password@host) are deprecated and visible in logs and browser history — avoid them.

Também pesquisado como: parse url online, query string parser, url decoder, url components, remove utm parameters, query string builder.

Ferramentas que combinam com: URL Parser

  • Redirect Checker — Follow a URL hop by hop to see every redirect, its status code and timing, and check that the http, https, www and non-www versions of your domain all end at one canonical address.
  • HTTP Header Checker — Fetch any URL and see exactly what the server sends back — status code, redirect chain and every response header, with a plain-English explanation of the ones that matter for SEO, caching and security.
  • Slug Generator — Convert any title into a clean, lowercase URL slug — with proper transliteration of accents, umlauts and Cyrillic, optional stop-word removal and a bulk mode for whole lists.
  • Email Header Analyzer — Paste the raw headers of an email to see its whole journey: every server hop with the time it took, the SPF, DKIM and DMARC results, the originating IP, and warning signs like a mismatched Reply-To or Return-Path.

Perguntas frequentes

Is the fragment (#) sent to the server?
No. Browsers keep everything after # on the client; servers never see it.
Can a query parameter appear twice?
Yes, for example ?tag=a&tag=b. Each occurrence appears as its own row and is kept when rebuilding.
Is my URL sent anywhere?
No. Parsing uses the browser’s built-in URL API.
Posso instalar o URL Parser como um aplicativo da web e usá-lo offline?
Sim. O URL Parser é um aplicativo da web instalável (PWA) — instalado a partir do seu navegador, não baixado de uma loja de aplicativos. Clique em “Instalar aplicativo” na parte superior desta página no Chrome ou no Edge (Windows, macOS, Linux, ChromeOS) ou, no Android, use “Compartilhar” → “Adicionar à tela inicial” no iPhone e no iPad, ou “Arquivo” → “Adicionar ao Dock” no Safari 17+ em um Mac. Em seguida, ela se abre em uma janela própria com seu próprio ícone e, como é executada inteiramente no seu navegador, continua funcionando offline. O Firefox no desktop não permite a instalação de aplicativos da web. Como funciona a instalação.

Ferramentas relacionadas