Encode, clean and rebuild URLs without guessing what changed.

Work with full URLs, path segments, query strings and user-entered values. Parse components, remove tracking noise, detect risky parameters and export code snippets for APIs.

URL parser Query editor Tracking cleanup Double-encode detection
Kusimba URL kwa Kiswahili. Safisha na andaa URLs kwa APIs, redirects, tracking cleanup na snippets za requests. Hakiki kabla ya kutumia kwenye production redirects. Kwa security, API, hosting, SEO, PWA, USSD au domain decisions, hakiki source output, provider docs na production environment kabla ya launch.

URL Input

Absolute URLs are parsed directly. Relative paths use the base URL below.

Encode and Decode Lab

Compare full URL, component and stricter RFC 3986 component behavior.
encodeURI
encodeURIComponent
RFC 3986 component
decodeURIComponent

Components and Query Surgery

Edit path and query safely, including duplicate query keys.
KeyValue

Outputs

Rebuilt URL, cleaned URL, query string, and code handoff.
Rebuilt URL
Clean URL
Query String

            
When should I use encodeURIComponent instead of encodeURI?

Use encodeURIComponent for user-entered values that will become one path segment, one query key or one query value. Use encodeURI only when you already have a complete URL and want to preserve URL delimiters like colon, slash, question mark and ampersand.

Why does this tool warn about double encoding?

Double encoding often appears as `%2520`, which means an already encoded `%20` was encoded again. That can break redirects, signed URLs, callback URLs and search filters.

Does removing tracking parameters change the destination?

Usually it keeps the destination while removing analytics parameters such as `utm_source`, `fbclid`, `gclid` or `msclkid`. Some sites misuse tracking parameters for routing, so test important campaign URLs before publishing.