A cron parser, Base64, JSON formatter, URL encoding and eight more. Everything is computed in your browser, so nothing you paste reaches our server.
We just published a handful of small utilities at /tools: a cron expression parser that shows the next five runs, Base64 encoding, a JSON formatter and URL percent-encoding. They are free, need no account, and there is no upsell in the middle of them.
The interesting part is not what they do. It is where they do it.
None of these tools send anything anywhere. The cron expression you paste, the JSON you are debugging, the Base64 blob that might be a token: it is processed by JavaScript in your browser and never leaves it. There is no request to our backend, because there is no backend involved at all.
That sounds like a technical footnote. It isn’t. Think about what people actually paste into online formatters: staging database credentials inside a JSON config, an API key in a webhook payload, a JWT copied straight out of production logs. Every site that processes those server-side has that data in a request log, whether or not it wanted it.
We would rather not have it. Handling other people’s secrets is a liability we get nothing for.
The tools use only what the browser already ships: TextEncoder for UTF-8, btoa for Base64, JSON.parse, encodeURIComponent. The cron parser is about a hundred lines written from scratch.
That was a deliberate choice too. A tool that advertises “runs locally” while pulling a script from someone else’s CDN is only as local as that CDN’s operator decides. The dependency does not disappear because it is convenient.
The one exception, stated plainly: these pages carry our analytics, same as the rest of the site. It counts page views. It does not see what you type into the tools, and no tool input is ever transmitted.
Honest answer: because people search for this. Someone writing a crontab entry at 2am, squinting at */5 * * * * to check they got it right, is exactly the person who will want to know next week whether that job actually ran.
The less cynical answer: we look at cron expressions all day. The parser shows what we would want to see, which is the next five runs in your timezone, not a paragraph of prose describing the schedule back to you. Anyone who has been bitten by a UTC-versus-local mixup knows why that matters more than the wording.
Twelve of them: cron parser, Base64, JSON formatter, URL encoding, timestamp converter, UUID and ULID generator, SHA hashing, regex tester, chmod calculator, CIDR calculator, password generator, and a plain reference table of HTTP status codes.
That last one has no JavaScript at all, and the status code table has a column the other twenty such tables online do not: what each code means for a monitor. A 401 usually means your check lost its credentials, not that the service is down. A 429 means the service is alive and refusing you specifically.
And if you ever find yourself wondering whether the cron you just wrote actually fired last night, that part we also do. It just needs an account.
Sign up, get an API key, paste the curl into your cron. That's it.