Getting started: turn text into verifiable results
Open any operation page and choose "Run in browser" to reach /app/?lang=en&tool=<operation-id>. The left pane holds input and parameters; the right pane holds the result (tabs on mobile). Press Run to see phase names, real byte counts, format and elapsed time.
Base64: enter 你好 🚀 and choose encode to get 5L2g5aW9IPCfmoA=; choose decode with that string to recover the original. Encoding works on UTF-8 bytes so Chinese and emoji survive. Inputs like !!! or YS== raise INVALID_BASE64 instead of being silently swallowed.
JWT: paste a three-segment token to see header, payload, UTC renderings of iat/exp, and every decode error. Remember it is decode-only, NOT signature verification: signatureVerified is always false and signatureVerification is always NOT_PERFORMED. A non-JSON segment is shown as raw text and recorded in errors, never presented as a valid payload.
Hash: enter abc with sha256 to get ba7816bf8f01cfea414140de5dae2223b00361a396177a9cb410ff61f20015ad — a literal that the tests also compare against Node built-in crypto. MD5 and SHA-1 are for compatibility checks only, never passwords or signatures.
Timestamp & Cron: 0 with unit s yields 1970-01-01T00:00:00.000Z and 0 ms; 1700000000000 is auto-detected as ms and reports 1700000000 s. Cron uses strict 5 fields such as */15 0-4 1,15 * 1-5 and prints expanded fields plus upcoming UTC times; 60 * * * * reports an out-of-range error. Every time is labelled Z/UTC or the chosen zone.
URL encoding: encodeURI preserves https:// and ?& while encodeURIComponent escapes them too. Only form (application/x-www-form-urlencoded) decoding treats + as a space; in decodeURI / decodeURIComponent, + is a literal plus and %2B always stays a plus sign.
Exceeding 1 MiB (64 KiB for JWT) fails immediately with a reason and keeps your input. No network request is made and no input text enters analytics.