Cron Explainer
Explain cron expressions in plain human-readable words.
Explain cron expressions in plain human-readable words. Enter your numbers and get an instant result.
Paste a cron expression, pick the language, and the page returns the schedule in human-readable words: which minutes, hours and days the expression covers.
This page executes on the tool server: the expression and the locale are sent for that one request, the description runs there, and nothing is stored. An expression that does not parse is refused as invalid rather than described as a guessed schedule.
The description follows the five standard fields. English and Chinese describe the same schedule; the locale changes the words, never the meaning.
What the explanation covers
Each field is decoded in place — minute, hour, day of month, month, day of week — and composed into one sentence naming the covered times. Ranges, steps and lists are read as written, so a stepped hour field stays a stepped schedule in words.
The page describes coverage, not execution. It says which times match; it never computes the next run or touches any scheduler.
- Five standard fields, decoded in place
- English or Chinese description
- Invalid expressions refused, never guessed
What is sent and what is kept
The request carries the expression and the locale, and the response carries the description. Neither is written to disk or logged; a second expression is a second request with no memory of the first.
An empty input is refused with the reason. The description library must be present for the run; a missing library is reported rather than answered with a fabricated schedule.
How to use the expression and locale
Paste the cron expression, pick the English or Chinese locale, and press Execute Tool Engine. Each field is decoded in place, minute, hour, day of month, month, day of week, and composed into one sentence naming the covered times; ranges, steps and lists are read as written. The locale changes the words, never the meaning.
An expression that does not parse is refused as invalid rather than described as a guessed schedule, and an empty input is refused outright. The page describes coverage, not execution: which times match, never the next run or any scheduler.
What to Expect
Best for
- Reading an inherited crontab line
- Checking a schedule before deploying it
- Explaining cron to a teammate in either language
Not ideal for
- Computing the next execution time
- Non-standard schedulers with extra fields
- Editing or installing the crontab
What this tool keeps
- The expression exactly as pasted
- The same description for the same input and locale
- Your input private beyond the single request
What may need cleanup
- Confirming the timezone the scheduler runs in
- Checking extensions your cron adds to the five fields
- Testing the schedule where it will actually run
Common errors
- Pasting six fields where five are read
- Reading coverage as a next-run promise
- Forgetting the scheduler's timezone differs
Example use cases
- Decoding a nightly backup line
- Verifying a stepped interval before rollout
- Documenting a job's cadence in words
Sample input
A five-field expression for midnight daily, explained in English.
Sample output
A sentence naming the covered times with the expression and locale echoed, described on the tool server.
Who this is for
- Operators reading crontabs
- Developers scheduling jobs
- Anyone checking a cadence twice
Frequently asked questions
What shape must the expression have?
A standard cron expression, five fields and the usual ranges. Anything else is refused as invalid rather than described as a guessed schedule.
What does the locale do?
It chooses the language of the description, English or Chinese. The schedule described is the same either way.
Will it tell me the next run time?
No. The page describes the schedule the expression names — which minutes, hours and days it covers — not a computed next execution.
Build custom tools for your store
Join the SDK program to create useful ecommerce utilities for your store.