Pages

Topics

Tools

↑↓navigate↵openescclose
Encoding & Security

URL Parser & Encoder

Parse a URL into protocol, origin, port, path segments, query parameters and basic-auth parts, strip utm_* and click ids in one press, percent-encode or decode a single value or a whole column of them, and copy a fetch() or cURL request for the result.

Runs entirely in your browser — nothing you paste is uploaded.

URL reserved characters

quick reference
%20
Encoded space. In a query string a plain + is also read as a space by most form parsers.
%2F %3F %23
Encoded slash, question mark, and hash, the three characters that would otherwise change the URL structure.
%26 %3D
Encoded ampersand and equals, needed inside a parameter value to avoid splitting the query.
encodeURIComponent
Escapes a single parameter value, including / ? # & = — the right choice for query values.
encodeURI
Keeps URL structure characters intact, so it is for a whole URL rather than one value.
new URL(input)
Built-in parser that exposes protocol, host, pathname, searchParams, and hash.

Frequently asked questions

answered below the tool
encodeURI or encodeURIComponent?

encodeURI keeps ? & / # and is for a whole URL; encodeURIComponent escapes them and is for one parameter value.

What do the utm_ parameters do?

They tag a campaign so analytics can attribute the visit; they never change the page. The cleaner removes them along with fbclid, gclid, mc_cid and the other click ids.

Why does my parameter arrive split?

A raw & or = inside a value ends the parameter early. Encode the value before building the link.

All Next.js guides