Clear English Translation for Complex Schedules
Demystify confusing step values (*/15), ranges (1-5), and comma lists with an immediate natural language description.
Free online Cronjob Explainer and Generator. Convert cron expressions into plain English sentences, view next 5 run dates, and build crontab schedules visually.
Any value
Match every unit
Value list
e.g. 1,15,30
Range
e.g. 1-5 (Mon–Fri)
Step / Interval
e.g. */15 (every 15)
A systems engineer inspects a legacy server crontab line: `15 3 1,15 * 1-5` and needs to verify when the maintenance script triggers.
| Expression | 15 3 1,15 * 1-5 |
| Human Explanation | At 03:15 AM, on day 1 and 15 of the month, and Monday through Friday. |
| Upcoming Next Runs | 1. Mon, Nov 2, 2026, 03:15 AM 2. Tue, Nov 3, 2026, 03:15 AM 3. Sun, Nov 15, 2026, 03:15 AM |
💡 The explainer eliminates guesswork, guaranteeing that backup scripts execute at intended off-peak maintenance hours.
Enter any 5-field (standard Unix/Linux) or 6-field cron expression into the input field, or choose from popular preset schedules.
Read the instant human-readable English explanation breaking down minutes, hours, days, months, and weekdays.
Examine the calculated upcoming run times list showing exact execution dates, hours, and relative countdowns in your local timezone.
Demystify confusing step values (*/15), ranges (1-5), and comma lists with an immediate natural language description.
Preview the next 5 to 10 scheduled execution timestamps calculated against your current system clock in both local and UTC time.
Select common schedules (hourly, daily at midnight, weekly, monthly) or use intuitive dropdown controls to build cron lines without memorizing syntax.
Validating input strings or cron log outputs? Check out the Test regular expressions in real time.
Need to structure scheduled cron event payloads in JSON? Use the Format and validate JSON payloads.
Auditing changes across server crontab configuration files? Try the Compare crontab file versions.
Triggering external HTTP webhooks via scheduled jobs? Use the Encode webhook URLs.
Standard 5-field order and allowed values for Linux crontab configurations.
| Field Position | Field Name | Allowed Values | Special Characters Allowed |
|---|---|---|---|
| 1st | Minute | 0 - 59 | * , - / |
| 2nd | Hour | 0 - 23 | * , - / |
| 3rd | Day of Month | 1 - 31 | * , - / L W |
| 4th | Month | 1 - 12 or JAN - DEC | * , - / |
| 5th | Day of Week | 0 - 6 (0 = Sunday) or SUN - SAT | * , - / L # |
Field positions are separated by a single space. Comments can be added with # at the start of a line.
In standard Unix/Linux crontab, the 5 fields are: (1) Minute (0-59), (2) Hour (0-23), (3) Day of the Month (1-31), (4) Month (1-12 or JAN-DEC), and (5) Day of the Week (0-6 where 0 is Sunday, or SUN-SAT).
An asterisk (*) represents every possible value for that field (e.g. * in the hour field means every hour). A forward slash followed by a number (/n) indicates step intervals (e.g. */15 in the minute field means every 15 minutes).
Standard Unix crontab accepts 0 for Sunday. Many implementations (including Vixie cron and AWS EventBridge) accept both 0 and 7 to represent Sunday.
Yes. The scheduling engine accurately accounts for varying month lengths (28, 29, 30, 31 days) and leap years when projecting upcoming run dates.
Developer Tools
Test, evaluate, and debug regular expressions in real-time with visual match highlights, capture group inspection, and quick regex cheat sheets.
Format, beautify, validate, and minify JSON data online with instant syntax error highlighting and tree inspection.
Compare two text snippets or code blocks side-by-side with highlighted character and line differences.
Encode or decode URL components and query strings with percent encoding.
Generate secure, cryptographically random Version 4 (v4) and time-ordered Version 7 (v7) UUIDs and GUIDs with custom formatting, bulk batch generation, and live inspection.
Explore, navigate, and inspect complex JSON payloads with an interactive collapsible tree viewer, type badges, node search, and JSON path copying.