If you’ve ever written 0 9 * * 1-5 from memory, you already know why a visual cron builder helps.

KeptTools includes a free cron expression creator that runs fully in the browser.

What you get

• Presets for common schedules

• Five-field editor (minute, hour, day, month, weekday)

• Human-readable summary

• One-click copy for crontab / workers

Sample:

0 9 * * 1-5 → weekdays at 09:00

Privacy

No paste is sent to a server for processing.

Open the tool: https://kepttools.com/cron-generator

More developer utilities: https://kepttools.com

I build a lot of small utilities into my day: format JSON, clean SQL, peek at a JWT, encode Base64, generate a hash, compress an image. The annoying part isn’t the task.
It’s trusting a random website with the paste.

Why that matters

Dummy data is fine anywhere. But real-ish data isn’t:

• a JWT from a staging app

• a SQL snippet with customer emails

• a Base64 payload that still holds sensitive text
  If the tool uploads your input, you’ve already lost control of it.

What I built

KeptTools is a free set of developer tools that run entirely in the browser. Nothing you paste is sent to a server for processing. On sensitive pages (JWT decoder, Base64, hash generator, password generator):

• no analytics

• no ads

• no third-party scripts
  You can verify this yourself: open DevTools → Network while you work.

Tools included

• JSON formatter & converter

• SQL formatter

• JWT decoder

• Base64 encoder / decoder

• Hash generator (MD5, SHA-1, SHA-256, SHA-512)

• URL & HTML encoder

• Regex tester

• Image convert / compress / crop / background tools

• and more everyday utilities
  Try it here: https://kepttools.com

What I’m looking for

Honest feedback:

1. Is “nothing leaves your browser” clear on first visit?

2. Which tool would you open every week?

3. What’s missing for your workflow? Thanks for reading. If you try KeptTools, please stress-test the privacy claim in Network — that’s the whole point.

That’s a trust problem. Tokens can include emails, roles, and session data. If the page uploads it, you just gave secrets to someone else’s server.

Here’s the fastest way to check any tool:

Use the Network tab

1. Open DevTools (F12)

2. Open Network

3. Paste a sample token

4. Watch for requests

If decoding fires a request with your token, leave.

A privacy claim is marketing. An empty Network tab is evidence.

Try a local decoder

I built a browser-only JWT decoder here:

https://kepttools.com/jwt-decoder

No account. Nothing uploaded. Open Network while you decode and confirm it yourself.

If you try it, tell me bluntly: is the privacy story clear in 5 seconds?

Is that seconds? Milliseconds? Yesterday? Next week?

I got tired of guessing — and tired of pasting values into random websites.

So I added a Unix timestamp converter to KeptTools. It runs in the browser. Nothing is uploaded.

👉 https://kepttools.com/timestamp

What it does

1. Paste a Unix timestamp

2. See UTC and local time

3. Copy the ISO value

4. Or tap Use now for the current epoch

Example:

• Input: 1729000000

• UTC: 2024-10-15T13:46:40.000Z

Useful when you’re reading created_at, writing a test, or checking an expiry field.

Why browser-only matters here

Timestamps themselves aren’t always sensitive.

But the habit is: once you start pasting API payloads into third-party sites, it’s easy to paste a token next.

I want the everyday tools on the same page as the privacy promise: work happens on your device.

Other tools in the suite

If timestamps are only one part of your day:

• JSON Formatter

• JWT Decoder

• JSON Converter

Full set: https://kepttools.com

Quick question

When an API returns epoch time, do you usually:

• convert it in code,

• use a browser tool, or

• guess from the length?

Tell me in the comments — I’m iterating based on real workflows.

What they don’t always make clear: that content often leaves your device.

For JSON with client data, a JWT, a draft you’re not ready to publish, or a passport-style photo — that’s a bad trade.

So I built KeptTools: a small set of developer and image tools that run in the browser. No account. No “upload to process.”

👉 https://kepttools.com

What “browser-only” means here

When you open a tool page:

• The work happens on the page (JavaScript in your browser)

• You can format, convert, crop, or decode without creating an account

• Closing the tab ends the session — nothing is stored as “your file” on our servers for processing

A few tools download a small model the first time (for example, portrait background replacement). That download is the model, not your photo.

What’s live

Developer tools

• JSON formatter / validator

• JSON converter (CSV, Laravel, TypeScript, PHP, and more)

• SQL formatter

• JWT decoder

• Base64, hash, URL/HTML encode

• Regex tester, cron generator, UUID/slug

Image tools

• PNG/JPG → WebP

• Compress

• Crop

• Image → SVG

• Change background (white / blue / custom / transparent)

Text utilities

• Word counter

• Case converter (camelCase, snake_case, kebab-case, and more)

Why I care about this

I use these utilities every week. I don’t want a random site keeping a copy of:

• a token

• a production-ish JSON blob

• an ID photo

Privacy shouldn’t be a premium feature for basic tools.

Stack (short)

Laravel + Vite + Tailwind + Alpine. Tools are client-side where it matters.

What I’d love feedback on

1. Is “browser-only / no upload” a strong enough reason to switch tools?

2. Which tool would you open first from the homepage?

3. What’s missing that would make you bounce?

If you try something and it feels unclear, tell me — I’m iterating from real use.

Try it: https://kepttools.com

paste some API JSON, get a clean Laravel array, a TypeScript interface, a PHP DTO, or CSV — without sending that payload to a random website.

So I built it into KeptTools.

What it does

The JSON Converter turns JSON into:

• a Laravel PHP array

• a TypeScript interface

• a PHP DTO class

• CSV

Everything runs in the browser. Nothing is uploaded.

Quick example

Input:

[
  {"id": 1, "name": "Ada", "role": "engineer"},
  {"id": 2, "name": "Linus", "role": "founder"}
]