Cron Expression Parser & Generator
Parse and explain cron expressions in plain English. See the next 5 upcoming run times for any schedule.
Last updated:
Format: minute hour day-of-month month day-of-week (5 fields)
In plain English
At minute 0,15,30,45 of every hour, on Monday,Tuesday,Wednesday,Thursday,Friday.
Next 5 run times (local timezone)
- 7/20/2026, 12:00:00 AMin 10 hr
- 7/20/2026, 12:15:00 AMin 11 hr
- 7/20/2026, 12:30:00 AMin 11 hr
- 7/20/2026, 12:45:00 AMin 11 hr
- 7/20/2026, 1:00:00 AMin 11 hr
Enter a cron expression above (like 0 9 * * 1-5) to see a plain-English description and the next five run times. Everything is computed in your browser.
What is Cron Parser?
A cron expression is a compact schedule used by Unix cron, Kubernetes CronJobs, CI systems, and cloud schedulers. Its five fields — minute, hour, day-of-month, month, day-of-week — are terse and easy to get wrong. This parser translates any expression into plain English and previews the next few run times so you can confirm a schedule does what you intend before deploying it.
How to read a cron expression
- 1Enter a 5-field cron expression, e.g. */15 * * * *.
- 2Read the plain-English explanation of when it runs.
- 3Check the list of upcoming run times to confirm the schedule.
- 4Adjust the fields until the preview matches your intent.
Use Cases
Verify a CronJob schedule
Confirm a Kubernetes CronJob or crontab entry fires at the times you expect before shipping it.
Decode an inherited crontab
Understand a cryptic expression someone else wrote without mentally parsing every field.
Design a new schedule
Iterate on fields and watch the next-run preview until the timing is right.
Code Examples
Common expressions
*/15 * * * * every 15 minutes
0 9 * * 1-5 09:00, Mon–Fri
0 0 1 * * midnight on the 1st
0 */6 * * * every 6 hoursKey Concepts
- The five fields
- In order: minute (0-59), hour (0-23), day-of-month (1-31), month (1-12), day-of-week (0-6, Sun=0). An asterisk means 'every'.
- Step and range
- */5 means 'every 5'. 1-5 is a range. 1,15 is a list. Combine them: 0-30/10 runs at 0, 10, 20, 30.
- Timezone
- Cron runs in the server's timezone. Most production servers use UTC, so a '9am' schedule may not be 9am locally.
Tips & Best Practices
- ▸Day-of-month and day-of-week are OR-combined when both are set — a classic gotcha that fires more often than expected.
- ▸Servers usually run in UTC; convert your intended local time before writing the expression.
- ▸The optional 6th 'seconds' field (Quartz, some cloud schedulers) is not standard Unix cron — check your platform.
- ▸Prefer */N steps over long comma lists for readability (*/15 beats 0,15,30,45).
Frequently Asked Questions
Which cron dialects are supported?
Classic Unix crontab with 5 fields (minute, hour, day of month, month, day of week). The optional 6th 'seconds' field used by Quartz and some cloud schedulers is not supported.
Are the next run times in my local timezone?
Yes. The upcoming schedule is computed against your browser's local timezone. Servers usually schedule in UTC, so double-check when copying to production.
Related Tools
Timestamp Converter
Convert Unix timestamps to human-readable dates and vice versa. Supports seconds, milliseconds, ISO 8601, and timezone selection.
JSON Formatter
Format, beautify, and validate JSON online. Free, fast, and 100% local — your data never leaves your browser.
JSON Validator
Validate JSON online with instant error location and structure statistics (depth, keys, node types). 100% local — your JSON never leaves the browser.
JSON → TypeScript
Convert JSON to TypeScript interfaces instantly. Generate strongly-typed TS types from any JSON sample.
JSON → Go
Convert JSON to Go structs online. Generates idiomatic Go structs with proper json tags and PascalCase field names.
JSON → YAML
Convert JSON to YAML online. Preserve structure, comments-free, and ready to paste into Kubernetes or CI configs.