What Is a Cron Expression? A Plain-English Guide
A cron expression is a compact string of five (or six) fields that tells a scheduler exactly when to run a task — every minute, every weekday at 9 AM, on the last day of each month, you name it. The name comes from the Unix cron daemon, which has driven background automation since the 1970s. Today the same syntax powers cloud functions, CI/CD pipelines, database backups, Kubernetes CronJobs, Spring Boot schedulers, and dozens of other modern systems.
How This Cron Generator Online Works
This cron generator online removes the need to memorise field order or special characters. You pick a format — Standard 5-field or Quartz 6-field — fill in the dropdowns for minute, hour, day, month, and day-of-week (plus second for Quartz), and the tool instantly assembles a valid cron expression. You can also paste any existing expression into the tester to see a human-readable breakdown and the next five scheduled run times. There is nothing to install, no account to create, and no data ever leaves your browser.
The quick-preset menu covers the most common schedules — every minute, every five minutes, daily at midnight, weekdays at 9 AM — so you can get a working expression in one click and customise from there. Every change you make is reflected in real time, making it the fastest cron builder for both beginners and experienced engineers who just want to double-check a field.
Cron Expression Fields Explained
Understanding what each position does is the key to writing — or reading — any cron expression without guesswork.
Field 1
Minute (0–59)
Controls which minute(s) within an hour the job fires. */15 means every 15 minutes; 0 means on the hour only.
Field 2
Hour (0–23)
Uses 24-hour format. 9 = 9 AM, 21 = 9 PM. Pair with */6 for every six hours.
Field 3
Day of Month (1–31)
Targets specific calendar dates. Use 1,15 to run on the 1st and 15th, or L (Quartz) for the last day.
Field 4
Month (1–12 / JAN–DEC)
Numeric (3) or name (MAR) both work. Most systems accept either. A range like 6-8 covers summer months.
Field 5
Day of Week (0–6 / SUN–SAT)
1-5 targets Monday–Friday. Both 0 and 7 mean Sunday in standard cron.
Quartz Only — Field 0
Second (0–59)
Quartz adds a leading second field, enabling sub-minute precision. Required for Java Spring and AWS CloudWatch Events using Quartz syntax.
Standard Cron vs. Quartz Cron Expression Generator — What's the Difference?
The most common source of confusion when switching between systems is the difference between standard Unix cron and the Quartz cron expression format. Here is a quick comparison:
| Feature |
Standard Cron (5 fields) |
Quartz Cron (6–7 fields) |
| Field order |
MIN HOUR DOM MON DOW |
SEC MIN HOUR DOM MON DOW [YEAR] |
| Second-level precision |
❌ Not supported |
✅ Supported via first field |
Special chars: L W # |
❌ Not available |
✅ Last, Nearest weekday, Nth day |
? wildcard |
❌ Use * instead |
✅ Required when DOM and DOW both set |
| Year field |
❌ Not supported |
✅ Optional (1970–2099) |
| Common platforms |
Linux crontab, GitHub Actions, AWS Lambda, Kubernetes |
Spring Boot, Java EE, AWS CloudWatch (Quartz mode), Quartz Scheduler |
A common mistake is pasting a standard 5-field expression into a Quartz-based system without adding the leading second field. The Quartz cron generator mode in this tool automatically handles the extra field so the output is ready to drop into your Spring @Scheduled annotation or CloudWatch rule without any manual adjustment.
Cron Special Characters: A Complete Reference
The real power of cron expressions — and the part that trips people up — lives in its special characters. Here is what each one does and when to use it.
*
Any value
Matches every possible value for that field. * * * * * runs every single minute of every day.
,
Value list
Runs at each listed value. 0 9,12,17 * * * fires at 9 AM, noon, and 5 PM.
-
Range
Spans a consecutive sequence. 1-5 in the day-of-week field means Monday through Friday.
/
Step / increment
Fires at regular intervals. */10 in the minute field runs every 10 minutes starting at :00.
?
No specific value (Quartz)
Used when you set a day-of-week but not a day-of-month, or vice versa. Avoids ambiguity.
L
Last (Quartz)
L in day-of-month means the last day. 5L in day-of-week means the last Friday of the month.
W
Nearest weekday (Quartz)
15W fires on the closest weekday to the 15th — useful for payroll or billing jobs.
#
Nth occurrence (Quartz)
2#1 means the first Monday of the month. 6#3 means the third Saturday.
Real-World Cron Job Examples
These are the schedules engineers actually need. Copy any expression directly into your cron maker, CI/CD tool, or cloud scheduler.
| Use Case |
Standard Expression |
Quartz Expression |
Description |
| Database backup |
0 2 * * * |
0 0 2 * * ? |
Every day at 2 AM |
| Health check ping |
*/5 * * * * |
0 */5 * * * ? |
Every 5 minutes |
| Weekly report email |
0 8 * * 1 |
0 0 8 ? * MON |
Monday at 8 AM |
| Monthly invoice |
0 9 1 * * |
0 0 9 1 * ? |
1st of month, 9 AM |
| Cache flush |
0 0 * * * |
0 0 0 * * ? |
Daily at midnight |
| Business-hours sync |
0 9-17 * * 1-5 |
0 0 9-17 ? * MON-FRI |
Hourly, Mon–Fri, 9–5 |
| Quarterly archive |
0 0 1 1,4,7,10 * |
0 0 0 1 1,4,7,10 ? |
1st of each quarter |
Platform-Specific Cron Expression Converter Notes
Different platforms have slightly different interpretations of the cron specification. Use this as a quick cron expression converter reference before deploying.
🐧 Linux crontab
Standard 5-field syntax. The leading * for minutes is leftmost. Edit with crontab -e. No seconds field. Day of week: 0 or 7 = Sunday.
☁️ AWS CloudWatch Events
Quartz-style 6-field syntax with a mandatory ? in either DOM or DOW. Must wrap the whole expression in cron(...) when used in a rule.
☸️ Kubernetes CronJob
Standard 5-field syntax in the schedule: field. Time is in the cluster's timezone by default; use spec.timeZone (Kubernetes 1.27+) to override.
🍃 Spring Boot @Scheduled
Quartz 6-field format required. Expressions go in cron="" inside the annotation. Use this tool's Quartz mode to generate a ready-to-paste value.
🐙 GitHub Actions
Standard 5-field syntax under on.schedule.cron. All times are UTC. The minimum supported interval is every 5 minutes.
⚡ AWS Lambda
Supports both rate (rate(5 minutes)) and cron. For cron, uses the same CloudWatch Quartz style. All times run in UTC.
Frequently Asked Questions
What is a cron job generator used for?
A cron job generator helps you build syntactically correct cron expressions without having to memorise field positions or special characters. Instead of writing 0 9 * * 1-5 from memory, you select the values from a UI and the expression is assembled automatically — reducing typos and saving time.
How do I convert a cron expression to a human-readable description?
Paste any expression into the Expression Tester section of this cron expression converter above. It will translate the fields into plain English (for example: "At 09:00 AM, Monday through Friday") and show the next scheduled execution times so you can verify the logic before deploying.
What is a Quartz cron expression and why does it have 6 fields?
The Quartz Scheduler, widely used in Java applications, extends standard cron by adding a seconds field at the very beginning of the expression. This gives you sub-minute scheduling precision (e.g. run exactly at the 30-second mark) and additional special characters like L, W, and #. Our Quartz cron generator mode automatically handles the 6-field layout.
Can I use this as a cron timer generator for scheduled notifications?
Yes. As a cron timer generator, this tool is ideal for scheduling recurring notifications, alert checks, or reminder jobs. Define the time and recurrence pattern here, then copy the expression into your notification service — whether that's AWS SNS, a Node.js cron library, or a cloud platform scheduler.
Why does my cron expression not run at the right time?
The most common reasons are: (1) timezone mismatch — most cloud schedulers run in UTC regardless of your local timezone; (2) field-count mismatch — using a 5-field expression where a 6-field Quartz expression is expected; (3) ambiguous DOM/DOW in Quartz — if you specify both fields, use ? in the one that should be unrestricted. Use the tester above to confirm the next run times before deploying.
Is this cron expression generator online free and private?
Completely. This cron expression generator online runs entirely in your browser. No expressions, schedules, or any other data are sent to a server or stored anywhere. You can use it as many times as you need with no account, no sign-up, and no cost.
5 Tips for Writing Reliable Cron Schedules
- Always test in UTC first. Almost every cloud platform executes cron jobs in UTC. Build and validate your schedule in UTC using the tester above, then account for your local offset when communicating run times to stakeholders.
- Avoid the "midnight stampede". If you have many jobs scheduled at exactly
0 0 * * *, they all compete for resources at the same instant. Stagger them: 0 0 * * *, 5 0 * * *, 10 0 * * *.
- Use named days and months in Quartz. Writing
MON-FRI instead of 1-5 makes the intent obvious to anyone reading the config six months later.
- Set sensible retry and timeout policies. A cron expression defines when a job starts, not how long it can run. Set execution timeouts so a slow job does not overlap with the next scheduled run.
- Document every schedule in code comments. Above each cron expression in your codebase, add a comment with the human-readable equivalent. This tiny habit saves enormous debugging time when an unexpected execution is investigated weeks later.
More Developer Tools on EzyToolbox
Everything you need for backend and DevOps work — no installs, no sign-ups.