Cron library
Cron expression for every minute
* * * * *
At every minute every day.
Runs 100% in your browser. Nothing you paste is uploaded, stored, or sent to a server.
Or build one
Meaning
Next 10 run times
How to use
- Read the expression and the English meaning above. Confirm they match the job you have in mind.
- Use the time zone dropdown to preview the next 10 fire times in UTC or a US/EU city.
- Copy the expression into crontab, GitHub Actions (`on.schedule.cron`), or your job runner.
- If you need a nearby interval, browse the related schedules at the bottom of this page.
The five-star expression is the densest schedule Unix cron can express: every minute of every hour, every day. It is useful for a health check or a queue poller, and expensive if the job does any real work.
If you inherited * * * * * and the box is hot, start here. Confirm that you really meant “every minute” and not “at minute zero,” which is 0 * * * *.
When this schedule is a good fit
Typical uses: Liveness probes that must notice a dead worker in under a minute; Draining a local outbox table on a single host; Temporary debugging — then switch back to a coarser step.
Cron fields are zone-naive. The daemon’s TZ — or the TZ= line above the job — decides what “midnight” or “9am” means. Preview both UTC and the office zone before you ship.
FAQ
How many times does this run per day?
1,440 times, once per minute. On a fleet, multiply by the number of hosts that each have their own crontab.
Is this the same as a 60-second sleep loop?
No. Cron starts a new process on the wall clock. If a run lasts 90 seconds you can overlap jobs unless you add locking (flock, systemd, or a job runner).
Does this page upload my crontab?
No. The explainer and the next-run list run in your browser. The expression on this page is a public example.