How to Read a Crontab Expression and Turn It Into a Plain English Schedule
Learn how to decode a five-field crontab line into a readable schedule, load common presets, and copy the expression into a crontab or CI config.
Cron Expression Parser
Introduction
A cron line such as 0 0 * * 1 is compact but easy to misread, and a wrong field means a backup or report runs at the wrong time. The Cron Expression Parser accepts a standard five-field crontab expression and prints a short English description of the minute, hour and weekday it targets. Parsing happens in the browser with no server involved.
Step-by-Step Instructions
- Enter a five-field expression (minute hour day-of-month month day-of-week) in the Cron Expression field.
- Click a preset such as Every 15 Mins, Daily at Midnight or 1st of Month to load a common schedule instantly.
- Read the Human-Readable Schedule box, which updates on every keystroke.
- Adjust individual fields and watch the description change to confirm the intended time and weekday.
- Click Copy Cron to copy the finished expression into a crontab file or scheduler config.
Key Use Cases
- Server maintenance: Confirm a nightly cleanup job is set for midnight rather than noon before saving the crontab.
- CI pipelines: Check the schedule block of a GitHub Actions or GitLab workflow before committing it.
- Onboarding: Explain an inherited crontab entry to a teammate without reading the cron man page.
Frequently Asked Questions
What happens if the expression has six fields or extra spaces?
The parser expects exactly five whitespace-separated fields. Six-field formats that include seconds, or lines with a missing field, return an invalid expression message that lists the expected field order. Extra spaces between fields are tolerated.
Does the description cover every field?
The summary focuses on the minute, hour and day-of-week fields. It recognises step minutes like */15, exact hours, midnight, and weekday numbers 0 to 7. The day-of-month and month fields are accepted but not spelled out in the English sentence, so check those manually for schedules like 0 0 1 * *.
Does the tool list upcoming run times?
No. The current version produces a text description only and does not calculate the next execution dates. Use it to sanity check the expression, then rely on the scheduler itself for exact run history.