URL Encoder/Decoder

Encode text for URLs or decode URL-encoded strings

URL Encoder/Decoder

Encode text for URLs or decode URL-encoded strings

Preserves: A-Z a-z 0-9 ; , / ? : @ & = + $ - _ . ! ~ * ' ( ) #
Characters: 0 • Spaces: 0
URL Encoding Reference
Common Encodings:
  • Space → %20
  • ! → %21
  • @ → %40
  • # → %23
  • $ → %24
Special Characters:
  • & → %26
  • = → %3D
  • ? → %3F
  • / → %2F
  • + → %2B

URL Encoder/Decoder – Complete URL Encoding Tool

Our URL Encoder/Decoder is an essential tool for web developers, API designers, and anyone working with URLs and web addresses. Convert between readable text and URL-encoded format with support for both standard and full encoding modes.

Frequently Asked Questions (FAQs)

URL encoding, also known as percent-encoding, is a mechanism for encoding information in a Uniform Resource Identifier (URI). It replaces unsafe ASCII characters with a '%' followed by two hexadecimal digits representing the character's ASCII code.

Use URL encoding when: 1) Including special characters in URLs, 2) Sending form data via GET method, 3) Passing parameters in query strings, 4) Including non-ASCII characters in URLs, 5) Creating URLs programmatically that might contain reserved characters.

encodeURI encodes a complete URI but leaves functional characters like :, /, ?, &, =, etc. intact. encodeURIComponent encodes everything except alphanumerics and - _ . ! ~ * ' ( ). Use encodeURIComponent for URL parameters and encodeURI for complete URLs.

Characters that need encoding include: 1) Control characters (ASCII 0-31, 127), 2) Reserved characters: ; / ? : @ & = + $ , #, 3) Unsafe characters: space, <, >, ", %, {, }, |, \, ^, ~, [, ], `, 4) Non-ASCII characters (Unicode).

URL decoding is the reverse process: it converts percent-encoded characters (% followed by two hex digits) back to their original characters. For example, %20 becomes a space, %40 becomes @, and %E4%BD%A0 becomes the Chinese character '你'.

Spaces can be encoded as either %20 or +. Modern browsers and servers understand both. Our encoder uses %20 for consistency. When decoding, both %20 and + are converted to spaces.

Yes, but be careful. encodeURI is designed for complete URLs and preserves characters needed for URL structure. encodeURIComponent is for URL components/parameters. Our tool offers both options.

Yes, our encoder/decoder fully supports Unicode characters. Non-ASCII characters are encoded as UTF-8 byte sequences, then percent-encoded. For example, 'é' becomes %C3%A9 (UTF-8 bytes C3 A9).

URL-safe Base64 is different from URL encoding. It's a Base64 variant that uses - and _ instead of + and / to make Base64 strings safe for URLs without additional encoding. Our Base64 tools handle this separately.

Always validate and sanitize URLs before decoding to prevent injection attacks. Be cautious when constructing URLs from user input. Use proper validation and consider using allowlists for safe characters.