Cron expression decoder
Read a five-field crontab expression and preview its next 10 matching times. Your input stays in your browser.
At 09:00; on Mon, Tue, Wed, Thu, Fri.
| Field | Expression | Matching values |
|---|---|---|
| Minute | 0 | 0 |
| Hour | 9 | 9 |
| Day of month | * | Any |
| Month | * | Any |
| Day of week | 1-5 | Mon, Tue, Wed, Thu, Fri |
Next run times
Times below use the selected zone. Your scheduler must use the same zone.
- 2026-11-23 09:00 UTC
- 2026-11-24 09:00 UTC
- 2026-11-25 09:00 UTC
- 2026-11-26 09:00 UTC
- 2026-11-27 09:00 UTC
- 2026-11-30 09:00 UTC
- 2026-12-01 09:00 UTC
- 2026-12-02 09:00 UTC
- 2026-12-03 09:00 UTC
- 2026-12-04 09:00 UTC
Convert a JST schedule to UTC
This conversion always treats the expression above as Japan Standard Time, regardless of the preview setting. Hours before 09:00 JST fall on the previous UTC day, so weekdays shift too. Some schedules need two expressions.
0 0 * * 1-5
Automatic conversion excludes some schedules with calendar-date restrictions or wildcard steps in the day-of-week field when they cross into the previous UTC day. JST has no daylight saving time.
Common cron expressions
Select an example to try it. Times are in the zone selected above.
| Expression | Meaning |
|---|---|
| Every 5 minutes | |
| Every hour | |
| Daily at midnight | |
| Weekdays at 09:00 | |
| Fridays at 18:30 | |
| First day of each month | |
| Weekdays, hourly from 09:00 to 18:00 | |
| Every 10 minutes from 09:00 through 17:50, Monday–Friday | |
| First day of each quarter | |
| Sundays at 03:00 | |
| Weekends at midnight | |
| January 1 at midnight |
Common mistakes
- Day of month and day of week use OR when both are restricted.
- A step resets within its field:
*/7in the minute field matches 00, 07, …, 56, then 00 of the next hour. It is not a continuous seven-minute interval. - Month and weekday names such as
JANandMON-FRIare accepted. Macro aliases such as@dailywork here, but support varies by scheduler. - In a crontab command, escape percent signs: write
date +\%Y\%m\%d. Cron jobs may have a shorter PATH than your interactive shell; use absolute paths or set PATH explicitly. - A valid expression may never run, for example February 30. If no matching time is found within five years, the preview says so.
Frequently asked questions
What are the five cron fields?
Minute (0–59), hour (0–23), day of month (1–31), month (1–12), and day of week (0–7; 0 and 7 are Sunday). Separate fields with spaces. There is no seconds field.
What happens when both day fields are restricted?
This tool uses Vixie-style OR semantics. 0 0 13 * 5 runs on the 13th of each month and every Friday, not just Friday the 13th. With a plain * in either day field, the other field controls the matching days. If a day field starts with a wildcard step such as */2, both day fields must match.
How do UTC and Japan Standard Time differ?
JST is UTC+9 year-round. 09:00 JST is 00:00 UTC on the same day. 08:00 Monday JST is 23:00 Sunday UTC. Select the zone in which your scheduler interprets the expression.
Does this support Quartz or EventBridge expressions?
The tool reads five-field crontab expressions. It does not interpret a seconds or year field, or Quartz L, W and # extensions. EventBridge uses a different cron dialect; adapt and check the syntax before using it there.
Is my expression uploaded?
No. The tool processes the expression locally in your browser. It does not send your input to a server.
Why can actual runs differ from the preview?
The preview shows matching times in UTC or fixed-offset JST, up to five years ahead. It does not model scheduler delays, missed runs, server downtime or daylight saving time in other zones.