Cron Expression Parser & Explainer
Private by design — runs entirely in your browser
Parse a cron expression and see the next ten runs in human form. Toova explains the schedule in plain English, surfaces common mistakes, and runs entirely in your browser — no upload, no signup, no server lookup.
What cron expressions mean
A cron expression is a compact schedule like 0 */6 * * * — minute, hour, day-of-month, month, day-of-week. The syntax is dense and easy to get wrong, especially around step values (*/15), ranges (1-5), and the day-of-month versus day-of-week interaction. Toova parses any standard cron expression and explains it in clear English, so you can verify the schedule before deploying it.
Next runs and timezone awareness
After parsing, Toova lists the next ten scheduled runs in your local timezone and in UTC. That makes it obvious when a job will fire — including across daylight saving transitions, which trip up cron schedules every spring and fall. Switch the timezone to match wherever the job actually runs (your server, your CI, your scheduler) to predict exactly when the next execution will happen.
Browser-only parsing
Toova parses the cron expression and computes future runs entirely in your browser. The expression you paste never leaves the page, and there is no logging of the content. That matters when the cron is part of an internal scheduling system or contains hints about your job names. The page works offline after first load.
Frequently Asked Questions
- Which cron syntax does this support?
- Standard 5-field cron (minute, hour, day-of-month, month, day-of-week) and the 6-field variant with seconds. Step values (*/N), ranges (1-5), and lists (1,3,5) are all supported. The non-standard quartz extensions (L, W, ?) are recognized too.
- Why are my day-of-week and day-of-month both set?
- When both are specified, most cron implementations OR them together — the job runs when either matches. That is rarely what people expect. Toova flags this case so you can rewrite the expression if the intent was AND.
- How does Toova handle daylight saving time?
- Future runs are computed in the timezone you pick. Schedules that fall in the gap (2:30 AM on spring forward) are handled per the timezone's rules — typically the run is skipped or shifted.
- Can I parse human-readable schedules?
- This tool parses cron expressions in the canonical form. For human descriptions like "every 15 minutes", build the expression yourself (*/15 * * * *) and let Toova confirm the schedule by listing the next runs.
- Is my expression sent to any server?
- No. Parsing happens entirely in your browser.