Encode and decode query parameters, path segments, and full URLs with exact RFC 3986 compliance. Seamlessly transcode UTF-8 multi-byte glyphs, diagnose recursive double-encoding faults, and decompose nested payloads.
The input contains percent signs that were themselves transcoded as %25 (e.g. %2520 representing a space). Processing with normal decode will yield %20 rather than the underlying literal character.
| Key | Raw Encoded Value | Decoded Value | Actions |
|---|
Detailed breakdown of character sets, percent-encoding matrix differences, and the root causes of corrupted HTTP payloads.
RFC 3986 divides ASCII into unreserved characters (letters, digits, - . _ ~) which should never be encoded, and reserved delimiters (: / ? # [ ] @ ! $ & ' ( ) * + , ; =).
;,/?:@&=+$-_.!~*'()# intact.-_.!~*'().
A notorious source of bugs. RFC 3986 mandates spaces be encoded strictly as %20. However, HTML form submissions historically used the W3C application/x-www-form-urlencoded spec, where spaces serialize to +.
+ in paths is taken literally as a plus glyph, corrupting tokens or base64 keys without explicit form parsers.
When an application blindly runs encodeURIComponent() on a query parameter already encoded by an upstream proxy, %20 transforms into %2520.
/%25[0-9a-fA-F]{2}/ before serializing downstream.
| Character | Name / Symbol | Percent Encoded | encodeURI() | encodeURIComponent() | Form Data |
|---|---|---|---|---|---|
| (space) | ASCII 32 | %20 | %20 | %20 | + (or %20) |
| / | Forward slash | %2F | / (Preserved) | %2F | %2F |
| ? | Question mark | %3F | ? (Preserved) | %3F | %3F |
| & | Ampersand | %26 | & (Preserved) | %26 | %26 |
| # | Hash / Fragment | %23 | # (Preserved) | %23 | %23 |
| % | Percent Literal | %25 | %25 | %25 | %25 |
RFC 4648 Base64 & Base64URL converter with UTF-8 byte stream alignment.
Decode headers, timestamps, exp timers, and verify signatures with zero token leakage.
Side-by-side Myers diff algorithm comparison for payloads, configs, and URLs.
Compute SHA-256, SHA-512, MD5, and HMAC digests using native WebCrypto.