Tools & 3D Studio
← All tools

CronMint · parse · explain · next runs

A cron line,
read back to you.
Before it runs.

Paste a 5-field or 6-field cron expression and get it back in plain English or Korean, the next 10 runs in the timezone you choose, and a crontab or GitHub Actions snippet of the same schedule — parsed and projected in this tab, never on a server.

0 bytes uploaded 0 external requests 5 + 6 fields crontab · Actions

Expression

minute hour day month weekday
—

    Field editor

    click a value to set it
    Reads asEN

    —

    Presets

    twelve lines that cover most jobs

    Take it with you

    same schedule, ready to paste
    
            

    How this reads a line

    POSIX first, edges stated

    01Fields, ranges and steps

    Each field is a list of numbers, names, ranges and steps: 1,15, mon-fri, 9-17, */5 and 20/15 all parse. A field that is * (or ?) is unrestricted — the difference matters for the next note.

    FieldRange
    Minute0–59
    Hour0–23
    Day of month1–31
    Month1–12 / JAN–DEC
    Weekday0–7 / SUN–SAT
    Second (6-field)0–59

    02Two day rules, one tie

    In Vixie cron, if day of month and weekday are both restricted, the job runs when either matches — 0 0 1 * 1 fires on the 1st and on every Monday. Leave one as * and only the other applies. Quartz refuses that line instead unless one of the two is ?; this tool follows crontab and states which rule it used.

    03Timezones are the usual bug

    crontab has no timezone field: it fires in the server's local time, which is UTC on most containers and runners. GitHub Actions schedules also default to UTC and now accept an optional timezone: key; the shortest interval there is 5 minutes. Each run below is shown in your chosen zone with its UTC equivalent, so the line you paste says the hour you meant.

    Questions

    syntax · timezone · platforms
    Why does my job run at the wrong hour?
    Nearly always a timezone gap. crontab fires in the server's local time — UTC on most containers — and GitHub Actions schedules default to UTC too. Set the zone your machine actually uses above and read the UTC column: 0 9 * * 1-5 in Asia/Seoul is 0 0 * * 1-5 in UTC, which is what a UTC server needs.
    5 fields or 6 — which do I need?
    Five for crontab, systemd timers, GitHub Actions and most schedulers. Six when the first field is seconds — Quartz, and parsers that follow it. Nothing else changes: a six-field line is a five-field line with a second in front, and this page reads both the same way.
    Why are L, W and # rejected?
    They are Quartz extensions rather than POSIX cron, and they mean different things in different engines. Rather than let a line work here and fail in crontab, the parser reports them as unsupported. For "last day of the month" the portable form is a normal day list plus a guard inside the job.
    What happens on a daylight-saving change?
    Runs are projected on the zone's real offsets, so an 09:00 schedule stays 09:00 local while its UTC time shifts by an hour. A wall-clock time that does not exist — the hour skipped when clocks spring forward — is dropped rather than invented, and the next valid run is shown instead.
    Does this page keep what I type?
    No. There is no endpoint, no analytics and no storage of the expression — only your language choice is remembered in this browser. The footer measures the page's own external requests and it stays at 0.