Ultimate Guide · 2026

Cron Expression Cheat Sheet: 50 Real-World Schedules Explained in Plain English

Cron is the quiet engine behind most of the internet — but its five cryptic fields scare away more developers than almost any other syntax. This guide breaks every field and special character down into plain English, then gives you 50 real-world schedules you can copy straight into your crontab, CI pipeline or cloud scheduler.

Written by Benjamin Rotshtein

Updated August 6, 2026

Download as PDF

What is a cron expression?

A cron expression is a compact string of five fields that tells a schedulerwhen to run a job. The cron daemon on Linux, GitHub Actions, cloud schedulers and thousands of libraries all speak the same five-field dialect:

# ┌───────────── minute (0 - 59)
# │ ┌───────────── hour (0 - 23)
# │ │ ┌───────────── day of the month (1 - 31)
# │ │ │ ┌───────────── month (1 - 12)
# │ │ │ │ ┌───────────── day of the week (0 - 7) (0 or 7 is Sunday)
# │ │ │ │ │
# * * * * * command-to-run

Each field is either a concrete value, a range, a list, or a wildcard. When a field is *, it means “match any value” — the job runs whenever that field would not otherwise rule it out.

Special characters: the operators behind real schedules

Almost every interesting cron expression is built from just seven operators. Learn these and you can read — and write — any schedule on the planet:

50 real-world cron schedules, explained

Here is every schedule from our cron schedule library, grouped by use case. Click any card to open its dedicated page with the next five run times and copy-paste code for Python, Node.js, Bash and n8n.

Frequent intervals: monitoring, syncs and heartbeats

Daily jobs: rollups, backups and off-peak processing

Weekly jobs: reports and weekday automation

Monthly & yearly jobs: billing, archives and maintenance

How to read any cron expression in plain English

Reading cron is just pattern-matching. Start at the left: ask which minute, then which hour, then which days. For 0 9 * * 1-5 the answer is: minute zero, hour nine, any date, any month, days Monday through Friday → “weekdays at 9 AM”. For */15 * * * * the step operator tells you the minute field matches every 15th minute →“every 15 minutes”.

The fastest way to sanity-check an expression before deploying it is to see the next real execution times. Our cron generator translates any expression into plain English and previews the next five runs live — no installation needed.

Common cron mistakes (and how to avoid them)

• Confusing day-of-month with day-of-week. 0 0 1 * 1 means the 1st of the month or any Monday — not “the first Monday”. Use the # operator for “the Nth weekday”.
• Forgetting cron runs in server time. A job at 0 9 * * * runs at 9 AM in the scheduler’s timezone, not yours. Always confirm the timezone of your host, CI service or cloud scheduler.
• Using five fields in a six-field system. Quartz and some cloud schedulers accept seconds — but Linux cron does not. Check the documentation of your platform before copying an expression.
• Assuming daylight saving is handled. During DST transitions an hourly job can run twice or not at all. Schedulers like cron do not adjust automatically.
• Not testing the output. A valid expression is not necessarily the one you wanted. Preview the next run times before you deploy anything that triggers payments or emails.

Copy-paste snippets for popular runtimes

Cron strings are portable, but each runtime has its own way of declaring them. Here is the same “every 5 minutes” schedule in five places:

# cron  (Linux / macOS / BSD)
*/5 * * * * /usr/bin/your-job.sh

# Python (croniter / apscheduler)
schedule.every(5).minutes.do(your_job)

# Node.js (node-cron)
cron.schedule('*/5 * * * *', () => yourJob());

# GitHub Actions
on:
  schedule:
    - cron: '*/5 * * * *'

# n8n
"cronExpression": "*/5 * * * *"

Each schedule page on this site includes the exact snippet syntax for your runtime — open one from the list above and copy it in one click.

Frequently asked questions