Encoder/décoder URL
Encodage pourcent
À propos de cet outil
URL-encode or URL-decode strings - the percent-encoding (%20, %3F, etc.) used in URLs, query strings and HTTP form data. Also parses a full URL into its components (protocol, host, port, path, query, hash) so you can inspect each part separately.
Useful for debugging APIs, building URLs by hand, decoding suspicious links, and pretty-printing query strings. Runs entirely in your browser.
Fonctionnalités
- Encode and decode percent-escapes
- Parse a full URL into protocol, host, port, path, query, hash
- Pretty-print query parameters as key/value pairs
- Live two-way conversion
- Browser-only - data never uploaded
- Free and unlimited
- Handles percent-encoding of full URLs and individual query components separately
Comment l'utiliser
- Paste text or a full URL.
- Pick encode, decode or parse.
- Copy the result.
Tout se passe dans votre navigateur grâce à JavaScript et WebAssembly. Vos fichiers ne sont jamais téléversés, jamais stockés et jamais vus par nous.
Questions fréquentes
URL encoding escapes characters that aren't safe in URLs (?, &, /, spaces). Base64 turns binary bytes into text. They solve different problems.
Whenever you build a URL from user input or arbitrary text - values in query parameters or path segments need encoding so special characters don't break the URL structure.
encodeURI assumes you're encoding a complete URL and leaves URL-structural characters (/, ?, #) alone. encodeURIComponent escapes everything that isn't a letter or digit, suitable for query parameter values.
Yes - modern browsers support IRIs (international URIs) with non-ASCII characters. The encoded form is still ASCII percent-escapes.
In the query string of an HTTP URL, both encodings are accepted by most servers, but they mean slightly different things by convention: %20 in paths, + in form-encoded queries. The tool offers both modes so you can match whatever your downstream expects.
Click Decode twice to peel two layers of encoding. The tool doesn't auto-detect double encoding because that would change the meaning of legitimately single-encoded URLs.