Cron Expression Generator & Tester Online Free
Generate and test cron expressions. Visual builder, human-readable description, next 5 execution times.
🔒 Your file never leaves your browser. All processing runs locally.
Format: minute hour day-of-month month day-of-week
Description
Every 5 minutes
Next 5 executions
- 1. 8/23/2026, 1:55:00 PM
- 2. 8/23/2026, 2:00:00 PM
- 3. 8/23/2026, 2:05:00 PM
- 4. 8/23/2026, 2:10:00 PM
- 5. 8/23/2026, 2:15:00 PM
How to Generate Cron Expressions Online
- 1
Type or build a cron expression
Enter a 5-field cron expression directly, or use the visual builder to set minute, hour, day, month, and weekday fields.
- 2
Read the human-readable description
The tool converts your expression to plain English using cronstrue, so you can verify the schedule is correct.
- 3
Copy the expression
Copy the cron string and paste it into your scheduler (crontab, GitHub Actions, Cloud Scheduler, etc.).
Cron syntax is fifty years old and still runs the world's scheduled jobs — from crontab entries on a single server to Kubernetes CronJobs, GitHub Actions schedules, AWS EventBridge rules, and every CI pipeline's nightly build. Its five terse fields (minute, hour, day of month, month, day of week) are powerful but notoriously easy to get subtly wrong, and a wrong schedule fails silently: the job simply runs at 3 AM Sunday instead of 3 PM Monday, and nobody notices for weeks.
Building vs. reading: this tool works in both directions. Compose a schedule with the dropdowns and get the expression; or paste an inherited expression and get a plain-English translation of when it actually fires. The translation step is where mistakes surface — 0 12 * * 1-5reading back as "at 12:00 on weekdays" either confirms your intent or exposes the bug.
The classic traps: day-of-month and day-of-week are OR-ed, not AND-ed, when both are restricted (0 0 13 * 5 fires on the 13th and on every Friday, not only Friday-the-13th); step values like */7in the day field do not mean "weekly"; and the schedule runs in the server's timezone, which on most cloud platforms is UTC — check offsets before assuming local time.
Related timing tools:when a job's logs show raw epoch timestamps, the Unix timestamp converter translates them; and the regex tester helps when you are parsing those logs in the first place.