Cron: Every minute (* * * * *)
Plain-English meaning, run times, and visual editor for the * * * * * cron schedule. No sign-up required.
What does * * * * * mean?
The cron expression * * * * * translates to “Every minute”. It is one of the most commonly used schedules (every minute).
Every field is a wildcard, so there is nothing to constrain the schedule - the job fires at the top of every single minute, 60 times an hour, 1,440 times a day. This is the most frequent standard cron schedule (you cannot go below one minute without a different scheduler). Use it for near-real-time polling, health checks or queue draining, but be careful: if one run can take longer than a minute, overlapping executions can pile up unless your job guards against it.
Use the builder above to tweak this expression and instantly see how the description and the next run times change.
Example runs from Jan 1, 2026 (UTC)
- Thu Jan 01 2026, 00:01 UTC
- Thu Jan 01 2026, 00:02 UTC
- Thu Jan 01 2026, 00:03 UTC
- Thu Jan 01 2026, 00:04 UTC
- Thu Jan 01 2026, 00:05 UTC
Frequently Asked Questions
About cron expressions and this generator.
The cron expression "* * * * *" runs a job every single minute of every hour, day, month, and day of week.
Running a task every minute puts a constant load on your server. If the job takes longer than 60 seconds to finish, processes can stack up, leading to high CPU usage or memory leaks.
Related cron expressions
From the blog
Cron Expressions Explained: A 5-Field Cheatsheet
A technical reference for POSIX cron expressions: the 5-field syntax, step-value math traps, and the Day-of-Month vs. Day-of-Week OR-behavior that catches everyone.
Read →cronCron Syntax Across Schedulers: Unix vs. Quartz vs. AWS EventBridge
Why your cron expression failed in the cloud. A technical breakdown of the differences between POSIX, Java Quartz, AWS, and Node.js schedulers.
Read →cronWhy Your Cron Job Failed: Debugging Timezones, PATH Variables, and Overlaps
A practical guide to diagnosing standard runtime failure modes in cron daemons. Learn why your script works in the terminal but fails silently in the background.
Read →