Read any cron expression in plain language and see exactly when it will next run.
Five fields: minute, hour, day of month, month, day of week. Shortcuts such as @daily also work.
Every 15 minutes
| */15 | Minute |
| * | Hour |
| * | Day of month |
| * | Month |
| * | Day of week |
This expression never matches a real date.
Times are shown in your device's timezone. Servers usually run cron in UTC, so check before relying on these.
Five fields separated by spaces, or one of the shortcuts such as @daily or @hourly. The presets below the box cover the schedules people set most often.
The tool turns the expression into a sentence, so you can check it says what you meant before it goes into a crontab or a pipeline definition.
The next five run times are calculated from your clock. This is the real test: a schedule that reads correctly but fires at the wrong time shows up immediately here.
In order: minute, hour, day of month, month and day of week. An asterisk means every value, and cron runs the job when all of the fields match the current time.
It is a step. Written as */15 in the minute field it means every fifteenth minute, so at 0, 15, 30 and 45. Written as 10-20/2 it steps by two within that range.
This is the trap. When both are restricted, cron runs the job if either matches, not both. So 0 0 1 * mon fires on the first of the month and on every Monday.
Both. Most implementations accept 0 and 7 for Sunday, and this tool normalises 7 to 0 so the description and the run times are consistent either way.
Your device's timezone, because that is what the browser knows. Servers usually run cron in UTC, so confirm the server's timezone before trusting a schedule that matters.
Characters such as L, W and the hash are extensions supported by Quartz and some other schedulers, but not by standard cron. They are rejected rather than being silently ignored, which would give you wrong run times.
Yes. Both use standard five field cron, and both run in UTC, so read the run times with that in mind.
Yes, completely free with no sign-up.
Convert Unix timestamps to readable dates and back, in seconds or milliseconds, with ISO, UTC and local output.
Open ToolEvery HTTP status code with what it means and when to send it, searchable by number, phrase or description.
Open ToolOnline UUID v4 and v7 generator, free. Bulk generation with uppercase and no-dash formatting. Cryptographically secure and generated in your browser.
Open Tool