Codificador / Decodificador URL
Codifica y decodifica URLs
Siguientes pasos sugeridos
Herramientas Relacionadas
Codificador / Decodificador Base64
Codifica texto a Base64 o decodifica Base64 a texto rapidamente.
Codificador / Decodificador de Entidades HTML
Codificar caracteres especiales a entidades HTML o decodificarlos
Escapar / Desescapar cadenas
Escapar y desescapar cadenas para HTML, JSON, JavaScript, SQL y más
Convertidor de Base Numérica
Convertir números entre binario, octal, decimal y hexadecimal
Convertidor de Marca de Tiempo
Convertir entre marcas de tiempo Unix y fechas legibles
Búsqueda ASCII / Unicode
Buscar y consultar códigos de caracteres ASCII y Unicode
Cómo Usar
Pega o Escribe
Ingresa tu texto, código o datos en el área de entrada.
Elige las Opciones
Selecciona la transformación o formato que deseas aplicar.
Copia el Resultado
Copia la salida a tu portapapeles con un solo clic.
Por Qué Usar Esta Herramienta
100% Gratis
Sin costos ocultos, sin niveles premium — todas las funciones son gratuitas.
Sin Instalación
Se ejecuta completamente en tu navegador. No necesitas descargar ni instalar nada.
Privado y Seguro
Tus datos nunca salen de tu dispositivo. Nada se sube a ningún servidor.
Funciona en Móvil
Totalmente responsivo — úsalo en tu teléfono, tableta o escritorio.
URL Encoding: Percent-Encoding for Safe Web Addresses
Key Takeaways
- URL encoding (percent-encoding) replaces unsafe characters with %XX hex values to ensure URLs are transmitted correctly.
- Spaces, ampersands, question marks, and non-ASCII characters all require encoding when used in URL parameters.
- All encoding and decoding is performed in your browser — no data is sent to any server.
URLs can only contain a limited set of ASCII characters. When you need to include spaces, special characters, or Unicode text in query parameters or path segments, URL encoding (also called percent-encoding) converts them into a universally safe format. Proper URL encoding prevents broken links, security vulnerabilities, and data corruption in web applications.
Improper URL encoding is among the OWASP Top 10 causes of web application injection vulnerabilities.
Security Impact
Key Concepts
Reserved vs. Unreserved Characters
RFC 3986 defines unreserved characters (A-Z, a-z, 0-9, -, _, ., ~) that need no encoding. Reserved characters (: / ? # [ ] @ ! $ & ' ( ) * + , ; =) have special meaning in URLs and must be encoded when used as data.
encodeURI vs. encodeURIComponent
encodeURI() encodes a full URI but preserves reserved characters. encodeURIComponent() encodes everything except unreserved characters, making it correct for encoding individual query parameter values.
Unicode and UTF-8 Encoding
Non-ASCII characters (Chinese, Arabic, emoji) are first converted to UTF-8 bytes, then each byte is percent-encoded. The character '日' becomes %E6%97%A5.
Double Encoding Pitfalls
Double encoding occurs when already-encoded values are encoded again (% becomes %25). This creates broken URLs and is a common source of bugs in URL construction.
Pro Tips
Always use encodeURIComponent() for query parameter values, never encodeURI() — the latter will not encode & and = characters.
Decode URLs before displaying them to users for readability, but always keep them encoded in HTTP requests.
Be careful with the '+' character — in query strings it represents a space (application/x-www-form-urlencoded), but in path segments it is literal.
Test URL encoding with international characters (CJK, Arabic, emoji) to ensure your application handles multibyte UTF-8 correctly.
All URL encoding and decoding is performed entirely in your browser. Your URLs and query parameters are never sent to any external server.