The cron expression to run a job every minute is * * * * *, the shortest interval standard cron supports. See the next run times in your timezone.
Paste an expression or choose a starting schedule below.
Select a field to edit it.
Schedule summary
Build a schedule
Starts at minute 0 and repeats within each hour.
Valid changes update the expression above immediately.
Upcoming runs
The next 50 runs, shown in the schedule timezone and your local time.
About * * * * *
* * * * * matches every minute of every hour, so the job starts 60 times an hour — the finest granularity standard cron offers. Anything faster needs two lines with sleep, or a scheduler with a seconds field; the FAQ on the home page covers both.
Cron reads the five fields as minute hour day month weekday. For this schedule that breaks down as:
| Field | Position | Matches |
|---|---|---|
* | minute | every minute |
* | hour | every hour |
* | day of month | every day |
* | month | every month |
* | day of week | every day of the week |
New to cron? Read the syntax reference or the FAQ.
Use it in crontab or GitHub Actions
The snippets below use UTC. The crontab timezone setting requires a compatible daemon such as Cronie. GitHub Actions defaults to UTC and accepts a timezone on each schedule. For other timezones, Kubernetes, EventBridge Scheduler, or Vercel, use the export menu in the calculator above.
crontab
# Every minute, every hour, every day # CRON_TZ requires a cron implementation that supports it, such as Cronie. CRON_TZ=UTC * * * * * /path/to/command
GitHub Actions workflow
GitHub Actions requires at least five minutes between scheduled runs, including across hour and day boundaries.