Skip to content
CrateX.app logo

CrateX.app

Cron Expression Parser

Parse and validate 5-, 6-, and 7-field cron expressions locally, inspect the field breakdown, preview timezone-aware next runs, read a human-readable description, use presets, and copy the current expression for crontab, CI/CD, and scheduled jobs.

Cron Expression

Every 5 minutes, every hour, every day

Common Presets

Field Breakdown

*/5

Minute

0, 5, 10, 15, 20, 25, 30, 35, 40, 45…

*

Hour

All

*

Day

All

*

Month

All

*

Weekday

All

Next Executions

Timezone

Local Time · UTC

No upcoming executions found within 4 years.
Cron Expression Parser

Quick Start

1
Enter a cron expression or choose a preset
2
Choose the timezone for next runs
3
Review description, fields, and next runs
4
Copy the current cron expression

Common Scenarios

CI/CD pipelines

validate cron schedules for GitHub Actions / GitLab CI

Linux crontab

verify your cron syntax before deploying

Kubernetes CronJobs

simulate execution times to verify scheduling

Monitoring alerts

plan check intervals to balance coverage and cost

Usage Advice

Standard cron uses 5 fields (minute hour day month weekday). The 6-field format adds seconds at the beginning, the 7-field format adds a numeric year at the end, and day / weekday fields support ? as a no-specific-value placeholder.
Weekday: 0 = Sunday, 1 = Monday, …, 6 = Saturday; names like MON-FRI also work
Execution times are calculated in the selected timezone. Switching zones also changes DST behavior.

URL Quick Fill

Prefill the cron parser from the URL hash. expression is required; timezone stays on the tool's current default or saved setting.
expression: Cron expression
Example: #expression=*/15%20*%20*%20*%20*
Hash parameters stay in the browser for tool prefill; CrateX.app does not record them.
Do not put private schedule names, tokens, or other sensitive data in URLs.

Limitations & Compatibility

Special characters L, W, # (Quartz-style) are not supported
Year field is supported only as a numeric value from 1970-2099. Advanced Quartz tokens like L, W, and # are still not supported.
Cron macros such as @daily or @reboot, Jenkins H, TZ= lines, command parts, environment variables, full crontab files, platform YAML, and workflow exports are not supported.
This page previews schedules only; it does not run jobs, connect to production schedulers, monitor missed runs, or send monitoring alerts.

Privacy & Security

Cron parsing runs in your browser. The cron expression and selected timezone may stay in the current browser session or browser storage. If WebDAV sync is enabled, the expression and selected timezone may sync according to your settings. Field breakdown, readable description, and next run times are recalculated from the current expression and timezone, not stored as separate results. The page does not read crontab files, execute commands or jobs, connect to scheduler platforms, fetch URLs for parsing, or send the expression for server-side parsing. On shared devices, clear the expression, timezone, and site data when needed.

FAQ

5

Continue with these related tools for the next step.

About

About Us
Pricing

Legal

Terms
Privacy Policy
Cookie Policy

Preferences

Manage Cookies

All tool processing happens locally in your browser.