Cron Expression Tool

Parse, build, and validate cron expressions with real-time feedback. Visual builder, presets, next execution times with timezone support.

"Every minute"

MinuteHourDayMonthWeekday
Quick Presets
Syntax
*any value
,value list separator
-range of values
/step values
@yearly(non-standard)
@monthly(non-standard)
@weekly(non-standard)
@daily(non-standard)
@hourly(non-standard)
4.6(71 votes)
Try also: Base64 Encoder/Decoder
Run Check

Key Features

100% Free

No registration required, unlimited checks

Instant Results

Real-time analysis with detailed output

REST API Access

Integrate into your workflow via API

Accurate Data

Live queries to authoritative sources

What is Cron Expression Tool?

The Cron Expression Tool helps you create, understand, and validate cron schedule expressions used across the entire DevOps ecosystem: Linux crontab, Kubernetes CronJobs, GitHub Actions schedules, GitLab CI, AWS EventBridge, Google Cloud Scheduler, and virtually every task automation system. It parses any standard 5-field cron expression (minute, hour, day-of-month, month, day-of-week) into a clear human-readable description, shows the next 10 execution times in your selected timezone so you can verify the schedule is correct, and offers a visual point-and-click builder for constructing expressions without memorizing cron syntax. The tool also includes common presets (every minute, hourly, daily at midnight, weekly, monthly) for quick access to the most-used schedules.

This free cron expression generator and tester is used by DevOps engineers scheduling automated tasks, backend developers setting up recurring jobs, system administrators managing crontab entries, and CI/CD pipeline builders configuring scheduled workflows.

How to Use

  1. 1Enter a cron expression in the 5 fields or use a preset
  2. 2Read the human-readable description that updates in real time
  3. 3Switch to Builder mode to visually select minutes, hours, days
  4. 4Check the next 10 execution times and adjust the timezone

Who Uses This

System Administrators

Monitor and troubleshoot infrastructure

Developers

Debug network issues and integrate via API

SEO Specialists

Verify domain configuration and performance

Security Analysts

Audit and assess network security

Frequently Asked Questions

What is a cron expression and where is it used?
A cron expression is a string of 5 space-separated fields that defines a recurring schedule: minute (0-59), hour (0-23), day of month (1-31), month (1-12), and day of week (0-7, where 0 and 7 are Sunday). It originated in Unix systems for the crontab scheduler and is now used everywhere: Linux crontab, Kubernetes CronJobs, GitHub Actions 'schedule' trigger, GitLab CI, AWS EventBridge/CloudWatch, Google Cloud Scheduler, Azure Functions Timer Trigger, Vercel Cron, and most backend task scheduling libraries in any programming language.
What do the special characters *, /, -, and , mean in cron?
The asterisk (*) means 'every possible value' — * in the hour field means every hour. Slash (/) defines step values — */15 in the minute field means every 15 minutes (0, 15, 30, 45). Hyphen (-) defines ranges — 1-5 in the day-of-week field means Monday through Friday. Comma (,) creates lists — 1,15 in the day-of-month field means the 1st and 15th. You can combine these: 10-50/10 means every 10 minutes starting from minute 10 (10, 20, 30, 40, 50).
How do I schedule a cron job every 5 minutes?
Use the expression */5 * * * * — the */5 in the minute field means 'every 5th minute starting from 0'. This runs at :00, :05, :10, :15, :20, :25, :30, :35, :40, :45, :50, :55 of every hour, every day. Other common intervals: every minute is * * * * *, every 15 minutes is */15 * * * *, every hour is 0 * * * *, every day at midnight is 0 0 * * *, every Monday at 9am is 0 9 * * 1.
What is the difference between 5-field and 6-field cron expressions?
Standard (POSIX) cron uses 5 fields: minute, hour, day-of-month, month, day-of-week. Some systems add a 6th field for seconds (at the beginning) or year (at the end). AWS CloudWatch uses 6 fields with year. Spring Framework uses 6 fields with seconds. Kubernetes CronJobs use standard 5 fields. This tool works with the standard 5-field format which is compatible with the vast majority of cron implementations.
How do I test if my cron expression is correct?
Enter your expression in this tool and check three things: the human-readable description (does it match what you intended?), the next 10 execution times in your timezone (do they fall when you expect?), and verify the timezone is set correctly (cron runs in the server's timezone, which may differ from yours). Common mistakes: confusing day-of-week numbering (0=Sunday in some systems, 1=Monday in others), forgetting that month and day-of-week fields interact with OR logic (not AND), and using the wrong timezone.

Related Tools

Base64 Encoder/Decoder

URL Encoder/Decoder

Hash Generator

JSON Formatter & Validator

Popular Tools

DNS Lookup

WHOIS Lookup

Domain Age

Nameserver Checker

API Endpoint

POST
View Documentation