Cron expression generator
Type or click together a cron expression. You see right away when the job runs, what to watch out for and how to write it in other schedulers.
The tool could not be loaded. Check your connection and reload the page.
Next runs
Cheat sheet
*every value*/15every 15th value1-5range from 1 to 51,15values 1 and 15MON-FRIMonday to Friday@dailyshortcut for 0 0 * * *
Syntax for your scheduler
GitHub Actions use UTC, run at most every 5 minutes and may be delayed under load.
The timeZone field works since Kubernetes 1.27.
Verify with systemd-analyze calendar.
How it works
The expression is parsed by the rules of classic cron (Vixie cron, cronie) used on Debian, Ubuntu and RHEL: five fields, month and weekday names, ranges, lists and steps. Sunday can be 0 or 7.
One trap: when you restrict both the day of month and the day of week, cron runs the job when EITHER matches. "0 0 13 * 5" is not Friday the 13th, it is every 13th plus every Friday.
Next runs are computed in the selected time zone, including daylight saving changes. A time that is skipped or happens twice when the clocks change is marked, because cron implementations handle it differently.
GitHub Actions always use UTC and may start a job several minutes late. Kubernetes supports its own time zone through timeZone since version 1.27.
When it helps
- You set up a scheduler and want to be sure "every weekday at 8:00" is really what you wrote.
- You read someone else's crontab and need to understand quickly what runs when.
- You move jobs between crontab, the Laravel scheduler, GitHub Actions and Kubernetes.
- You debug nightly backups around the daylight saving change.
Frequently asked questions
// 01 How do I write "every 5 minutes"?
*/5 * * * *. A star with a slash is a step: */5 in the minute field means 0, 5, 10 up to 55. Likewise */2 in the hour field means every second hour.
// 02 Why doesn't "0 8 * * *" run at 8:00 my time?
Cron uses the system time zone (or the CRON_TZ variable). A server set to UTC runs the job at 8:00 UTC. In Laravel you set the zone with ->timezone().
// 03 What happens to a job at 2:30 at night when the clocks change?
When daylight saving starts, 2:00 to 2:59 does not exist; when it ends, that hour happens twice. cronie on Debian and Ubuntu runs fixed-time jobs from the skipped hour right after the change and runs them once in the repeated hour; other schedulers differ. Avoid scheduling critical jobs between 2:00 and 3:00.
// 04 Does it support seconds?
No. Classic cron has five fields and the smallest step is one minute. Six-field expressions with seconds are used by Quartz or Spring, and the tool tells you so.
You may also need
Did this save you time?
The tools and simulations are free, ad-free and need no sign-up. If they helped you, you can send a contribution for coffee and new tools.
Donate via PayPalWhat happens to your data
Privacy policy (in Czech)- The tools process your input with JavaScript on your device. Nothing you paste is sent to the server, stored or logged.
- The exception is the SPF/DKIM/DMARC check: it asks public DNS (Cloudflare, Google as a fallback) directly from your browser. Only the domain name is sent.
- Analytics (only if you accept analytics cookies) records anonymous events such as "a tool was opened". Never your input or results.
- No ads or advertising scripts run on the tool and simulation pages.
Need a hand?
I build and maintain web applications in Laravel and PHP. If something on these pages is giving you trouble in a project, get in touch.
Get in touch