Encode values, not whole URLs
Encode each query value separately, then join them.
Encode text so it is safe to use in a URL, decode a %-encoded link back into readable text, or break a URL into its host, path and query parameters.
Private by design. Your code and data are processed in your browser. Nothing is uploaded, logged or stored, so it is safe for API responses, configs and other internal data.
URLs can only contain a limited set of characters. Spaces, ampersands, accented letters and many symbols must be percent-encoded, so a space becomes %20 and & becomes %26. Encoding a single value, such as a search term inside a query string, needs component encoding, which also escapes characters like ? and &.
Full URL encoding is for a complete address: it encodes spaces and non-ASCII characters but keeps the characters that give a URL its structure, such as :, /, ? and =. Form encoding is what HTML forms send, where spaces become plus signs.
Encode each query value separately, then join them.
Encoding twice turns %20 into %2520. Decode first if unsure.
Decode long tracking links to see what they contain.
It lists every query parameter, which is handy when debugging campaigns.
It is an encoded space. Each %XX is a byte written in hexadecimal.
%20 works everywhere. + means a space only in form-encoded query strings.
Yes. Characters are encoded as UTF-8, the web standard.
No. Everything runs in your browser.
Hire dedicated developers from iCreativez who work as part of your team.