Developer

Developer

Browse 22 professional tools

AI Playground

Developer

API Response Mocker

Developer

Chmod Calculator

Developer

Code Formatter & Beautifier

Developer

CORS Debugger

Developer

Docker Compose Builder

Developer

Git Command Builder

Developer

Git Commit Message Generator

Developer

Gitignore Generator

Developer

HTTP Status Codes Reference

Developer

JSON Schema Generator

Developer

JSON to TypeScript Converter

Developer

JSONPath Tester

Developer

JWT Builder

Developer

JWT Decoder

Developer

Regex Tester

Developer

SQL Formatter & Beautifier

Developer

SQL Playground

Developer

Test Credit Card Generator

Developer

User Agent Parser

Developer

XPath Tester

Developer

XSLT Transformer

Developer

The Developer category covers the tools you reach for during the actual programming day — formatting JSON, building regex patterns, decoding JWTs, debugging CORS, generating .gitignore files. The interesting question is not "do these exist elsewhere" (every dev tool has at least three online versions) but which ones you should reach for first, which are safe to paste production data into, and which are quietly wrong in ways that bite you later. These all run locally in the browser; nothing you paste leaves the page.

Parsing, validation, transformation

For testing expressions against real data. JSONPath and XPath have multiple dialects (RFC 9535 vs Jayway vs Goessner; XPath 1.0 vs 2.0/3.1) — verify against the exact engine your production code uses before shipping a query.

Formatting

Beautifying minified JSON / SQL / code blobs. Prettier-compatible defaults; SQL dialect selection (Postgres / MySQL / SQLite / BigQuery) preserves dialect-specific quoting.

Auth & API debugging

JWT pair lets you both inspect and construct test tokens. CORS debugger walks the same algorithm the browser uses (Fetch spec §3.2) so you can find the exact step where preflight or credentials handling breaks.

Git & deployment

Conventional Commits, common git recipes, and the few-second .gitignore generator that prevents node_modules ending up in history. Compose builder targets v2.x (the `version:` line is no longer needed).

Systems & data

Unix permission math, CIDR subnet math, an in-browser SQLite playground via WebAssembly, and an LLM tokenization sandbox. The SQL playground handles 1-10M rows comfortably; beyond that switch to a real database.

Frequently asked questions

Why use a browser tool when I have the same thing locally?

Two reasons: zero-install for one-off uses, and pasting test data without it being in your shell history or in a temp file you forget to delete. For repeated daily work, native tools (jq, regex in your editor) are faster.

Are these safe to paste production data into?

Every tool in this category runs entirely in the browser tab — no upload, no logging, no telemetry on the inputs themselves. The page itself is served from the site; pasted text never reaches the server. The risk model is "is your browser trustworthy" which is the same risk model as any web app.

Which tools work offline?

All of them, once the page is loaded. The JS bundle runs entirely client-side; refreshing without internet still works as long as the browser cached the page. Useful when debugging from a hotel WiFi captive portal.

How do I pick between similar tools?

For format-conversion tasks (JSON ↔ TypeScript, sample → schema), pick the direction matching your workflow. For inspection tasks (JWT, regex, JSONPath), pick the one that matches the engine your production code uses — RFC 9535 JSONPath produces different results than Jayway JSONPath on the same input.

Last updated · E-Utils editorial team