Should I use encodeURI or encodeURIComponent?
Use encodeURIComponent for individual query values, path segments, and redirect_uri values. Use encodeURI only for a full URL when you want to keep separators such as : / ? & = readable.
Codifica y decodifica URLs, componentes URI, valores de formulario y query strings en el navegador.
Use URI component for query values and path segments; use Full URL when you want to keep : / ? & intact.
Enter a value to see the result.
Qué aprenderás en este curso y cómo están organizadas las lecciones.
Guías relacionadas para este flujo: Herramientas locales del navegador para depurar APIs
DevCove URL Encoder / Decoder helps developers safely prepare URLs, query parameters, redirect targets, and form values. It supports encodeURIComponent, encodeURI, application/x-www-form-urlencoded plus-sign handling, query string parsing and building, and batch line-by-line conversion. Everything runs locally in your browser.
Use this tool when you need to safely place text inside a URL, decode copied URLs, or inspect query parameters.
Designed for everyday API debugging, redirect URLs, OAuth callbacks, form payloads, and query string work:
Use encodeURIComponent for individual query values, path segments, and redirect_uri values. Use encodeURI only for a full URL when you want to keep separators such as : / ? & = readable.
In application/x-www-form-urlencoded form data, spaces are commonly represented as +. General URI percent encoding uses %20. This tool has a separate Form value mode so the behavior is explicit.
Yes. Query string mode accepts either a full URL or a raw ?key=value string, extracts the query portion, decodes keys and values, and preserves repeated parameters as separate rows.
The decoder reports malformed input when it sees incomplete or invalid percent-encoded bytes. That makes broken copied URLs easier to spot before you put them into code or documentation.
No. Encoding, decoding, parsing, and query building run in your browser. DevCove does not upload or store your input.