Build a cron schedule from menus, read it in plain English, see the next runs
Runs in your browser. Nothing you type is sent anywhere. Updated on 24 Oct 2026.A cron expression has 5 fields and almost nobody remembers the order. Build one from menus instead, read it back in plain English, and see the next few times it would actually run before committing it to a server. Nothing is sent anywhere.
Click a preset such as "Every 5 minutes" or "Weekdays at 9:00", or choose an option under Run.
Set the Hour, Minute, days or interval that appear for that choice; the Cron expression updates.
Read the plain-English sentence and the Next 10 runs in the Time zone you pick.
Click Copy expression.
This cron expression builder writes a schedule for you from plain choices, such as every 15 minutes, daily at 07:30 or on the 1st of every month, and reads any expression back as a sentence like "At 09:00 AM, Monday through Friday". Below it you see the next ten times the job will run.
Use it when you set up a crontab entry for a backup, a Kubernetes CronJob for a report, or a GitHub Actions schedule for a nightly build. It is just as useful in reverse: paste the expression from an old server and find out whether "0 */6 * * *" really means every six hours starting at midnight.
The builder speaks standard 5-field cron: minute, hour, day of month, month and day of week, with ranges (1-5), lists (1,15), steps (*/10), month and day names (JAN, MON) and shortcuts such as @daily. Quartz and Spring expressions with a seconds field, and the L, W and # extensions, are rejected with an explanation, because crontab would reject them too. When both day fields are set, cron runs on either one, and the preview follows that rule.
Run times are shown in the time zone you choose, India Standard Time by default. Most servers and CI runners use UTC, so pick UTC to see exactly when a server will fire, then compare. Everything is worked out in your browser; nothing is sent anywhere. Related tools: Unix Timestamp Converter, Regex Tester.
Use */5 * * * *. The first field is the minute, and */5 means every fifth minute starting at 0, so the job runs at :00, :05, :10 and so on, every hour of every day.
In order: minute (0-59), hour (0-23), day of month (1-31), month (1-12 or JAN-DEC) and day of week (0-7 or SUN-SAT, where 0 and 7 are both Sunday). An asterisk means every value.
Usually because the server runs in UTC while you are thinking in local time. 0 9 * * * on a UTC server fires at 14:30 in India. Choose UTC in the time zone menu to see the times the server will use.
No. It builds standard 5-field cron used by crontab, Kubernetes and GitHub Actions. Expressions with a seconds field or the L, W, # and ? extensions are flagged with an explanation of how to convert them.
Cron runs the job when either one matches, not only when both do. For example 0 0 13 * 5 runs on every 13th and on every Friday. The list of next run times shows this.
Yes, with no signup and no limit on how many schedules you build or check. Everything runs in your browser, so a cron line copied from a private server never reaches us. The next run times are worked out on your device from the time zone you choose.
Still stuck? Ask about Cron Expression Builder and anybody who knows can answer. No account needed.
Same job, other tools: Tailwind Flexbox Generator – Arrange a flex layout visually and copy the Tailwind classes for the parent and each child · Meta Description Generator – Write a description that fits the snippet instead of being cut off.
Also works as: Cron Schedule Builder.
In the collection Developer Converters.