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
Characters
0 / 50,000
Quick Start
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
Encoding Boundaries
Limitations & Compatibility
Privacy & Security
FAQ
URL (Uniform Resource Locator) is the address text used on the Web, with structure such as scheme, host, path, query, and fragment. Encoding is needed when data characters could be mistaken for delimiters such as ?, &, #, =, or /, or when the data contains spaces, non-ASCII text, or emoji. Those characters are written as %HH UTF-8 bytes, for example space → %20 and / inside a parameter value → %2F. This tool is best for URL components and values, not for preserving the structure of a complete URL. URL encoding is reversible formatting and does not provide confidentiality.
No. Encoding is a reversible format conversion. Passwords, API keys and other secrets must be encrypted
You can, but Encode will treat the whole string as data and encode structure characters such as: /? & = #. If you need to keep the URL structure, encode only the parameter value or path segment data, or use URL Parser to inspect the URL first
General URL percent encoding uses %20. application/x-www-form-urlencoded form data uses + for spaces, but decodeURIComponent leaves + unchanged. This page transforms one text value, not a complete form body, so replace + with %20 first when you want form-style spaces decoded.
Encoded content contains %XX sequences (% followed by two hex digits, e.g., %E4%BD%A0). If you see many such sequences, it is already encoded; avoid encoding again
Non-ASCII text such as Chinese, accents, and emoji is encoded as UTF-8 %HH bytes. Slashes depend on position: keep / as a path separator, but encode it as %2F when it is data inside a query value or path segment.