Enter or Paste Text / URL
Type or paste your query parameter, path segment, or complete URI into the input editor.
Percent-encode and decode URL components, full URIs, and form query values with full RFC 3986 conformity and multi-byte Unicode support. Runs 100% inside your local browser memory.
0 characters
Follow these steps to safely escape query parameters, prevent delimiter collisions, and decode percent-encoded strings:
Type or paste your query parameter, path segment, or complete URI into the input editor.
Choose "Component mode" for query values, "Full URL mode" for complete addresses, or "Form value mode" for application/x-www-form-urlencoded syntax.
Run the conversion to generate RFC-compliant percent-encoded output or restore raw UTF-8 text.
Review the output length and verified encoding mode directly in the editor status bar.
Copy the output directly to your clipboard or clear both editors to begin your next task.
Formal specification rules governing reserved characters, percent-encoding, and form value serialization:
Escapes all reserved punctuation characters (; , / ? : @ & = + $ #). This mode is mandatory for individual query string parameter values to prevent delimiter injection.
Preserves structural protocol and path delimiters (http://, /, ?, #, &) while encoding unsafe characters like spaces and Unicode glyphs. Use when encoding full destination links.
Standardized form value encoding used by HTML forms and URLSearchParams. Spaces are encoded as "+" instead of "%20".
Detailed technical analysis of URI reserved character sets, form serialization, and UTF-8 multi-byte octets:
RFC 3986 divides the ASCII character space into unreserved characters (A-Z, a-z, 0-9, "-", "_", ".", "~"), which should never be encoded, and reserved characters (; , / ? : @ & = + $ #), which carry structural delimiter meaning.
Characters outside the ASCII range (such as emojis or international scripts) are first converted to their UTF-8 byte representation, and each byte is emitted as a three-character sequence "%XX".
In standard RFC 3986 URI paths, a space is encoded as "%20" and a plus sign "+" is a literal character. In query strings encoded as application/x-www-form-urlencoded, spaces are serialized as "+", which requires form mode decoding.
Diagnose and correct malformed URI errors, double-encoding bugs, and plus-sign confusion:
Root Cause: The string to be decoded contains a percentage sign "%" that is not followed by two hexadecimal digits, or contains split UTF-8 surrogate code units.
Solution: Ensure every percentage sign is followed by two valid hex digits (e.g. %20), or escape raw % characters as %25 before decoding.
Root Cause: A previously percent-encoded string was passed into an encoder again, causing % to be encoded into %25.
Solution: Decode the string once before re-encoding, or ensure your API client does not automatically re-encode already escaped query values.
Root Cause: The input was encoded using form mode (where + denotes a space), but was decoded using standard Component mode.
Solution: Switch the tool mode to "Form value mode" to properly decode + into whitespace.
Key constraints regarding URL length restrictions and international domain name handling:
Convert text payloads to URL-safe Base64 for query strings and JWT tokens.
Generate cryptographic hashes (SHA-256) of URL strings for cache keys and canonical identification.