Free Online Cron Expression Generator
Last updated: 2026-10-17
Quick answer: Stop guessing cron syntax. Our free cron expression generator builds valid schedules field by field, explains any expression in plain English, and shows the next 5 run times — so you can verify a schedule before it ever hits production. No signup, everything runs in your browser.
Build a schedule
Next 5 runs (your browser's local time)
🔒 100% Private: Data never leaves your device.
Field syntax: * every · */5 every 5 · 1,15 list · 9-17 range. Month and weekday names (JAN–DEC, MON–SUN) also work.
Explain an expression
✓ Free forever · ✓ No signup · ✓ Tool inputs stay in your browser — never sent to our servers.
How to Use the Cron Expression Generator
- Pick a preset to fill the five fields, or type values directly (minute, hour, day of month, month, day of week).
- Read the plain-English explanation — it updates live as you edit.
- Check the 'Next 5 runs' list to confirm the schedule fires when you expect.
- Click 'Copy Expression' and paste it into your scheduler (cron, CI, cloud).
- To decode an existing schedule, paste it into the 'Explain an expression' box and click Explain It.
Why Use Our Cron Expression Generator?
- Visual schedule builder — fill five fields or start from 12 common presets; the expression builds itself.
- Plain-English explanations — every expression is translated into readable schedule language.
- Next-run preview — see the next 5 exact run times in your local timezone before you deploy.
- Full cron syntax — steps (*/5), lists (1,15), ranges (9-17), and month/weekday names all supported.
- 100% private — parsing and calculation happen in your browser; schedules never leave your device.
Common Use Cases
- Nightly database backups: Schedule a dump at 2 AM — '0 2 * * *' — when traffic is lowest, then verify the 'Next 5 runs' preview matches your maintenance window before it touches production.
- Off-hours CI builds: Run the full test suite or nightly build at 1 AM on weekdays ('0 1 * * 1-5') so developers wake up to green or red, not a queue competing with daytime commits.
- Scheduled digest emails: Fire a weekly metrics summary every Monday at 9 AM ('0 9 * * 1') — build the expression here, paste it into your job queue or cloud scheduler, and never hand-roll the syntax again.
- Uptime and certificate checks: Ping health endpoints every 5 minutes ('*/5 * * * *') or check SSL expiry daily — a two-line cron schedule beats a paid monitoring tier for simple cases.
- Content and social queues: Publish queued posts, rotate featured content, or trigger newsletter sends at fixed times — decode an inherited expression with the explainer first so you don't double-publish.
Cron Expression Generator vs Alternatives
- crontab.guru: The classic explainer: paste an expression, get a plain-English reading. Excellent for decoding, but it's explain-only — no visual builder, no preset library, no next-run preview.
- AWS EventBridge / cloud scheduler consoles: A GUI picker tied to your cloud account, with the vendor's own 6-field dialect. Convenient if you live in AWS, but it won't help with GitHub Actions, plain cron, or any other scheduler.
- Man pages and cheat sheets: Authoritative and always correct, but slow — you're translating field tables in your head and there's no way to verify the schedule fires when you think it does.
- Writing expressions from memory: Fast for the five schedules you've memorized, typo-prone for everything else — and a wrong field can mean a job that never runs or runs 60× too often. This page builds the expression, explains it back to you, and previews the next 5 runs, all in your browser with no signup.
If your jobs live entirely in AWS, EventBridge's console picker is the path of least resistance. For everything else — plain cron, CI pipelines, GitHub Actions, or just decoding a schedule someone left you — this page is the fastest free way to build, explain, and verify an expression before it ever reaches production.
Frequently Asked Questions
What is a cron expression?
A compact schedule format — five fields (minute, hour, day of month, month, day of week) — originally from Unix cron, now used by CI systems, cloud schedulers, and job queues. '0 9 * * 1' means 'at 9:00 AM every Monday'.
What do the five fields mean?
In order: minute (0–59), hour (0–23), day of month (1–31), month (1–12), day of week (0–6, Sunday=0). An asterisk means 'every'. So '30 14 1 * *' is 2:30 PM on the 1st of every month.
What does */5 mean in cron?
A step value: 'every 5 units'. '*/5' in the minute field runs every 5 minutes (at :00, :05, :10…); '*/2' in the hour field runs every 2 hours. Steps also work on ranges, e.g. '0-30/10' = minutes 0, 10, 20, 30.
How do I schedule a job every weekday at 9 AM?
Use '0 9 * * 1-5': minute 0, hour 9, any day of month, any month, weekdays Monday(1) through Friday(5). You can also write '0 9 * * MON-FRI' — weekday names work too.
What happens if I set both day-of-month and day-of-week?
Standard cron runs when EITHER matches (OR logic). '0 0 1 * 0' fires on the 1st of the month AND every Sunday. If you want AND logic, your scheduler probably doesn't offer it — run the job more often and gate inside your code.
Will this expression work in AWS EventBridge or GitHub Actions?
Mostly yes — both accept standard 5-field cron (GitHub Actions uses UTC). Watch out for schedulers with their own dialects: AWS EventBridge and Quartz use 6–7 fields (with seconds and year), so strip or pad fields when moving between systems.
How do I schedule a cron job to run every 2 hours?
Use '0 */2 * * *': minute 0, then every 2nd hour (00:00, 02:00, 04:00…). The */n step syntax works in any field — '*/15 * * * *' is every 15 minutes, '0 0 */3 * *' is every 3 days. Paste the result above and check the 'Next 5 runs' preview to confirm.
What do @daily, @weekly, and @reboot mean in cron?
Shortcut macros some cron implementations accept instead of five fields: @daily = '0 0 * * *', @weekly = '0 0 * * 0', @monthly = '0 0 1 * *', @yearly = '0 0 1 1 *', @reboot = run once at startup. Handy, but not portable — GitHub Actions, AWS EventBridge, and most cloud schedulers don't understand them, so stick to the five-field form for anything that leaves your server.
Why didn't my cron job run?
The usual suspects: the crontab file is missing its trailing newline (cron silently ignores the last line), an unescaped % in the command (cron treats % as a newline), a bare command name with no PATH (cron's PATH is minimal — use absolute paths), the cron daemon not running, or a timezone mismatch (the server runs UTC while you assumed local time). Check the 'Next 5 runs' preview here first, then verify with a trivial '* * * * * echo test' job.
How do I schedule a job for the last day of the month?
Plain cron can't express 'last day of month' — months have 28–31 days. The common workarounds: run daily and let the script check if tomorrow is the 1st ('0 9 * * *' + a date check inside your code), or schedule three expressions covering the 28th–31st and gate inside the job. If your scheduler supports it, a systemd calendar timer or cloud scheduler 'last day' option is cleaner.
How do I stop cron from emailing me after every run?
Cron emails the job's output to the crontab owner. Silence it per-job by redirecting: '0 9 * * * /path/to/job.sh > /dev/null 2>&1'. To disable mail for the whole crontab, add 'MAILTO=""' at the top. Better practice: log to a file instead ('>> /var/log/job.log 2>&1') so you keep the output without the inbox spam.
What's the difference between cron and a systemd timer?
Both schedule recurring jobs on Linux. systemd timers are the modern alternative: they log to journalctl (so failures are actually visible), support randomized delays and 'run if the machine was off at schedule time' (Persistent=true), and express calendar dates more flexibly. Cron's advantage is ubiquity — it exists on every Unix, in CI systems, and in cloud schedulers, and its five-field syntax is the lingua franca. Use the generator above to get the expression right either way.