⏰ Cron Expression to Text
By ToolNimba Web Dev Team · Updated 2026-06-19
Order: minute hour day-of-month month day-of-week. Try 0 9 * * 1-5 or */15 * * * *.
| Field | Value | Allowed | Meaning |
|---|
A cron expression is a compact way to tell a scheduler when to run a job, but five numbers and symbols like 0 9 1-5 are hard to read at a glance. Paste any standard 5-field crontab line here and this tool turns it into a plain English sentence, then breaks it down field by field so you can see exactly what each part means. It runs entirely in your browser, so nothing you type is sent anywhere.
What is the Cron Expression to Text?
Cron is the time-based job scheduler built into Unix and Linux systems, and its syntax has become the de facto standard far beyond cron itself: CI pipelines, container orchestrators, serverless platforms and many app frameworks all accept the same expression. A standard expression has five fields separated by spaces, in this fixed order: minute, hour, day-of-month, month, and day-of-week. Each field says which values trigger the job, and the job runs whenever the current time matches every field at once.
Each field accepts four kinds of value. A single number means exactly that value (5 in the minute field means minute 5). A star () means every value the field allows. A list separated by commas means any of several values (1,15 in day-of-month means the 1st and the 15th). A range with a hyphen means a span (1-5 in day-of-week means Monday through Friday). On top of any of these you can add a step with a slash: /15 in the minute field means every 15 minutes, and 0-30/10 means 0, 10, 20 and 30.
The field that trips people up most is day-of-week. It runs 0 to 6 where 0 is Sunday, and on many systems 7 is also accepted as Sunday. The other subtle rule is how day-of-month and day-of-week combine: in classic cron, if both are restricted (neither is a star) the job runs when either matches, not both. This tool focuses on translating the syntax clearly so you can read a schedule with confidence before you trust it in production.
When to use it
- Double-checking a crontab line a colleague wrote before you deploy it.
- Documenting what a scheduled job does so the comment matches the schedule.
- Learning cron syntax by typing an expression and reading the plain English it produces.
- Debugging a job that fires at the wrong time by seeing the field breakdown.
How to use the Cron Expression to Text
- Type or paste a 5-field cron expression into the box (minute hour day-of-month month day-of-week).
- Read the plain English description that appears instantly above the table.
- Check the field-by-field breakdown to confirm each part means what you expect.
- Use a preset button as a starting point, then edit it to match your schedule.
Formula & method
Worked examples
You want to understand the expression 0 9 * * 1-5.
- Field 1 minute = 0, so at the top of the hour.
- Field 2 hour = 9, so 09:00.
- Field 3 day-of-month = *, every day.
- Field 4 month = *, every month.
- Field 5 day-of-week = 1-5, Monday through Friday.
Result: At 09:00, Monday through Friday.
You want to understand the expression */15 * * * *.
- Field 1 minute = */15, a step of 15 over 0-59, so minutes 0, 15, 30 and 45.
- Field 2 hour = *, every hour.
- Fields 3, 4 and 5 are all *, every day, month and weekday.
- Combining a 15-minute step with every hour means it fires 4 times an hour.
Result: Every 15 minutes.
The five cron fields, in order, with their allowed values
| Position | Field | Allowed values | Notes |
|---|---|---|---|
| 1 | Minute | 0 to 59 | Top of the hour is 0 |
| 2 | Hour | 0 to 23 | 24-hour clock, midnight is 0 |
| 3 | Day of month | 1 to 31 | Day numbers, not weekdays |
| 4 | Month | 1 to 12 | January is 1 |
| 5 | Day of week | 0 to 6 | 0 is Sunday, 6 is Saturday |
Special characters you can use in any field
| Symbol | Name | Example | Meaning |
|---|---|---|---|
| * | Star | * | Every value the field allows |
| , | List | 1,15 | Any of the listed values |
| - | Range | 1-5 | A span from start to end |
| / | Step | */15 | Every nth value across the range |
Common mistakes to avoid
- Getting the field order wrong. The order is minute, hour, day-of-month, month, day-of-week. Putting the hour first (a common habit from reading clocks) means the job fires at the wrong minute. Read the breakdown table to confirm each field landed where you intended.
- Assuming Sunday is 7. The standard range for day-of-week is 0 to 6 with 0 as Sunday. Many systems also accept 7 as Sunday, but not all do, so 0 is the safe choice for Sunday.
- Mixing up day-of-month and day-of-week. When both day fields are restricted (neither is a star), classic cron runs the job when either field matches, not both. If you mean a specific weekday, leave day-of-month as a star.
- Reading */15 as starting at 15. A step like */15 starts at the lowest allowed value, so in the minute field it fires at 0, 15, 30 and 45, not at 15, 30 and 45. To start later, use a range such as 15-59/15.
Glossary
- Cron
- The time-based job scheduler on Unix and Linux that runs commands at fixed times, dates or intervals.
- Crontab
- The configuration file (and command) that holds a user's cron jobs, one schedule plus command per line.
- Field
- One of the five space-separated parts of a cron expression: minute, hour, day-of-month, month or day-of-week.
- Step value
- A slash expression like */15 that matches every nth value across a range, for example every 15 minutes.
- Range
- A hyphen expression like 1-5 that matches every value from the start to the end inclusive.
Frequently asked questions
What are the five fields in a cron expression?
In order they are minute (0-59), hour (0-23), day-of-month (1-31), month (1-12) and day-of-week (0-6, where 0 is Sunday). The job runs when the current time matches every field at once.
What does * * * * * mean?
Five stars means every value of every field, so the job runs every minute of every hour, every day, every month, on every weekday.
What does */15 mean in cron?
A step of 15. In the minute field, */15 fires at minutes 0, 15, 30 and 45, which is every 15 minutes. The step always counts from the lowest allowed value of the field.
Is Sunday 0 or 7 in cron?
The standard range is 0 to 6 with 0 as Sunday. Many systems also treat 7 as Sunday, but support varies, so use 0 to be safe across schedulers.
Does this tool support seconds or special strings like @daily?
No. It parses the classic 5-field cron format (minute through day-of-week). It does not handle a leading seconds field, named macros like @daily, or non-standard extensions such as L, W or # used by some schedulers.
Is my cron expression sent to a server?
No. The parsing and translation happen entirely in your browser with JavaScript. Nothing you type is uploaded or stored anywhere.