Join Amazon and Flipkart Deals and products under 99 Telegram Channel: @atjust99

What this tool does

This is a visual editor for the standard five-field cron format used by Linux crontab, GitHub Actions, GitLab CI, and most cloud schedulers. You pick values for minutes, hours, day of month, month, and day of week. The tool shows a plain-English description of the schedule and lists the next 10 upcoming run times so you can verify it does what you think it does.

Everything runs in your browser. Nothing is sent to a server.

The five fields

If you haven't memorized the cron field order yet (I still look it up sometimes), here's the layout:

┌───── minute (0-59)
│ ┌───── hour (0-23)
│ │ ┌───── day of month (1-31)
│ │ │ ┌───── month (1-12)
│ │ │ │ ┌───── day of week (0-6, Sunday=0)
│ │ │ │ │
* * * * *

Each field takes a number, a comma-separated list (1,15,30), a range (1-5), a step value (*/15), or * for "every value." Those four operators cover almost every scheduling scenario you'll run into.

How to use it

Enter values in each field, or use the preset buttons to load common schedules like "every 5 minutes" or "Monday at 9 AM."
Read the human-readable description to confirm the schedule matches your intent.
Check the "Next 10 Runs" list. The times are in your browser's local timezone, so keep in mind your server probably runs on UTC.
Copy the final expression and paste it into your crontab -e, your CI config file, or wherever your scheduler reads from.

You can also paste an existing cron expression into the text field and the visual editor will update to match.

Syntax reference

Operator	Meaning	Example	Result
`*`	Every value	`*` in minute field	Runs every minute
`,`	List of values	`1,15,30`	Runs at minutes 1, 15, and 30
`-`	Range	`1-5` in day-of-week	Monday through Friday
`/`	Step	`*/15` in minute	Every 15 minutes

Presets included

The tool comes with presets for the schedules that come up most often: every minute, every 5 minutes, every hour on the hour, daily at midnight, daily at 9 AM, every Monday at 8 AM, first of the month at 8 AM. One click loads the expression and you can tweak from there.

Timezone gotcha

This is the thing that bites people most often. The "Next Runs" preview uses your local browser time, but most production crontabs run on the server's system clock, which is usually UTC. If you set up "every day at 9 AM" and your server is in UTC, the job will run at 9 AM UTC, not 9 AM in your local timezone. Always check timedatectl or equivalent on your server before deploying.

Frequently asked questions

Does this support 6-field (Quartz/Jenkins) cron? Not yet. This covers the standard 5-field POSIX format that Linux crontab and most CI systems use. Quartz uses an extra seconds field and has slightly different syntax for day-of-week.

What timezone does the preview use? Your browser's local timezone. Your server almost certainly runs on UTC, so mentally offset before deploying.

How do I schedule a job for "every Sunday"? Set day-of-week to 0. Some systems accept 7 as Sunday too, but 0 is the most portable value.

Can I use names like MON or JAN? Many modern cron engines accept three-letter names, but numeric values work everywhere including older Linux distributions. Stick with numbers if you're not sure.

What happens if I specify February 31st? Cron skips impossible dates. Setting day-of-month to 31 and month to 2 means the job simply never fires in February. The preview shows this correctly.

Is there a way to run something every 90 minutes? Not directly with a single cron expression. Cron fields are independent, so you can't express durations that cross field boundaries. The common workaround is to run every 30 minutes and have the script itself check whether 90 minutes have passed since the last run.

Can I use this for AWS EventBridge or Google Cloud Scheduler? AWS EventBridge uses a 6-field format with an extra year field and slightly different syntax. Google Cloud Scheduler uses standard 5-field cron, so this tool works directly for that.

How accurate is the "Next 10 Runs" preview? The calculation steps through time minute-by-minute. It accounts for month lengths and leap years. Edge cases like daylight saving transitions may show slight differences from your actual server behavior depending on how the server handles DST.

Related tools

Regex Playground - Test pattern matching with live highlighting.
Date Calculator - Calculate durations between dates.
Random Date Generator - Generate test dates for scheduling.
JSON Validator - Validate JSON config files for your cron jobs.

Cron Expression Builder