Cron Expression Editor & Parser
Paste a cron expression and get a plain-language description and the next five run times. It supports the standard cron expression with five fields (minute, hour, day of month, month, day of week), with * (all), comma (list), hyphen (range) and slash (step), and English names for months (jan to dec) and weekdays (sun to sat). When both day of month and day of week are set, it runs on days matching either one (OR), as in standard cron. Next run times are shown in your browser's time zone, so take the offset into account when comparing with a server running in UTC or with a GitHub Actions schedule. A seconds field and the Quartz and AWS EventBridge symbols (?, L, W, #) are not supported. The description is shown in Japanese or English. Everything runs in your browser and your expression is not sent anywhere.
Also accepts @hourly, @daily, @weekly, @monthly and @yearly.
Human-readable description
Field labels
Next execution schedules
No runs in the next 5 years (for example February 30).
When both day-of-month and weekday are set, the job runs when either matches (standard cron).
Shape of the schedule (7 days from today)
How many times the expression runs, by hour of the day and by weekday, in the time zone above. The list of next runs shows only the first few; this shows the whole pattern.
Runs per hour of the day
Runs per weekday
Quartz / Spring cron (with seconds)
Check cron expressions used by Quartz (Java schedulers) and Spring @Scheduled: 6 or 7 fields with seconds, ?, L, W, # and an optional year. It finds mistakes, explains each field, and lists the next run times. Quartz counts Sunday as 1; Spring counts Sunday as 0 or 7 and requires both day fields to match.
Fields
Next runs
No run was found within the next 8 years.
GuideHow to use & features
- Type a Cron expression to update the human description and next run list instantly.
- Inspect the minute/hour/day/month/weekday parts to confirm each field’s meaning.
- Invalid input triggers an error message so you can fix syntax quickly.
- The tool expects the standard 5-field crontab format.
SamplesSample input & output
Ejecutar cada 5 minutos
*/5 * * * *
Descripción: Ejecutar cada 5 minutos Próxima: 00:05, 00:10, 00:15 (ejemplo)
FAQFAQ
Which cron format does it support?
The standard cron expression with five fields: minute, hour, day of month, month and day of week. `*` (all), `,` (list), `-` (range) and `/` (step) work. Example: `0 9 * * 1-5` is 9:00 on weekdays.What happens if I set both day of month and day of week?
As in standard cron, it runs on days matching either one (OR, not AND). For example `0 0 13 * 5` runs on the 13th of every month and also every Friday.Can I use names for months and weekdays?
Yes. Months accept `jan` to `dec` and weekdays `sun` to `sat`, case-insensitive. In the weekday field both 0 and 7 mean Sunday.What is "next run" based on?
It calculates the next five runs from the current time in your browser and shows them in the browser's time zone. It searches up to four years ahead.Can I use Quartz or Spring expressions (`?`, `L`, `W`, `#`, a seconds field)?
Yes. The “Quartz / Spring cron” card lower on the page checks 6 or 7 fields (with seconds), `?`, `L`, `W`, `#` and a year, points out mistakes, explains each field and lists the next 10 runs. The top field is for 5-field standard cron. AWS EventBridge expressions are not supported.Is my expression sent anywhere?
No. Parsing and next-run calculation all happen in your browser.
Use casesCommon use cases
Checking that a crontab expression does what you intend
Paste an expression such as `*/15 9-17 * * 1-5` and use the description and next run times to confirm it behaves as expected.Writing GitHub Actions or Kubernetes CronJob schedules
Check the expression you put in `schedule` or a CronJob's `schedule:`.Reading cron expressions written by others
Paste an inherited or to-be-reviewed expression and see at once when it runs.Estimating run frequency
Look at the next few run times to check, before deploying, that a batch interval is neither too long nor overlapping too much.
NotesNotes & limitations
The top field is for 5-field standard cron (use the card below for seconds)
The top field only reads 5-field standard cron. For Quartz and Spring expressions (6 or 7 fields, with seconds, `?`, `L`, `W`, `#`) use the “Quartz / Spring cron” card below. AWS EventBridge expressions are not supported.Next run times use your browser's time zone
If your server or CI runs in UTC, the real run time differs from what is shown. GitHub Actions `schedule` uses UTC.Out-of-range values are not strictly checked
A value such as minute 70 does not raise an error and may just leave the next run times empty. If no times appear, review the expression.The description is in Japanese and English only
The written description appears in Japanese or English; other languages show the English one. Next run times appear in every language.
AboutAbout this tool
Cron Expression Parser and Editor
A must-have tool for system administrators and backend engineers to parse, visualize, and edit “Cron expressions” as human-readable schedules.
It translates cryptic strings of asterisks and numbers like 0 0 * * * or */5 * * * 1-5 into natural language descriptions like “Every day at midnight” or “Every 5 minutes, Monday through Friday”.
Primary Use Cases
- Configuring Batch Jobs: Before scheduling a cron job directly on your production server (crontab), use this tool to verify the syntax and prevent misconfigurations that could cause unexpected server load.
- Preview Upcoming Executions: The parser lists the exact dates and times of the next planned executions based on your formula, letting you see at a glance whether the job behaves as intended. All computations are securely processed on your local machine.
