Cron Expression Translator
A cron expression translator reads a crontab line the way a scheduler reads it, then says the same thing in plain English. It shows what each of the five fields means, flags the cases where standard cron surprises people, and lists the next run times in your own timezone.
What a cron expression says
Cron is the scheduler built into Linux, macOS, and most Unix-like systems. You write one line per job in a crontab file, and the daemon wakes up, checks which lines are due, and runs them. The schedule itself is five space-separated fields. The command runs when all five fields match the current time.
The order never changes. Minute first, then hour, then day of month, then month, then day of week. Getting the order wrong is the single most common mistake, and it fails quietly: the expression is valid, it just fires at a time you did not expect.
Each field accepts several forms. An asterisk means every possible value. A number is a single value. A range such as 1-5 covers everything in between. A comma separated list such as 0,30,45 covers several values. A step such as */15 takes every fifteenth value of the field. Month names JAN through DEC and day names SUN through SAT are accepted too, in either case, so JAN, jan, and Jan all mean January.
The five fields in order
The minute field runs from 0 to 59 and the hour field from 0 to 23, both starting at zero rather than one. The day of month field runs from 1 to 31, the month field from 1 to 12, and the day of week field from 0 to 7 where both 0 and 7 mean Sunday.
Day of week is the only field where two numbers mean the same thing, and that trips people up when they read a schedule somebody else wrote. Sunday is 0 or 7, Monday is 1, and Saturday is 6.
How to use the translator
Paste the expression into the input field. The translation updates as you type, so you can edit one field at a time and watch the sentence change.
The plain English line is the quick read. Under it, the field breakdown shows what each field contributes, and next to that you get the next ten run times as they will happen in your browser's timezone. Copy the sentence if you need to explain the schedule to someone, or copy the run-time list if you are checking a deployment window.
The preset buttons fill in the schedules people ask about most often. They are a starting point, so edit them into whatever your job actually needs.
Worked examples
These are the same outputs the tool produces. Read the input, then read the sentence, then check the run times against what you expected.
Every five minutes
The step in the minute field is the whole schedule. The other four fields are unrestricted, so the job runs on every day of every month.
Input: */5 * * * * Result: Every 5 minutes, every day. Runs: 10:10, 10:15, 10:20, 10:25, 10:30
Weekdays at nine in the morning
Day of week set to 1-5 covers Monday through Friday. Because the day of month field is left as an asterisk, it does not narrow anything down, so the job runs on every weekday.
Input: 0 9 * * 1-5 Result: At 09:00, from Monday through Friday. Runs: Thu 09:00, Fri 09:00, Mon 09:00, Tue 09:00, Wed 09:00
The first of every month
The day of month field is set to 1 and day of week is left open. That combination runs once a month, on the first, at midnight.
Input: 0 0 1 * * Result: At 00:00, on day 1 of the month. Runs: Sat 1 Jun 00:00, Mon 1 Jul 00:00, Thu 1 Aug 00:00
The rule that catches everyone
When you restrict both the day of month field and the day of week field, standard cron runs the job when either one matches. Most people expect an AND, where the job runs only when both match on the same day. Vixie cron, the implementation that Linux and macOS still ship, uses OR.
The expression below looks like it means midnight on the first of the month, and on Mondays. That is exactly what it does. It fires on every Monday, and it also fires on the first of the month even when that falls on a Wednesday.
Input: 0 0 1 * 1 Result: At 00:00, on day 1 of the month, on Monday. Warning: both day fields are restricted, so the job runs when either one matches. Runs: Mon 20 May, Mon 27 May, Sat 1 Jun, Mon 3 Jun, Mon 10 Jun
Macros and short forms
Several schedules have a shorthand name. @hourly runs at minute 0 of every hour. @daily and @midnight both run at 00:00 every day. @weekly runs on Sunday at midnight. @monthly runs on the 1st at midnight, and @yearly and @annually run on 1 January at midnight.
@reboot is different from all of them. It is not a schedule. The command runs once each time the system starts, so there is no repeating run time to calculate and the translator lists none.
Dialects that use a different format
This translator handles the standard five-field format only. Three other formats show up often enough to be worth naming.
Quartz, the scheduler inside Java EE application servers, adds a seconds field at the front and expects six or seven fields. It also uses a question mark to mean no specific value in the day fields, and it rejects the names in favour of numbers. A Quartz expression such as 0 0 12 * * ? is not a valid standard cron expression, and this tool will tell you it has the wrong number of fields.
AWS EventBridge rules use a six field cron format with the seconds field first, the same way Quartz does, and they do not support the macros. EventBridge also runs in UTC, so a rule that fires at 09:00 UTC fires at a different wall clock time for each region that reads it.
systemd timers use calendar event syntax instead, such as OnCalendar=Mon *-*-* 09:00:00. The idea is similar but the spelling is not compatible with crontab, so it needs a separate parser.
Tips for a schedule you can trust
Write the schedule in a form a colleague can read without decoding it. Named months and days, like 0 4 * JAN-MAR MON, are easier to review than 0 4 * 1-3 1.
Check the timezone before you trust the run list. Cron on a server uses the system timezone of that server, which is often UTC and rarely the timezone of the person who wrote the crontab. The translator shows times in your browser's timezone, so compare the two deliberately.
Think about daylight saving time. When clocks jump forward, a wall clock time such as 02:30 may not exist on that day, and the job is skipped. When clocks fall back, a job scheduled in the repeated hour can run twice. Scheduling outside the 01:00 to 03:00 window avoids both cases in most implementations.
Give the job a short interval only when it needs one. A job that runs every minute writes to disk and logs 1,440 times a day. If five minutes is enough, use */5.
Test before you rely on it. Install the expression in a scratch crontab, or use a crontab simulator, and check that the times match what you expected before the job starts touching anything real.
Edge cases and troubleshooting
A schedule that never fires is usually a day field problem. Check whether day of month and day of week are both restricted, because that flips the matching rule to OR and can fire the job far more often than you expected.
A job that fires an hour late or an hour early is almost always a timezone difference between your laptop and the server.
A job that fires twice at the same wall clock time is usually the daylight saving fall-back case, or a second crontab entry for the same command.
If the translator rejects an expression that works on your server, compare the field count first. Six or seven fields means a Quartz-style or EventBridge-style schedule rather than standard cron. If a field value is rejected, check for a stray character such as a full-width dash or a space inside the field, and remember that day of week only goes up to 7.
This tool reads the expression and does the maths in your browser. It does not connect to your server, read your crontab, or run anything.
Explore more developer tools on Tolz.me.