Free · No signup · Runs in your browser

Cron Expression Explainer

Turn a cryptic crontab line like */15 9-17 * * 1-5 into a sentence you can actually read — entirely in your browser.

01 · How it works

Three steps, then done.

Paste a standard five-field cron expression and read the schedule in plain English instantly. The parser understands stars, ranges, lists, steps, and month and weekday names.

1

Paste the cron line

Drop in a five-field crontab expression — minute, hour, day-of-month, month, day-of-week. A six-field line is accepted too; the first field is read as seconds.

2

Read the sentence

The tool describes exactly when the job fires, such as "Every 15 minutes, between 09:00 and 17:59, Monday through Friday." Names like JAN or MON-FRI are understood.

3

Verify and copy

If a field is out of range or malformed, you get a precise error instead of a wrong answer. Copy the explanation to drop into a comment, ticket, or runbook.

02 · Why ours

Why use thiscron explainer

A focused way to sanity-check a schedule before it ships — readable, strict about ranges, and private by default.

  • 01

    100% client-side

    The expression is parsed by JavaScript in your browser. Nothing is uploaded, logged, or sent to a server, so an internal schedule stays internal.

  • 02

    Full field syntax

    Stars, step values like */5, ranges such as 9-17, comma lists like 0,30, and month and weekday names (JAN, MON-FRI) all parse, including combinations of them.

  • 03

    Strict validation

    Field count and per-field numeric ranges are checked. Minute 60, hour 25, or a backwards range returns a clear error rather than a confidently wrong sentence.

  • 04

    Readable output

    Contiguous hours become time windows, evenly spaced minutes become "every N minutes", and weekday runs read as "Monday through Friday" — the way a person would say it.

"Every cron line is a sentence in disguise. This reads it back to you before it runs in production."
csvtodashboard.com
03 · FAQ

cron explainer questions.

What cron format does this expect?
Standard five-field crontab syntax: minute, hour, day-of-month, month, and day-of-week, in that order. If you paste six fields, the leading field is treated as a seconds field (Quartz-style) and noted in the result.
Asterisks for every value, step values like */15, ranges like 9-17, comma-separated lists like 0,30, and combinations of those. Month names (JAN-DEC) and weekday names (SUN-SAT, including MON-FRI ranges) are recognized, case-insensitively.
When both the day-of-month and day-of-week fields are restricted, standard cron runs the job when either matches. The explanation reflects that by joining the two day clauses with "or".
You get a specific, friendly error instead of output — for example "60 is out of range for the minute field (0-59)" or "A cron expression needs 5 fields". The tool never throws or guesses.
No. Parsing happens entirely in your browser with no network call. The expression, the explanation, and any error all stay on your machine.