Cron Expression Parser & Run Time Prediction
ConvertEverything runs locally in your browser — nothing is uploaded
Turn something like “*/15 9-17 * * 1-5” into plain English: each field is explained in turn, a one-line summary follows, and the next few run times are listed — together with the previous ones. Times are found by jumping to the next possible match rather than testing every minute, so even a schedule pinned to 29 February resolves instantly. The backward search is a separate implementation, not the forward results read in reverse, because cron is asymmetric along the time axis (February 29, `*/5` minutes and weekly schedules all resolve differently going back). Each listed time also carries a relative note such as “in 2 hours 13 minutes” or “3 days ago”. An expression that can never fire — 31 February, say — is reported with the reason instead of leaving the page spinning.
Features
- All the usual syntax: star, single value, a-b ranges, a,b,c lists and /n steps on stars or ranges
- Month and weekday names (JAN-DEC, SUN-SAT) are accepted
- Per-field explanation plus a one-line summary such as "every 15 minutes of 09:00 to 17:00 on Monday to Friday"
- Lists the next 1-50 run times with the weekday for each
- Also lists the previous run times — the backward search steps down from the largest unit, handling February 29, `*/5` minutes and weekly schedules correctly
- A relative note on each time (“in 2 hours 13 minutes” / “3 days ago”) in the interface language
- A base instant can be set (blank = now) for retrospective lookups
- Applies the classic day-of-month / day-of-week OR rule (Vixie cron semantics)
- Understands the @daily, @hourly, @weekly, @monthly and @yearly macros
- Impossible schedules are rejected up front, naming the fields that cannot line up
- Run times can be shown in local time or UTC, since server crons usually run in UTC
How to use
- Paste a 5-field cron expression into the box
- Choose the description language, how many runs to list, and the timezone; toggle the previous runs and set a base instant if needed
- Click Run (or press Ctrl/⌘ + Enter)
- Copy the result, or fix the expression using the breakdown
FAQ
- Why was my 6-field expression rejected?
- A leading seconds field is the Quartz and Spring convention; classic cron has five fields. Reading a 6-field expression as 5 fields shifts every field by one, so the run times you get back are for a completely different schedule — this tool refuses it and asks you to drop the seconds field rather than guess.
- What happens when both day-of-month and day-of-week are set?
- Classic (Vixie) cron treats them as an OR: “0 0 1 * 1” fires on the 1st of the month, or on any Monday. Only when one of the two is a star does it become an AND. Many implementations get this wrong; this tool follows Vixie.
- Which timezone are the run times in?
- Either, and it defaults to local time. Containers and servers usually run cron in UTC while local time is easier to sanity-check by hand, so both are offered. Switching shifts every listed time — and the weekday shown along with it.
- Why does it say the expression can never fire?
- For example “0 0 31 2 *”: February has no 31st in any year, so it never runs. The tool checks whether the day and month combinations exist at all. On top of that there is a four-year search limit (leap-year gaps can reach eight years); past the limit it reports that nothing was found instead of searching forever.
- How are the previous run times computed? Why not just reverse the next ones?
- Because cron is asymmetric along the time axis, so the forward jump logic fails when reversed. Going forward, a mismatched month jumps to the 1st of the next month; going backward it must jump to the last day of the previous month at 23:59. `*/5` minutes must step back to a minute divisible by 5, and `0 0 * * 0` must step back to the previous Sunday. Those land in different places in each direction, so the backward search walks down from the largest unit (month → day → hour → minute) as a separate implementation symmetric to the forward one. The window is four years the other way too: the previous `0 0 29 2 *` reaches back to the last real 29 February, and says so plainly if there is none within four years.
- What happens to run times on the daylight-saving changeover days?
- They follow the real rules of the selected zone (local time means this machine’s zone). ⚠️ On the day DST starts, some wall-clock times do not exist (02:30 on 2026-03-08 in New York, for instance), so a schedule such as `30 2 * * *` skips that day rather than being nudged to 01:30 or 03:30 — a nudged time looks normal but is an hour out. On the day DST ends, some times happen twice (01:30 on 2026-11-01 in New York) and both count as valid run times. None of this is extra work here: the calendar arithmetic is delegated to the platform’s time-zone database (the local Date methods). Implementations that add and subtract offsets by hand get these days wrong by an hour — and only on those days.
Related tools
Timestamp Converter
ConvertConvert Unix timestamps into dates and back, telling seconds, milliseconds, microseconds and nanoseconds apart, with Windows FILETIME and decimals.
Date Calculator
ConvertCount the days, weeks or months between two dates, or shift a date by any of those. Dates can be picked from a calendar or pasted in — nothing is uploaded.
Number Base Converter
ConvertConvert numbers between binary, octal, decimal, hex, base 36 and base 64, with long IDs converted digit for digit. Runs in your browser.
Color Converter
ConvertConvert between HEX, RGB, HSL, HWB, CMYK, Lab and OKLCH, with colour temperature, inverse, complement, nearest ANSI colour and WCAG contrast.
CSS Units
ConvertConvert a CSS length between px, rem, em, vw, vh and more. Root font size and viewport are adjustable, and each row says what it assumed.
Unit Converter
ConvertConvert between 26 categories of units — length, weight, temperature, energy, pressure, flow, force, density and more. All in your browser.