Ascii85 Encoder and Decoder
encoding
Encode text or uploaded files as Adobe Ascii85, or decode Ascii85 back to binary. It all runs in your browser, so your input stays on the device.
Percent-encode or decode URL text using component, path, query, fragment, or userinfo rules. It runs in your browser, so your input stays on the device.
Runs in your browser — your input is processed on this device and never uploaded.
Percent-encoding, defined in RFC 3986, writes a byte as a percent sign followed by two hexadecimal digits. A space becomes %20. It exists so that characters with a structural job in a URL can also appear as ordinary data without breaking the URL apart.
Choose Encode to percent-encode UTF-8 text, or Decode to turn encoded octets back into text. The character set option picks which context you are encoding for: component, path, query, fragment, or userinfo. It applies to encoding only and is ignored when decoding.
Different parts of a URL reserve different delimiters. A slash is structure in a path and ordinary data in a query value. An ampersand separates parameters in a query and means nothing special in a fragment.
So there is no single correct escaping. Encode a value with path rules and drop it into a query string and you can leave an ampersand unescaped that splits your parameter in two. Picking the set that matches where the value is going is the whole point of the option.
Percent-encoding is not the same as application/x-www-form-urlencoded, and this tool does the former. A plus sign is not treated here as a universal stand-in for a space, so form payloads that rely on that convention need a form encoder instead.
For binary data rather than URL text, use Base64, Base32, Hex Encoder, or Ascii85. Percent-encoding arbitrary bytes works but triples the size of anything non-ASCII.
Encoding an already encoded value is the classic mistake. The percent signs themselves get encoded, %20 becomes %2520, and the damage is invisible until something downstream decodes once and hands on a string that still contains %20.
Decoding is not context-sensitive the way encoding is, which is why the character set option greys out. A %2F is a slash regardless of which part of the URL it came from.
More encoding tools on ToolkitBay.
encoding
Encode text or uploaded files as Adobe Ascii85, or decode Ascii85 back to binary. It all runs in your browser, so your input stays on the device.
encoding
Encode text or uploaded files as Base64, or decode Base64 text and files back to binary. It all runs in your browser, so your input stays on the device.
encoding
Encode text or uploaded files as Base32, or decode Base32 text and files back to binary. It all runs in your browser, so your input stays on the device.
encoding
Encode text or uploaded files as lowercase hexadecimal, or decode hex back to binary. It all runs in your browser, so your input stays on the device.
encoding
Encode bytes as whole-value Base62, or decode Base62 text back to bytes. Choose either supported digit and letter ordering.
Find similar tools by category or tag.