Cron Expression Parser Online — Next Run Times

Paste a standard 5- or 6-field cron expression (or a supported @ alias) and see a live human-readable schedule, field breakdown, and next fire times in UTC or your local timezone — all in your browser.

Loading…
Cron parser — developer notes
Live human-readable schedule explanations, field breakdown, and upcoming fire times for standard Unix cron (5 fields) or 6-field expressions with seconds. Not AWS EventBridge or Quartz dialects.

How parsing works

Type a cron expression (or pick a preset) — parsing updates live. Choose 5 or 6 fields, how many next runs to list, and UTC vs local display. Matching always uses UTC calendar fields; the timezone option only changes how times are shown.

Options

Field count (5 / 6)
5 fields is classic crontab (minute hour day-of-month month day-of-week). 6 fields prepends seconds for schedulers that support them.
Next runs (5 / 10 / 25)
Show enough upcoming fires for planning without flooding the list.
Timezone (UTC / local)
Align the next-run list with ops expectations — UTC for servers, local for wall-clock checks.

Examples

Every 5 minutes

Expression

*/5 * * * *

Meaning

Fires at minute 0, 5, 10, … of every hour

Every 15 minutes (6-field)

Expression

0 */15 * * * *

Meaning

At second 0 of every 15th minute

Related utilities

Need epoch math? Open the Unix timestamp converter. Generate IDs with the UUID generator.

Cron parser FAQ

Scheduling questions

Are @daily macros supported?

Yes for common aliases: @hourly, @daily / @midnight, @weekly, @monthly, @yearly / @annually. @reboot is not supported (no boot context in the browser). Unknown or malformed @ tokens are rejected.

What day does @weekly use?

@weekly expands to 0 0 * * 0 — Sunday at midnight UTC fields (day-of-week 0).

Is this Quartz or EventBridge cron?

No. This tool targets common Unix-style 5/6-field expressions, not vendor-specific dialects.

Does day-of-month vs day-of-week use OR or AND?

When both day fields are constrained (not *), fire times match if either field matches — common Unix semantics.

UTC matching vs local display?

Next-run matching uses UTC field values. The timezone control only formats the list for display (UTC or your browser local zone).

Is my expression uploaded?

Never — parsing stays in your browser.

Timestamps, UUID, ULID, Nanoid, cron, passwords, regex, slugify, number bases, case, text diff, and chmod — all client-side.