Free tool · Runs in your browser
Cron, translated to
plain English
Paste a cron expression, get a plain-English summary and the next 5 times it actually fires — in UTC, no guessing.
Cron expression
Standard 5-field cron: minute hour day-of-month month day-of-week. Supports *, ranges (1-5), steps (*/15) and lists (1,15,30). All times are UTC — convert from your local offset before scheduling.
In plain English
Runs at 09:00 UTC on Monday, Tuesday, Wednesday, Thursday, Friday (times in UTC).
Next 5 runs (UTC)
- Jul 28, 2026, 9:00 AM
- Jul 29, 2026, 9:00 AM
- Jul 30, 2026, 9:00 AM
- Jul 31, 2026, 9:00 AM
- Aug 3, 2026, 9:00 AM
Why cron schedules are worth double-checking
"Every day at 9am" isn't 0 9 * * *
It is, actually — but the field order (minute, hour, day, month, weekday) trips up almost everyone once. A misplaced field silently schedules the wrong thing.
UTC hides in plain sight
A cron job scheduled for 09:00 without a timezone conversion step fires at 09:00 server time — usually UTC — not 09:00 wherever you happen to be sitting.
Gated crons still need a correct schedule
A KV work-signal or feature flag can stop a cron from doing anything when idle, but it still has to fire on the schedule you meant, or the gate check never runs.
"Next run" beats mental math
For anything past a daily schedule — every 15 minutes on weekdays, first of the month — working out the actual next few timestamps by eye is where mistakes hide.
Questions, answered honestly
Does this support Cloudflare Cron Triggers syntax?
Yes — this tool works entirely with the standard 5-field format (minute, hour, day-of-month, month, day-of-week), which is what Cloudflare Cron Triggers, most CI systems, crontab, and Norbelys's own scheduler crons all use. It doesn't support the non-standard 6-field seconds-first variant some libraries add.
What timezone are the results in?
All times are computed and shown in UTC. A schedule written for 09:00 UTC fires at a different local hour depending on your timezone and daylight saving — convert your intended local time to UTC before writing the expression.
Why does it show "no occurrence found"?
The tool scans forward minute by minute (capped at two years) looking for a match against all five fields. Some day-of-month + month combinations never occur (day 31 restricted to a month field that excludes every 31-day month) — if nothing is found, that's usually why.
What cron syntax features are supported?
Ranges (1-5), steps (*/15), lists (1,15,30) and wildcards (*) are all supported and can be combined per field, same as standard cron. Named months/weekdays (JAN, MON) are not supported — use their numeric equivalents.
What can I use this for?
Cloudflare Workers Cron Triggers, GitHub Actions schedule:, most `crontab -e` entries, and application-level schedulers. This tool is generic date-math, not tied to any one platform.
Scheduling something that touches customer data?
Norbelys's own background workers gate every cron on a KV work-signal, so idle tenants never touch the database — the schedule still has to be right first.
Start sendingFrom $29/mo · Cancel anytime