# 15 developer tools that never upload your data

Most online developer tools are thin wrappers around a server: paste a JWT, a production config, or a customer's CSV, and it goes somewhere you cannot see. The fifteen tools at [ryuslog.com/tools](https://www.ryuslog.com/tools) work the other way — everything runs in the tab, with `JSON.parse`, `crypto.subtle` and ordinary JavaScript. No upload, no account, no rate limit.

Here is what each one does, and the detail worth knowing before you use it.

## Data and configuration

- **JSON Formatter** — format, validate and minify, sort keys, unescape a pasted JSON string, and generate TypeScript interfaces from a real payload.
- **YAML ↔ JSON** — both directions with indent control, plus presets for Kubernetes manifests and GitHub Actions workflows.
- **CSV ↔ JSON** — CSV, TSV or semicolon-separated input with quoted fields, header control and a download of the result.
- **SQL Formatter** — PostgreSQL, MySQL and SQLite dialects, uppercase keywords, one clause per line.

## Code and text

- **Text Diff Checker** — line-by-line comparison with added and removed highlighting, line numbers, and an ignore-whitespace mode for `git diff -w` style reviews.
- **Regex Tester** — live match highlighting, capture groups and a replacement preview, so a greedy quantifier is visible before it ships.
- **cURL to Code** — paste a curl command and get `fetch`, TypeScript, Python `requests` or Go `net/http` with headers and body intact. The shell quoting is the hard part, and it is what gets lost when you translate by hand.

## Tokens and encoding

- **JWT Decoder** — header and payload side by side, every standard claim (`sub`, `iss`, `aud`, `exp`, `nbf`, `iat`, `jti`) with readable dates, and an expiry check.
- **Base64 Encode / Decode** — UTF-8 text both ways, including URL-safe Base64 for tokens and query strings.
- **Hash Generator** — MD5, SHA-1, SHA-256 and SHA-512 as you type, lower or upper case hex.
- **URL Parser & Encoder** — split a URL into protocol, host, path and query parameters, or percent-encode and decode text.

## Time and colour

- **Timestamp Converter** — Unix timestamps and date strings in both directions, with relative time and time zone views.
- **Cron Expression Parser** — explain a five-field expression in plain English and list the next times it will run, in local time and UTC.
- **UUID Generator** — 1 to 100 UUID v4 values, formatted for JSON or SQL.
- **Color & Contrast** — HEX, RGB, HSL and OKLCH conversion with WCAG 2.1 AA/AAA contrast checks and copy-ready CSS and Tailwind snippets.

## Why client-side is the point

Two reasons. The first is privacy: a JWT is a bearer token, and a production YAML file often contains secrets; neither should travel to a stranger's server to be formatted. The second is durability: a tool with no backend cannot rate-limit you, log you out, or disappear behind a paywall.

The trade-offs are real, though. There is no history and no sync, and very large inputs are bounded by what a tab can hold. If you want the engineering details — OKLCH conversion, LCS diffing, cron next-run search, Web Crypto's gaps — they are written up at [ryuslog.com](https://www.ryuslog.com), and the same techniques show up in the guides on [Kubernetes resources and OOMKilled](https://www.ryuslog.com/blog/kubernetes-resource-requests-limits-qos-classes-and-oomkilled) and [React useEffect races](https://www.ryuslog.com/blog/react-useeffect-dependencies-cleanup-and-race-conditions).

