Cron Expression Generator: Build, Translate, and Test Cron Jobs Visually

TL;DR — The Cron Expression Generator builds cron strings visually, translates them to plain English, and shows the next 5 fire times so you can verify before deploying. For related work see the Unix Timestamp Converter and Date Calculator.

Why cron mistakes are so expensive

Cron has no "are you sure?". You ship */5 * * * * thinking "every 5 hours" when it actually means "every 5 minutes" — and now your nightly DB dump runs 288 times a day and your bill spikes. One asterisk in the wrong field becomes a 3 AM page.

The 5-field cheat sheet

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

Common patterns translated

Expression	Means
0 0 * * *	Every day at midnight (server time)
*/15 * * * *	Every 15 minutes
0 9 * * 1-5	9:00 AM on weekdays
0 0 1 * *	Midnight on the 1st of every month
0 */6 * * *	Every 6 hours (00, 06, 12, 18)
30 2 * * 0	2:30 AM every Sunday

Build a cron expression visually

1. Open the Cron Expression Generator.
2. Pick a preset (every hour / day / week) or click through each field with a dropdown.
3. Read the plain-English translation as you build.
4. Check the "next 5 fire times" — if those dates don’t match what you expect, your cron is wrong.
5. Copy the expression to your crontab, Kubernetes CronJob, GitHub Actions schedule, or AWS EventBridge rule.

Cron pitfalls that bite real systems

• Time zone. System crontab runs in server TZ (often UTC). A "9 AM" job is 4 AM Eastern. Convert intentionally — many platforms now let you set a TZ explicitly.
• Day-of-week vs day-of-month overlap. If both fields are set, classic cron OR-s them — your job fires on both. Use one or the other.
• Daylight saving. A job at 2:30 AM will fire twice or not at all during transitions. Stick to UTC for critical jobs.
• Overlapping runs. If your job takes 6 minutes and you schedule it every 5, you get pile-up. Add a lock or use a job runner that prevents overlap.
• Non-standard extensions. AWS, Quartz, and standard crontab differ on seconds field and year field. Check your platform’s docs.

Cron isn’t always the answer

For event-driven triggers (file uploaded, message in queue), use a real job runner. Cron is best for periodic, idempotent maintenance: backups, cleanup, report generation, cache warmup. If your job must run exactly once or has complex dependencies, reach for a workflow engine (Airflow, Temporal, GitHub Actions with conditions).

FAQ

What time zone does cron use?

The server’s local time by default. Set CRON_TZ=UTC at the top of crontab or use platform-specific TZ config to make it explicit.

Why didn’t my 0 0 31 2 * job ever run?

February doesn’t have a 31st. Cron silently skips impossible dates. Use the generator’s "next runs" preview to catch this.

How do I run a job every 90 minutes?

You can’t in standard cron — only divisors of 60 work cleanly with */n. Use two entries (0 0,3,6,9,12,15,18,21 * * *) or move to a job runner.

What’s the smallest cron interval?

One minute. For anything more frequent, use a long-running worker or an event-driven trigger.

Schedule-related tools

• Cron Expression Generator — visual builder + translator.
• Unix Timestamp Converter — for verifying fire times in your time zone.
• Date Calculator — for "what date is N days from now" planning.