TecnoCrypter Logo

URL Encoder

Encode/decode URLs and URIs

Codificar URL

Componente: Codifica todos los caracteres especiales incluyendo / : @ etc. Ideal para parámetros de query string.

URL completa: Preserva los caracteres válidos de una URL (/ : @ ? # etc). Ideal para URLs enteras.

URL Encoder: Safely Encode Query Parameters

URL encoding (percent-encoding) transforms special characters (spaces, ampersands, non-ASCII) into safe sequences for use in URLs. Essential when building GET queries with user data, forms, redirects, or shared links.

Our encoder supports the two standards: encodeURIComponent (for query strings, encodes / and ?) and encodeURI (for full URLs, preserves / and ?). Choose according to context: values → encodeURIComponent, entire URL → encodeURI.

Everything runs locally in your browser. Also decodes URL-encoded strings back to human-readable text.

How does it work?

  1. 1
    Select mode

    'Encode' to convert text to URL-safe format or 'Decode' to reverse.

  2. 2
    Choose encoding function

    encodeURIComponent (for query values) or encodeURI (for full URLs).

  3. 3
    Enter the text

    Paste the string to convert. The result appears in real time.

Frequently Asked Questions

What's the difference between encodeURI and encodeURIComponent?

encodeURI preserves reserved URL characters (:/?#[]@). encodeURIComponent encodes them too. Use encodeURIComponent when the string is a query parameter value; use encodeURI when it's a complete URL.

Why do spaces become %20 sometimes and + others?

%20 is standard URL encoding for spaces. In form data (application/x-www-form-urlencoded), spaces become +. Both are valid but in different contexts. Our tool uses %20 (standard).

Do I need to encode emoji or accented characters?

Yes. Any character outside ASCII (á, é, ñ, 😀, etc.) must be encoded. Modern browsers do it automatically in the address bar, but if you build URLs programmatically, you must encode.