Tool overview
What is a Cron Parser & Generator?
A cron calculator turns crontab expressions into a plain-language sentence, verifies the next runs in UTC, and lets you build Linux, Spring, or Quartz schedules.
Why use this Cron Parser & Generator?
Confirm what production will do before you paste into crontab or @Scheduled — UTC by default, with a local equivalent and copy-ready expression.
Key Features
Natural-language decode, UTC next runs, Linux/Spring/Quartz dialects, intent presets, and private client-side parsing.
How to Use
Follow these steps to get accurate results from the tool interface above.
- Choose Linux Cron, Spring, or Quartz — the field map and examples follow the scheduler you selected.
- Paste an expression or pick an intent preset such as every weekday at 9 AM.
- Read the plain-language sentence first, then confirm the next runs in UTC (with a muted browser-local equivalent when it differs).
- Edit the labeled fields under the calculator; the expression updates in the other direction, with inline errors such as minute > 59.
- Copy the expression, or share the page hash (#expr=&tz=&dialect=) so someone else opens the same schedule.
Cron Expression Technical Specifications
Parse and generate Linux crontab, Spring, and Quartz expressions in the browser. Next runs default to UTC. Quartz L, W, and # are not supported yet.
Field maps by dialect
Linux crontab is five fields. Spring adds a leading seconds field. Quartz is six fields, optionally seven with year, and requires ? on exactly one of day-of-month or day-of-week.
Linux crontab * * * * * │ │ │ │ └─ day-of-week (0–7 or SUN–SAT; 0 and 7 = Sunday) │ │ │ └─── month (1–12 or JAN–DEC) │ │ └───── day-of-month (1–31) │ └─────── hour (0–23) └───────── minute (0–59) Spring * * * * * * │ └─ same five fields as Linux, plus leading second (0–59) Quartz * * * * * ? * │ │ │ │ │ │ └─ year (optional, 1970–2099) │ │ │ │ │ └─── day-of-week (1–7 or SUN–SAT; 1 = Sunday) │ │ │ │ └───── month │ │ │ └─────── day-of-month (use ? when weekdays are set) │ │ └───────── hour │ └─────────── minute └───────────── second
UTC next-run calculator
Next runs are computed in the selected timezone. The default is UTC — the zone Kubernetes CronJobs, GitHub Actions, and most cloud crontab daemons actually use. Pick a UTC offset such as UTC -5, or your browser timezone. When the selected zone is not the browser zone, each timestamp also shows a muted local equivalent.
Linux crontab ORs day-of-month and day-of-week when both are restricted. Kubernetes CronJobs follow that Linux behavior; AWS EventBridge uses AND. Quartz L/ W / # last-day and nth-weekday tokens are rejected until a later release.
Example library and named values
Named months and weekdays parse on every dialect (MON-FRI, JAN). Linux also expands @hourly, @daily, @weekly, @monthly, @yearly, and @reboot. Linux still rejects ?.
- Every minute —
* * * * * - Every 15 minutes —
*/15 * * * * - Weekdays at 09:00 —
0 9 * * 1-5 - Spring weekdays at 09:00 —
0 0 9 * * MON-FRI - Quartz weekdays at 09:00 —
0 0 9 ? * MON-FRI
Share a calculator state with #expr=&tz=&dialect=.
Frequently Asked Questions
Expandable answers for common debugging bottlenecks and data privacy questions.
Related tools
Explore other related utilities that complement this tool.
Official Documentation & References
Authoritative specifications and platform documentation for this utility.