about · trydevtoolsv1.0MIT licensed

We built this so you'd stop tab-hopping at 2 a.m.

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.

780
tools shipped
and counting
12
categories
all linkable
100%
client-side
no server touches data
0
trackers
no analytics, no pixels
the story

Born from a folder of 47 bookmarks.

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 — 780+ 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.

principles

What we actually believe.

Five non-negotiables that decide what gets built and what gets rejected.

01 / 05principle
Privacy is the architecture, not the policy.

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.

02 / 05principle
No business model that depends on you.

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.

03 / 05principle
Speed is respect.

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.

04 / 05principle
Inspectable by default.

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.

05 / 05principle
Linkable state.

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.

hard noes

Things we will never do.

Every “free” dev tool eventually does at least three of these. We've put it in writing so we don't.

Sell or share your data with anyone
Run analytics or fingerprinting in the background
Put a paywall in front of a tool you used yesterday
Require an account, an email, or a phone number
Show a popup, a modal, or a cookie banner
Upload your inputs to a "queue" for processing
Ship a feature flag that quietly nerfs the free tier
Sell the project to a private-equity buyer
the platform

Every tool inherits the rest of the toolbox.

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.

every tool gets, for free
× 780
⌘KFuzzy search
From any tool, jump to any other in 2 keystrokes.
FFocus mode
One key to hide chrome and go fullscreen.
URLLinkable state
Input and settings encode into the URL.
⤓Copy & download
Every result is copy-to-clipboard or file-export ready.
◐Dark + light
Theme persists across visits and tools.
◳Embed-ready
Drop a tool into an iframe with a clean layout.
◉Offline-capable
After first load, no network round-trip required.
○Zero deps to learn
No accounts, no SDK, no API key — just paste.
+ per-tool OG card, JSON-LD schema, breadcrumb, sitemap entry, and canonical URL — generated at build, never written by hand.