Codificador / Decodificador de URL
Codifique e decodifique URLs
Proximos passos sugeridos
Ferramentas Relacionadas
Codificador / Decodificador Base64
Codifique texto para Base64 ou decodifique Base64 de volta para texto rapidamente.
Codificador / Decodificador de Entidades HTML
Codifique caracteres especiais em entidades HTML ou decodifique-os de volta
Escape / Unescape de String
Escapar e desescapar strings para HTML, JSON, JavaScript, SQL e mais
Conversor de Base Numérica
Converter números entre binário, octal, decimal e hexadecimal
Conversor de Timestamp
Converter entre timestamps Unix e datas legíveis
Consulta ASCII / Unicode
Pesquisar e consultar códigos de caracteres ASCII e Unicode
Como Usar
Cole ou Digite
Insira seu texto, código ou dados na área de entrada.
Escolha as Opções
Selecione a transformação ou formato que deseja aplicar.
Copie o Resultado
Copie a saída para sua área de transferência com um clique.
Por Que Usar Esta Ferramenta
100% Gratuito
Sem custos ocultos, sem planos premium — todos os recursos são gratuitos.
Sem Instalação
Funciona inteiramente no seu navegador. Nenhum software para baixar ou instalar.
Privado e Seguro
Seus dados nunca saem do seu dispositivo. Nada é enviado a nenhum servidor.
Funciona no Celular
Totalmente responsivo — use no seu celular, tablet ou desktop.
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.