Most online dev utilities are ad-stuffed, sign-up-walled, or quietly shipping your payload to a server. trydevtools is the opposite: one tab, every tool you need, nothing leaves the page. We're engineers building for engineers.
Every developer has the same dropdown in their bookmarks bar: json formatter, base64 encoder, jwt decoder, regex tester, cron parser. Eleven tabs deep in tools you do not trust, each gated by a banner ad or a sign-up or a sketchy server that wants your payload.
We got tired of it. We started with one well-built JSON formatter that ran entirely in the browser. Then a JWT decoder. Then a hash generator. Three years later that folder is gone and this is here instead — 779+ tools that respect your time and your data the way internal tooling does, except shared with everyone.
There is no startup behind this, no funding round to chase. It exists because we needed it to exist.
Five non-negotiables that decide what gets built and what gets rejected.
Every parser, formatter, decoder, generator — all of it runs as JavaScript in your tab. There is no server-side fallback to fall back to. You can paste production credentials, internal payloads, raw customer data; the network panel stays empty.
No accounts. No paid tier. No waitlist. No newsletter that you have to dismiss. No "unlock pro features." When the incentive to monetise users disappears, so does most of the friction.
Pages are statically rendered. Tools are small chunks loaded on demand. Most operations finish in under a millisecond. We treat your time the way an unfair ad-tech stack doesn't.
Source is open. Bundles aren't minified into an opaque blob. Crack open DevTools, read the function, audit the math, then decide to trust it. That's how trust is supposed to work.
Inputs and settings serialise into the URL where it makes sense. Send a teammate a link, they see exactly what you see — no "share" button, no document IDs, no expiring sessions.
Every “free” dev tool eventually does at least three of these. We've put it in writing so we don't.
The job of a tool is to format JSON, decode a token, generate a UUID. Everything around it — search, sharing, search rankings, accessibility — is the platform's job. You shouldn't have to rebuild any of it.