🔧

Encodeur d'URL

Encodage & Chiffrement · Outil en ligne gratuit

Encoder en pourcentage et décoder les URL.

Équipe CoderNewbieDernière mise à jour : 2026-09-20

Entrée61 caractères

Sortie

0 caractères

Click "Encode" or "Decode" to transform your URL...

Encoder

Encode en percent-encoding les caractères spéciaux comme les espaces, esperluettes et paramètres de requête pour un transport URL sûr.

Décoder

Convertit les URL encodées en percent-encoding en texte lisible, avec un retour clair sur les séquences malformées.

Conforme RFC 3986

Utilise encodeURIComponent — la norme pour encoder les composants URL et valeurs de requête.

Comment utiliser Encodeur d'URL

1Enter or paste your data into the input field.
2Select the desired encoding, hashing, or encryption options.
3Click the action button to process your data.
4Copy the result from the output field.

Fonctionnalités

✓100% gratuit — sans inscription, sans abonnement, sans publicité
✓Fonctionne entièrement dans votre navigateur — vos données ne quittent jamais votre appareil
✓Rapide et léger — résultats instantanés
✓Multiplateforme — compatible ordinateur, tablette et mobile

Qu'est-ce que Encodeur d'URL ?

URL encoding (percent-encoding), defined by RFC 3986, converts characters that are not allowed in a URL into a % followed by two hexadecimal digits. Reserved characters (:, /, ?, #, [, ], @, !, $, &, ', (, ), *, +, ,, ;, =) and non-ASCII characters must be encoded when used outside their reserved purpose.

Comment fonctionne Encodeur d'URL ?

Each character is encoded as UTF-8 bytes, then each byte that is not an unreserved character (A-Z, a-z, 0-9, -, _, ., ~) is converted to %XX form. Spaces are encoded as %20 in paths or + in query strings (application/x-www-form-urlencoded).

Cas d'usage courants

✓Query parameters — pass special characters in URL search strings
✓OAuth callbacks — encode redirect URIs
✓REST API requests — encode path and query parameters
✓International domains — encode non-ASCII characters (IDN)

URL Encoding vs Base64

URL encoding preserves URL structure (only encoding unsafe characters) while Base64 encodes the entire input. URL encoding is reversible in-place; Base64 changes the format entirely. Use URL encoding for web addresses; use Base64 for embedding binary data in text.

Sécurité et confidentialité

This tool runs entirely in your browser. URL encoding does NOT provide security — it only ensures characters are transport-safe. Never use it to hide sensitive data. For secure transmission use HTTPS; for data protection use encryption.

Détails techniques

Standard: RFC 3986. Unreserved: A-Z a-z 0-9 - _ . ~. Reserved: : / ? # [ ] @ ! $ & ' ( ) * + , ; =. Percent-encoded: %XX (hex). Space: %20 (path) or + (query). Non-ASCII: UTF-8 bytes each encoded as %XX. JavaScript: encodeURIComponent() encodes all except A-Z a-z 0-9 - _ . ! ~ * ' ( ).

Questions fréquentes

What is the difference between encodeURI and encodeURIComponent?

encodeURI preserves reserved URL characters (: / ? #) for full URLs. encodeURIComponent encodes everything except A-Z a-z 0-9 - _ . ! ~ * ' ( ), for use on individual query parameters.

Why is space encoded as %20 or +?

%20 is the RFC 3986 standard for paths. + is the application/x-www-form-urlencoded convention for query strings in HTML forms. Both are valid but context-dependent.