Free Cron Expression Generator — Linux Cron Job Builder Online

Generate cron expressions easily with visual interface

Custom Configuration

* * * * *

Runs every minute

Next 5 Scheduled Runs

May 18, 2026, 03:24 AM
May 18, 2026, 03:25 AM
May 18, 2026, 03:26 AM
May 18, 2026, 03:27 AM
May 18, 2026, 03:28 AM

How to Use the Cron Expression Generator

A cron expression is a 5-field string that defines when a scheduled task runs on Linux, Unix, or any cron-compatible system. This free cron job builder lets you build and validate cron expressions visually — no memorizing syntax required. Use the quick presets for common schedules (every hour, daily at midnight, weekly on Monday) or configure each field manually. The tool shows the next 5 scheduled run times so you can verify your expression before deploying it. Cron expressions are used everywhere: Linux crontab, GitHub Actions workflows, AWS EventBridge, Kubernetes CronJobs, Laravel task scheduler, and Django-celery-beat. Once you have your expression, copy it with one click.

* * * * *
│ │ │ │ │
│ │ │ │ └─── Day of Week (0-6, 0=Sunday)
│ │ │ └───── Month (1-12)
│ │ └─────── Day of Month (1-31)
│ └───────── Hour (0-23)
└─────────── Minute (0-59)
        

Special Characters

  • * - Any value — matches all (wildcard)
  • , - List — comma-separated values (e.g., 1,3,5)
  • - - Range — from–to inclusive (e.g., 1-5)
  • / - Step — every N units (e.g., */5 = every 5 minutes)

Common Cron Expression Examples

  • 0 * * * * - Every hour at minute 0
  • 0 0 * * * - Every day at midnight (00:00)
  • 0 9 * * 1 - Every Monday at 9 AM
  • */15 * * * * - Every 15 minutes
  • 0 0 1 * * - First day of every month at midnight

Frequently Asked Questions

What is a cron expression?

A cron expression is a string of five fields (minute, hour, day of month, month, day of week) that defines when a scheduled task should run. For example, '0 9 * * 1-5' means 'at 9:00 AM every weekday'. Cron expressions are used in Unix/Linux cron jobs, CI/CD pipelines, cloud schedulers (AWS EventBridge, GCP Cloud Scheduler), and application frameworks.

Where can I use cron expressions?

Cron expressions are supported by Linux/Unix cron, GitHub Actions (on.schedule), GitLab CI, Jenkins, AWS EventBridge Scheduler, GCP Cloud Scheduler, Azure Logic Apps, Kubernetes CronJobs, Laravel task scheduler, Django-celery-beat, and most other job scheduling systems. The exact syntax may vary slightly between platforms — always validate your expression in the specific environment you're targeting.

How do I test my cron expression?

Use our Cron Generator above to instantly see the next scheduled run times for any expression. You can also run 'crontab -l' to list active cron jobs and 'crontab -e' to edit them on Linux. For testing in CI/CD, trigger a manual pipeline run. Always verify in a staging environment before deploying scheduled tasks to production.

How do I run a cron job every 5 minutes?

Use the expression '*/5 * * * *' to run a task every 5 minutes. The '*/5' in the minute field means 'every 5th minute' (0, 5, 10, 15...). Similarly, '*/10 * * * *' runs every 10 minutes, '*/15 * * * *' every 15 minutes, and '0 */2 * * *' every 2 hours on the hour.

What does '* * * * *' (five asterisks) mean?

'* * * * *' means 'every minute of every hour of every day' — it's the most frequent possible cron schedule. Each asterisk is a wildcard: minute (0–59), hour (0–23), day of month (1–31), month (1–12), day of week (0–7). Use this pattern for testing, but avoid it in production for heavy tasks — it runs 1,440 times per day.

What time zone do cron jobs use?

By default, Linux cron uses the server's local time zone. On managed cloud schedulers like AWS EventBridge or GCP Cloud Scheduler, you can explicitly configure the time zone. This is critical for business-hour scheduling — a job set to run at '9 * * *' on a UTC server runs at 9 AM UTC, not 9 AM in your local time. Always specify time zones explicitly when running cron jobs across different regions.

How do I schedule a cron job for the first day of each month?

Use '0 0 1 * *' to run at midnight on the 1st of every month, or '0 9 1 * *' to run at 9 AM on the 1st. The third field (day of month) accepts values 1–31. For the last day of the month, most cron implementations don't support 'L' notation — you'd need a script that checks if tomorrow is the 1st.

Can cron run multiple commands at once?

Yes. In a crontab entry, separate commands with && (run second only if first succeeds), || (run second only if first fails), or ; (run both regardless). For complex jobs, it's best practice to call a shell script instead: * * * * * /path/to/script.sh — this keeps the crontab clean and allows the script to include logging, error handling, and locking.

Want Automated Monitoring?

Get 24/7 monitoring with instant alerts when issues are detected.

Start Free Trial

Related Tools