使用繁體中文瀏覽?切換到繁體中文
使用简体中文浏览?切换到简体中文
日本語で表示しますか?日本語に切り替える
한국어로 보시겠어요?한국어로 전환
ดูหน้านี้เป็นภาษาไทยไหม?เปลี่ยนเป็นภาษาไทย
Lihat halaman ini dalam bahasa Indonesia?Beralih ke bahasa Indonesia
Xem trang này bằng tiếng Việt?Chuyển sang tiếng Việt
यह पेज हिन्दी में देखें?हिन्दी में बदलें
Voir cette page en français ?Passer au français
Diese Seite auf Deutsch ansehen?Zu Deutsch wechseln
¿Ver esta página en español?Cambiar a español
Visualizzare questa pagina in italiano?Passa all'italiano
Deze pagina in het Nederlands bekijken?Overschakelen naar Nederlands
Wyświetlić tę stronę po polsku?Przełącz na polski
Ver esta página em português?Mudar para português
Открыть страницу на русском?Переключить на русский
Bu sayfayı Türkçe görüntülemek ister misiniz?Türkçeye geç
عرض هذه الصفحة بالعربية؟التبديل إلى العربية
Skip to content

URL Encode/Decode

URL Encode/Decode converts URL components and values locally with percent encoding using encodeURIComponent/decodeURIComponent semantics for spaces, reserved characters, UTF-8 text, emoji, query values, and path segment data.

Input Text

URL Encode/Decode

Quick Start

1
Paste text or an encoded value.
2
Choose Encode or Decode.
3
Result replaces the same text box.
4
Copy the current text.

Common Scenarios

API parameters

encode parameter values before placing them in a query string; keep ?, &, and = outside the encoded value

Form data

useful for individual values, but this is not an application/x-www-form-urlencoded serializer and does not turn spaces into +

Shared links

encode non-ASCII or reserved data inside a parameter, path segment, or fragment before assembling the URL

Search queries

encode keywords or filters, especially when they include & = #? / or spaces

Usage Advice

Avoid double encoding: check whether content already contains %XX sequences
Partial encoding: encode only parameter values or path segment data (e.g., ?key=encoded), and keep the URL structure outside the encoded text
Debugging: decode copied request values to inspect them; replace + with %20 first if the source is form-urlencoded and you want spaces
Reserved characters: : /? # [ ] @! $ & ' ( ) * +,; = have special meaning; when used as data they generally need encoding (context-dependent, especially : /? # & = +)
Character encoding: non-ASCII characters are encoded in UTF‑8 as 1–4 bytes, each byte written as %HH

Encoding Boundaries

Component/value semantics: Encode uses encodeURIComponent, so /? & = #: are encoded when they are part of data
Whole URLs: do not paste a complete URL if you need to preserve scheme, host, path, query, or fragment structure; inspect complete URLs with URL Parser instead
Form encoding: this tool does not build application/x-www-form-urlencoded bodies, parse key/value pairs, or use + for spaces
Decode errors: a lone %, incomplete %HH, or invalid UTF-8 percent sequence shows an invalid URL encoding message

Limitations & Compatibility

URL encoding ≠ encryption: a reversible format transform that does not protect sensitive data
URL length: recommended total length < 2048 characters (varies by browser/server)
Space differences: spaces encode as %20 here. decodeURIComponent leaves + as +, so replace + with %20 first when decoding form-urlencoded data as spaces

Privacy & Security

Encoding and decoding run in your browser. The current text stays as a browser-session draft by default; after encoding or decoding, the transformed text replaces it. On a shared device, clear the text and site data when needed.
Sensitive data (passwords, keys, tokens) should be encrypted, not encoded

FAQ

8

Continue with these related tools for the next step.

Community

© CrateX.app · All Rights Reserved