Cron Expression Parser
Parse and understand cron expressions. See a plain-English description and the next scheduled run times.
Plain English
At 09:00, on Monday, Tuesday, Wednesday, Thursday, and Friday.
Next 8 runs
- 1Mon, May 18, 2026, 09:00 AM
- 2Tue, May 19, 2026, 09:00 AM
- 3Wed, May 20, 2026, 09:00 AM
- 4Thu, May 21, 2026, 09:00 AM
- 5Fri, May 22, 2026, 09:00 AM
- 6Mon, May 25, 2026, 09:00 AM
- 7Tue, May 26, 2026, 09:00 AM
- 8Wed, May 27, 2026, 09:00 AM
What is a Cron Parser?
A cron parser reads a cron expression — the five-field (or six-field) schedule notation used by Unix cron schedulers — and translates it into a human-readable description, upcoming execution times, and individual field breakdowns. Cron expressions power scheduled tasks in Linux servers, Kubernetes CronJobs, GitHub Actions, AWS EventBridge, and virtually every server-side job scheduler. Reading and writing them correctly is critical for reliable automation.
Common Use Cases
- Verify that a cron schedule fires at the intended times before deploying it to production
- Debug a job that isn't running by checking the next scheduled execution
- Translate a product requirement ("run every weekday at 9 AM") into a cron expression
- Review an existing cron job's schedule without needing to read the cron documentation
- Generate cron expressions for CI/CD pipelines and cloud scheduler services
How It Works
A standard cron expression has five fields: minute hour day-of-month month day-of-week. Each field accepts a number, a wildcard (*), a range (1-5), a list (1,3,5), or a step (*/15). The parser evaluates all combinations to compute the next N execution timestamps. Some schedulers add a sixth seconds field at the start; toggle this option if your platform uses it.
Frequently Asked Questions
What does */5 mean in a cron expression?
*/5 means "every 5 units." In the minutes field, */5 means every 5 minutes (at 0, 5, 10, 15 … 55). The step operator divides the allowed range by the step value.
What is the difference between 0 and * in the seconds field?
0 fires at the exact start of the minute; * fires every second. Most jobs should use 0 in the seconds field to run once per minute trigger.
Why does my cron job run twice in some hours?
Daylight saving time transitions can cause an hour to repeat, firing a job scheduled for that hour twice, or skip an hour, causing a job to be missed. Schedule critical jobs at times that do not fall within DST transition windows, or use UTC.
Related Tools
Unix Timestamp
Convert Unix timestamps to human-readable dates and back instantly.
JWT Decoder
Decode and inspect JSON Web Tokens securely in your browser.
JWT Generator
Build and sign JSON Web Tokens with a custom payload and secret.
Regex Tester
Test and debug regular expressions with live match highlighting.
JSON Formatter
Format, validate, and minify JSON data instantly.
Hash Generator
Generate MD5, SHA-1, SHA-256, and SHA-512 hashes instantly.
Base64 Encoder
Encode and decode strings using Base64 encoding.
URL Encoder
Encode and decode URLs with percent-encoding instantly.
UUID Generator
Generate UUID v4 values instantly, with bulk generation and validation.
Text Diff
Compare two blocks of text and highlight additions, deletions, and unchanged lines.
Case Converter
Convert text to camelCase, snake_case, UPPERCASE, kebab-case, and more.
SQL Formatter
Format and minify SQL queries with dialect support for MySQL, PostgreSQL, SQLite, and more.
CSV ↔ JSON
Convert CSV to JSON or JSON to CSV with support for custom delimiters and quoted fields.
Number Base Converter
Convert between decimal, hexadecimal, octal, and binary number bases.
Color Converter
Convert colours between HEX, RGB, HSL, HSV, and CMYK formats.
Cron syntax: A standard cron expression has 5 fields — minute hour day month weekday. Each field accepts * (any), */n (every n), n-m (range), and a,b,c (list) syntax.
Supports @yearly, @monthly, @weekly, @daily, and @hourly macros. Month and weekday names (JAN–DEC, SUN–SAT) are also accepted. All processing happens locally in your browser.