Skip to content

Category

Developer Tools – Online Utilities & Calculators

Developer-focused formatting, conversion, debugging, and text generation tools that run in the browser with no server-side code processing.

Developer tools here cover the daily small jobs: JSON and XML formatting, regex testing, JWT inspection, timestamp conversion, URL encoding, and code cleanup. All parsing happens in your browser — paste production data without it leaving the machine.

All Developer Tools

JSON formatting you can trust

The formatter uses the same JSON.parse the language itself uses, so a successful parse means the payload is valid JSON per the spec (RFC 8259). Common failures are trailing commas (invalid), single quotes (invalid — JSON requires double), and unescaped control characters in strings. The error message points to the character position where parsing stopped.

Timestamps and JWTs, demystified

  • Unix timestamps are seconds (or milliseconds — the tool detects 10 vs 13 digit values) since 1970-01-01 UTC. Converting shows the result in UTC and your local zone; a "wrong" result is almost always a timezone reading, not a wrong conversion.
  • JWT decoding is base64url of the header and payload — it does not verify the signature. A decoded token proves nothing about authenticity; verification requires the secret or public key.
  • Regex testing uses the browser’s native engine (JavaScript flavor): lookaheads and named groups work, but lookbehind support depends on browser age.

Common mistakes

  • Encoding a whole URL when only query values need encoding (and vice versa) — the path slashes should usually survive.
  • Treating a decoded JWT’s exp claim as local time; it is always Unix seconds UTC.
  • Pasting JSON with a BOM or trailing newline and assuming the parser is broken.