URL Encoder

URL Encoder applies percent-encoding to special characters—spaces, ampersands, unicode—in strings you embed in query parameters, redirect URLs, or API requests.

It prevents broken links when passing user-generated search terms or pre-filled form values into URLs.

OAuth redirect_uri parameters fail registration when parentheses or spaces are not encoded—encode before pasting into provider consoles.

Marketing builds campaign links with UTM values containing spaces and emojis—encoding avoids 400 errors at the edge.

• Encode search query params for share links
• Fix broken mailto bodies with special characters
• Prepare redirect URLs for SAML configs
• Encode file names in download query strings
• Debug API clients sending encoded vs double-encoded values

1. 1Paste plain text or partial URL component to encode.
2. 2Choose component (encodeURIComponent) vs full URL encoding if options exist.
3. 3Copy encoded output into your link builder or code.
4. 4Decode with URL Decoder to verify round trip when debugging.
5. 5Avoid double-encoding already encoded strings.

• encodeURIComponent is usually correct for query values; encodeURI preserves reserved URL structure characters.
• Pair with UTM Builder when campaign strings need encoding before paste.
• JSON in query params should be URL-encoded after stringifying.
• Base64 is not URL encoding—use Base64 Encoder for different purpose.

• Double-encoding produces %2520 instead of space—decode first if unsure.
• Plus sign vs %20 for spaces varies by server parsing—test target platform.
• Common mistake — encoding entire URL including protocol: often only encode query values.