Inspect JSON, XML, encodings, tokens and patterns, or generate identifiers and passwords. Decoding and heuristic checks do not establish security.
Validate strict JSON before copying or downloading.
Read claims; decoding does not verify the signature.
Test JavaScript matches on a small sample first.
Parse and reformat JSON in raw/tree views.
Inspect readable JWT sections locally.
Generate random passwords or local-list passphrases.
Check well-formedness and reformat XML text.
Run a JavaScript regular expression on sample text.
Convert a simple CSV table to JSON or JSON objects to CSV.
Translate epoch values and local date/time input.
Convert a color and estimate contrast on a background.
Encode text or decode Base64 data.
Encode/decode URL text in whole-URL or component mode.
Estimate strength using length, character classes and pattern checks.
Compute text or file checksums locally.
Generate random v4 or custom time-based v1 identifiers.
Base64 turns binary data into text characters. This guide explains why it exists, when developers actually need it, and common mistakes to avoid — with real-world examples.
Standard JSON is strict — no comments, no trailing commas, keys must be quoted. JSONC and JSON5 relax these rules. Here is when each format is the right choice.
When you use an online PDF tool or image compressor, does your file stay on your device or get uploaded to a server? The difference matters more than you think.
Understand SHA-256 checksums, one-way hashing and file verification. General-purpose hashes are not a substitute for dedicated password hashing.
SyntaxError: Unexpected token at position 847. Sound familiar? This checklist covers the most common JSON errors and how to fix them quickly.
A practical regex cheat sheet with copy-paste patterns for the most common validation tasks — email, URL, phone number, date, IP address, and more. Includes explanations and test examples.
