Featured image: A close-up of text on a black screen. Photo by Pixabay on Pexels (Free to use).
Most “free online tools” top out at the basics: format some JSON, generate a UUID, done. The tools that actually save a professional’s afternoon are the ones that do something structural — sign a token, reformat a query, draw a diagram, split a network. Those are rare as free, local, no-signup tools, because they are genuinely harder to build.
These six close that gap. Each runs 100% in your browser, using the browser’s own crypto and engines, and each does a job the simple tools cannot. They join the 17-tool roundup on the AI Forward tools hub — this set is the power tier.
1. JWT Signer: Build Tokens, Not Just Read Them
Decoding a JWT is easy; signing one requires the actual HMAC primitive. The JWT Signer computes the HS256 signature with the Web Crypto API — the same crypto.subtle.sign your production libraries call — so you can generate a real header.payload.signature token from your own header, payload, and secret. The secret never leaves the tab, and the tool pairs with the JWT decoder to complete the loop: decode to understand, sign to build. It signs; it deliberately does not pretend to verify.
2. SQL Formatter: The One-Liner Civilizer
ORM logs emit SQL as a single 400-character line, and nobody debugs that. The SQL formatter tokenizes your query — keeping strings, comments, and quoted identifiers intact — then rebuilds it with structure: keywords uppercased, each major clause on its own line, AND/OR broken out, parentheses indented. It is a formatter, not a validator: dialect quirks pass through untouched, and your diff tool finally shows real changes instead of whitespace noise.
3. Regex Visualizer: Patterns You Can See
A 40-character regex is a language; a railroad diagram of it is a five-second scan. The regex visualizer parses a practical subset of regex — literals, \d \w \s ., character classes, groups, alternation, quantifiers, anchors — and draws the parse tree as an SVG diagram: boxes for atoms, containers for groups, branches for alternation, labels for quantifiers. It is built for reading other people’s regex, teaching, and screenshots that travel. Testing stays the regex tester’s job.
4. CIDR Subnet Calculator: Networks Without the Spreadsheet
Subnet math is a 10-minute spreadsheet exercise nobody should redo. The CIDR calculator takes 192.168.1.0/24 and returns everything — network, broadcast, first/last host, usable count, subnet and wildcard masks, address class — plus a ready-made split into eight smaller subnets, all computed with exact BigInt arithmetic (so /0 through /32 and the /31, /32 edge cases are correct). Network planning and VPC design get faster by exactly the time you used to spend recalculating.
5. Markdown Previewer: Write and See, No Build
Documentation drafts should not require a build step to read. The Markdown previewer renders live as you type — headings, emphasis, inline and fenced code, links, images, lists, blockquotes — with HTML escaped first so pasted markup stays inert. It targets the everyday 90% deliberately; tables and footnotes belong to full renderers, not to a preview pane. LLM prompt authors will recognize the second use case: structured Markdown prompts read exactly as intended.
6. Prompt Comparison Tester: Prompt Engineering, Measured
Prompt quality is a claim until you run the experiment. The prompt comparison tester runs two prompts side by side against any OpenAI-compatible API and reports both outputs, token usage, and latency. Requests go directly from your browser to the API provider — the site has no backend and never sees your key or prompts (the key is stored in localStorage for convenience; delete it on shared machines). Compare phrasings, output formats, or even two models — and price each side with the token cost calculator.
The Common Thread
All six share the properties that made the original 17 trustworthy: local execution (data never leaves the machine), the browser’s audited engines (Web Crypto, native parsers), and zero accounts (static pages, no quota pages, nothing to break). The difference is the depth of the job each one does — structural work that used to require a library, a script, or a spreadsheet. That is the whole thesis of the tools hub: the browser is the most underused development environment you already own.
Frequently Asked Questions
Tool behavior verified against the ECMAScript, Web Crypto, RFC 7519 (JWT), and RFC 4632 (CIDR) specifications as of November 2026.
