Cron Expression Parser
🔒 Runs in your browser
Build the expression with selects — every change updates the expression above
Common examples
Field by field
| Field | Value | Means |
|---|
@reboot runs once, at system startup — it has no scheduled next run.
Next 10 runs
| # | Your time zone | Romania time (Europe/Bucharest) |
|---|
A description you can actually read — in English or Romanian
Type any 5-field crontab expression, or a 6-field one with a leading seconds slot, and get a
plain-language sentence back instantly, via the open-source cronstrue library.
Switch the site language and the description switches with it — including a genuine
Romanian locale (not a machine translation), a feature most cron tools skip entirely.
Next 10 runs, in two time zones
Runs are computed in your browser's local time zone; when it differs from Romania's,
a second column shows those exact same moments converted to Europe/Bucharest —
computed with the cron-parser library.
Frequently asked questions
What's the difference between a 5-field and a 6-field cron expression?
The standard crontab format has five fields — minute, hour, day of month, month, day of week. A leading sixth field adds seconds, letting a schedule run more often than once a minute; both forms are supported.
How is the description translated to Romanian?
Via cronstrue's dedicated Romanian locale — the same underlying schedule produces a natural Romanian sentence (e.g. "la ora 09:00, doar lunea"), not a machine-translated English string.
Why are there two time-zone columns in the next-runs table?
A cron schedule is evaluated in a specific time zone. The table always shows your browser's local time zone and, separately, Europe/Bucharest — merged into one column when they already match.
Is my expression sent to a server?
No. Parsing, the human-readable description and the next-run calculation all run locally in your browser using the cronstrue and cron-parser libraries.