Category
Encoding tools.
Encode, decode and convert between common text and time formats, instantly.
Encoding tools
- EncodingLive
Timestamp Converter
Convert between Unix epoch, ISO 8601 and human-readable dates.
Paste a Unix timestamp in seconds or milliseconds, or an ISO 8601 date, and convert it across epoch, UTC and local time with relative age. Pure client-side.
Open tool - EncodingLive
Base64 Encoder / Decoder
Encode and decode Base64 and URL-safe Base64, with Unicode support.
Paste text or Base64 to encode or decode in either direction, with standard and URL-safe alphabets and full UTF-8 handling. Pure client-side.
Open tool - EncodingLive
JSON ↔ YAML Converter
Convert JSON to YAML and back — with honest warnings about what changes.
Convert JSON to YAML or YAML to JSON with a real YAML 1.2 parser, and see every comment, anchor, merge key, timestamp and out-of-range integer the conversion costs you. Catches the "Norway problem" in both directions. Pure client-side, no upload.
Open tool - EncodingLive
URL Encoder / Decoder
Percent-encode, decode, and parse query strings — with per-component RFC 3986 rules.
Percent-encode a value for the position it actually lands in, decode one that came back mangled, or split a whole URL into its components and a decoded query-parameter table. Double-encoding, + vs %20, punycode hosts and repeated keys are named, not guessed. Pure client-side.
Open tool
When you reach for Encoding tools.
Encoding tools are the ones you use ten times a day and never think about — until the round trip is not clean and you cannot tell whether the problem is your data, your encoder, or the terminal you pasted through.
Most of the failures are about variants nobody documents. Standard Base64 versus the URL-safe alphabet that swaps + and / for - and _. Whether padding is present. Whether a URL encoder is escaping a whole URL or a single query parameter, which need different treatment for characters like & and =.
These are built to make the variant explicit rather than guessing, and to round-trip losslessly so you can confirm the transformation rather than assume it.