Output will appear here
Click in the output to select all text
Output will appear here
Click in the output to select all text
Translate complex cron expressions into clear human-readable sentences.
Convert Unix epoch timestamps (seconds & ms) to UTC, ISO 8601, and local dates.
Convert time between major world timezones (UTC, EST, PST, GMT, IST, JST, CET).
Convert any date and time into Unix timestamps in seconds and milliseconds.
Convert numeric Unix timestamps into multiple human-readable date formats.
This cron expression tester parses standard 5-field cron syntax and calculates the upcoming execution times, so you can confirm a schedule is correct before deploying it to a real crontab or scheduled job. It's a must-have for developers and sysadmins who've ever second-guessed whether '0 */2 * * *' really means every two hours, or accidentally scheduled a job to run every minute instead of every day. Rather than waiting to see if a job fires at the wrong time in production, this cron parser shows you the next several run times immediately, based on the exact expression you type. It supports standard minute, hour, day-of-month, month, and day-of-week fields, along with common special characters like asterisks, ranges, steps, and lists. As with all tools here, parsing happens entirely client-side - your schedule expression is never sent anywhere. Type a cron expression below to see it validated and its next run times calculated instantly.
In order, they are minute (0-59), hour (0-23), day of month (1-31), month (1-12), and day of week (0-6, where 0 is Sunday).
It means 'run at minute 0 of every 2nd hour', so the job fires at 00:00, 02:00, 04:00, and so on throughout the day.
Yes, but most cron implementations treat these fields as OR'd together rather than AND'd when both are restricted from the wildcard.
An asterisk means 'every value' for that field, e.g. an asterisk in the hour field means the job can run in any hour.
Use '0 9 * * 1-5', which runs at 9:00 AM on Monday through Friday.
Results are shown in your browser's local time zone by default, matching how most cron daemons interpret the system's local time unless configured otherwise.
This tool focuses on the standard 5-field format used by Unix cron; some schedulers like Quartz add a seconds field, which isn't the default here.