Helpful information

Break a URL into its protocol, host, path, query, and hash, then inspect query parameters as a table or JSON. Quickly identify UTM campaign parameters and duplicate keys.

Input never leaves your device. Processing uses your local computer only.

URL encoding, decoding, parsing, and cleaned URL generation all happen in your current browser.

Q. When should I encode or decode a URL?

Use encode to safely include spaces, special characters, or non-ASCII text in a URL. Use decode to turn values such as %E2%9C%93 back into readable text.

Q. What are UTM parameters?

Marketing tracking parameters such as utm_source, utm_medium, and utm_campaign.

Q. Are relative URLs supported?

Relative URLs such as /path?a=1 are analyzed using a temporary base URL.

Q. How are duplicate parameters displayed?

When the same key appears more than once, it is counted as a duplicate and each value appears in a separate table row.

Marketing: Check UTM values before distributing campaign links.

Development: Quickly troubleshoot API callback URLs, redirect_uri values, and query encoding issues.

Copy: Copy the parameter JSON and format it with the JSON/XML Formatter.

Check patterns: Use the Regex Tester to find specific patterns in a list of URLs.

No. Encode behaves like JavaScript's encodeURIComponent, so it percent-encodes URL structure characters such as : / ? & = #. It is best for individual components such as query parameter values or path segments. To preserve the overall URL structure, parse the URL and use Rebuild URL.

It splits the URL into protocol, host, pathname, search, hash and origin, and shows query parameters as a table and JSON. Repeated keys appear as separate rows and are counted as duplicates, UTM parameters are counted, and Rebuild URL can sort parameters, remove empty values, and keep or drop UTM parameters.

URL Encoder / Decoder & Parser - Percent Encoding

Convert

Cleanup options

Query Parameters

Output

URL components

Helpful information

What does the URL parser show?

Where is the input URL processed?

Frequently asked questions (FAQ)

Tips

Does the Encode button preserve a full URL while encoding it?

How does the URL parser analyze Query Strings and UTM parameters?