ToolNest logoToolNest.

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.

    Try next: Unix Timestamp Converter · Regex Tester · JSON Formatter

    How to Use the Cron Expression Generator

    1. Pick a preset to fill the five fields, or type values directly (minute, hour, day of month, month, day of week).
    2. Read the plain-English explanation — it updates live as you edit.
    3. Check the 'Next 5 runs' list to confirm the schedule fires when you expect.
    4. Click 'Copy Expression' and paste it into your scheduler (cron, CI, cloud).
    5. To decode an existing schedule, paste it into the 'Explain an expression' box and click Explain It.

    Why Use Our Cron Expression Generator?

    Common Use Cases

    Cron Expression Generator vs Alternatives

    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.