ToolMintX
IT Tool

Cron Expression Generator & Parser

Build a cron schedule from five visual fields or paste one to translate it into plain English, then see the next five times it will actually fire in your local time zone.

Instant 100% Client-Side No Login
PROCESSINGLOCAL
LIMITNONE
PRIVACYBROWSER-ONLY

Cron Expression

“Every minute”
0-59
0-23
1-31
1-12
0-6, Sun-Sat

Common templates

How a cron expression actually works

Cron is the time-based scheduler that has run background jobs on Unix systems since the 1970s. A running daemon wakes up once a minute, compares the current time against every schedule it knows about, and runs the ones that match. Each schedule is one line: a five-field expression followed by the command to run. The five fields, in order, are minute, hour, day of the month, month, and day of the week. Nothing about the expression is fuzzy — it either matches the current minute or it does not.

Each field holds one of a few things. A single number pins that field to one value. An asterisk means “any value”, so it always matches. A range like 1-5 matches a span. A list like 0,15,30,45 matches several specific values. And a step like */15 matches every fifteenth value starting from the lowest — in the minute field that is :00, :15, :30, and :45. You can combine them: 0,30 9-17 * * 1-5 is “on the hour and half past, between 9 AM and 5 PM, Monday through Friday”.

The day-of-week field counts from 0 for Sunday through 6 for Saturday. For historical reasons 7 is also accepted as Sunday, and most crons let you write the first three letters of a day or month name instead of a number. This tool normalises all of that and shows you a plain-English reading of whatever you type, so you can confirm the expression says what you meant before it ever reaches a server.

The day-of-month and day-of-week trap

This is the single most misread piece of cron. When you restrict both the day-of-month field and the day-of-week field, cron does not require both to be true. It fires when either is true. So 0 0 13 * 5does not mean “the 13th, but only if it is a Friday” — it means “midnight on the 13th of every month, and also midnight every Friday”. That is why this tool shows a warning the moment both day fields are set, and why the next-run list is the real answer: it computes the OR exactly the way the daemon does.

Decoding beats guessing when writing the crontab line

A few habits save real outages. Cron runs with a bare environment, so give commands absolute paths (/usr/bin/python3, not python3) and do not assume your login shell's PATH. Redirect output — cron mails stdout and stderr to the local user by default, which usually means it is lost; append >> /var/log/job.log 2>&1 instead. And if a job might run longer than its interval, wrap it in flock so two copies never overlap.

Time zones, dialects, and what this parser does not cover

The next-run times on this page are in your browser's local time zone, because that is the frame you are reading in. A production cron daemon runs jobs in the server's configured zone, which on most cloud hosts is UTC. If a schedule needs to fire at 9 AM in a particular city, confirm what zone the box is set to first — a schedule that looks right on your laptop can land hours off in production. Daylight-saving transitions add another wrinkle: on the spring-forward night a job set for 2:30 AM may not run at all, and on fall-back it may run twice.

This tool parses the classic five-field Unix format used by Linux and macOS crontab. It deliberately does not accept the extensions layered on by other schedulers: the leading seconds field and the L (last), W (nearest weekday), and # (nth weekday) tokens from Quartz, or the ? placeholder those systems use in place of an asterisk. If you are targeting AWS EventBridge, a Spring application, or a Kubernetes CronJob, check that platform's own reference for the fields it adds — a Kubernetes CronJob, for instance, uses exactly this five-field syntax, while EventBridge requires six.

Everything here runs in your browser. The parsing, the English translation, and the next-run calculation are all plain JavaScript executing on your machine; no expression, path, or schedule is sent anywhere. Still, treat the output as a drafting aid: on a system where a missed or duplicated job matters, test the schedule in a staging environment before you trust it in production.

How to Use

1

Type a value into any of the five fields — Minute, Hour, Day of month, Month, Day of week — or paste a complete expression into the large box at the top.

2

Read the plain-English translation and, below it, the next five times the schedule will run in your own time zone.

3

Watch for the amber warning if you have set both day-of-month and day-of-week; cron treats those as OR, not AND.

4

Use a template button for a common schedule, then adjust a field to fine-tune it.

5

Copy the validated expression and paste it into your crontab, CI config, or scheduler.

Features

Translates any standard five-field cron expression into plain English
Shows the next five real fire times, computed locally in your time zone
Correctly handles the day-of-month / day-of-week OR rule and warns you about it
Validates every field and names the exact field that is wrong
Nine ready-made templates for the schedules people reach for most
Runs entirely in your browser — nothing is uploaded

Common Questions

About Cron Expression Generator

Build a cron schedule from five visual fields or paste an existing expression to translate it into plain English. See the next five times the schedule will actually fire in your local time zone, and get warned about the classic day-of-month versus day-of-week OR rule that trips up most people. Validates every field and names exactly what is wrong. Everything runs in your browser.

Also known as: cron expression, crontab generator, cron schedule maker, cron syntax, cron parser, translate cron to english, cron next run time, crontab validator, cron to plain english, cron job schedule builder, what does this cron mean, cron day of week vs day of month, crontab guru alternative.

Processing Note

Cron Expression Generator runs in your browser, so the input you enter is processed locally on this page and is not uploaded to a ToolMintX account.

Tool Limits

IT tools provide quick diagnostics and transformations. They cannot see every private network, deployment setting, proxy, firewall, or production edge case.

Explore More