Constructor de Expresiones CRON

Construye expresiones CRON visualmente seleccionando minutos, horas, días y meses, o ingresa una expresión para decodificarla. Muestra las próximas 10 ejecuciones y descripción en lenguaje natural.

Cron Format:

* * * * *

Description:Every minute

Minute

Hour

Day of Month

Month

Day of Week

Next 10 Run Times

Show nextruns

1.Mon, Mar 2, 2026, 06:12 AM

2.Mon, Mar 2, 2026, 06:13 AM

3.Mon, Mar 2, 2026, 06:14 AM

4.Mon, Mar 2, 2026, 06:15 AM

5.Mon, Mar 2, 2026, 06:16 AM

6.Mon, Mar 2, 2026, 06:17 AM

7.Mon, Mar 2, 2026, 06:18 AM

8.Mon, Mar 2, 2026, 06:19 AM

9.Mon, Mar 2, 2026, 06:20 AM

10.Mon, Mar 2, 2026, 06:21 AM

Platform Snippets

apiVersion: batch/v1
kind: CronJob
metadata:
  name: my-cronjob
spec:
  schedule: "* * * * *"
  jobTemplate:
    spec:
      template:
        spec:
          containers:
          - name: my-job
            image: my-image:latest
          restartPolicy: OnFailure

¿Tienes una sugerencia?

Solicita una nueva herramienta o sugiere mejoras — ¡únete a nuestra comunidad en Slack!

Dejar feedback en Slack

What is a Cron Expression?

A cron expression is a string of 5 (standard) or 6-7 (Quartz) fields that defines a schedule for automated tasks. Each field represents a time unit — minute, hour, day of month, month, and day of week — using numbers, wildcards (*), ranges (1-5), steps (*/15), and lists (1,3,5). Originally from Unix cron daemon, cron expressions are now used universally across Kubernetes CronJobs, GitHub Actions workflows, AWS EventBridge rules, and CI/CD pipelines. This builder helps you construct, validate, and visualize cron schedules with an interactive calendar heatmap that shows exactly when your jobs will execute — something a text description cannot convey.

How to Use the Cron Expression Builder

Choose your cron format: Standard 5-field for Linux/Kubernetes or Quartz 6/7-field for Java-based schedulers
Use the visual field selectors to set minute, hour, day, month, and weekday values using dropdowns for every, specific, range, or step patterns
Read the auto-generated plain-English description to verify your schedule matches your intent
Switch to Calendar View to see a monthly heatmap of all scheduled executions with exact timestamps
Copy ready-to-paste platform snippets for Kubernetes, GitHub Actions, AWS EventBridge, or Docker crontab
Or browse Quick Templates for common patterns like 'weekdays at 9 AM' or 'every 15 minutes during business hours'
Use the 'Next N Runs' panel to confirm upcoming execution times match your expectations

Frequently Asked Questions

What is the difference between standard cron and Quartz cron expressions?

Standard (Unix/Linux) cron uses 5 fields: minute, hour, day-of-month, month, day-of-week. Quartz cron (used in Java frameworks like Spring and Quartz Scheduler) adds a seconds field at the beginning and optionally a year field at the end, making it 6-7 fields total. Quartz also supports additional special characters like 'L' (last), 'W' (weekday), and '#' (nth day of week). This builder supports both formats with a simple toggle.

How do I schedule a cron job to run every weekday at 9 AM?

Use the expression '0 9 * * 1-5' for standard cron, which means: minute 0, hour 9, any day of month, any month, Monday through Friday (1-5). In Quartz format, it would be '0 0 9 ? * MON-FRI'. You can set this up in the builder by selecting 'Specific: 0' for minute, 'Specific: 9' for hour, and 'Range: 1-5' for day of week, or simply click the 'Weekdays at 9 AM' quick template.

What does the asterisk (*) mean in a cron expression?

The asterisk (*) is a wildcard that means 'every possible value' for that field. For example, * in the hour field means 'every hour' (0-23), and * in the day-of-month field means 'every day' (1-31). Combined with step values like */5, it means 'every 5th value' — so */15 in the minute field means 'every 15 minutes' (at 0, 15, 30, 45 minutes past the hour).

How can I visualize when my cron job will actually run?

This builder's Calendar View shows a monthly heatmap where each day is color-coded by the number of executions. Click any day to see exact timestamps of every scheduled run. This visual approach makes it easy to spot errors — for example, you can immediately see if a job runs on weekends when it shouldn't, or if there are unexpected gaps in the schedule.

Can I use cron expressions in Kubernetes and GitHub Actions?

Yes. Kubernetes CronJob uses standard 5-field cron syntax in the 'schedule' field of the YAML spec. GitHub Actions uses the same 5-field syntax in the 'cron' key under 'on.schedule'. AWS EventBridge uses a slightly modified 6-field format. This builder generates ready-to-paste snippets for all three platforms, so you can copy the correct YAML or JSON directly into your configuration files.