DevCoreTools
DevOps & Config

Cron Expression Parser

Paste a cron expression and instantly see what it means, whether it is valid, and when it will run next.

Unix, Quartz, and Spring cron parserAuto-detects common field counts, lets you override the format, and keeps all processing in your browser.

Cron expression input

Parse Unix 5-field cron, Quartz 6/7-field cron, or Spring 6-field cron.

Processed locally in your browser. Limit Browser-side cron parsing Your input is processed in your browser and is not uploaded or sent to a server. Avoid pasting production secrets, access tokens, private keys, passwords, or sensitive customer data unless you understand the risk.

Examples: */15 * * * *, 0 */15 * ? * *, 0 */15 * * * *.

Common examples

Parsed schedule

Results appear after parsing a valid expression.

No expression parsed yet

Paste a Unix, Quartz, or Spring cron expression or load a common example.

What is a Cron Expression Parser?

A cron expression parser turns compact schedule syntax into readable timing rules. This parser explains Standard Unix, Quartz, and Spring cron expressions before you edit a server, scheduler, CI job, or automation workflow.

How to read a cron expression

Read Unix cron left to right as minute, hour, day of month, month, and day of week. Quartz and Spring add a leading seconds field, and Quartz can add a seventh year field.

Cron field breakdown

Second0-59 in Quartz and Spring
Minute0-59
Hour0-23
Day of month1-31
Month1-12 or JAN-DEC
Day of week0-7 or SUN-SAT, Sunday is 0 or 7
YearOptional in Quartz

Format-specific fields

Unix uses 5 fields and no seconds. Spring uses exactly 6 fields with seconds first. Quartz uses 6 or 7 fields, supports ? for no specific day value, and allows day-field tokens such as L, W, and #.

Common cron examples explained

  • */5 * * * * runs every 5 minutes.
  • 0 * * * * runs at the start of every hour.
  • 0 9 * * MON-FRI runs at 9:00 AM on weekdays.
  • 0 0 1 * * runs at midnight on the first day of each month.
  • 0 */15 * ? * * is Quartz cron that runs every 15 minutes.
  • 0 */15 * * * * is Spring cron with seconds.

Cron Generator vs Cron Parser

Use the generator when you want to build a schedule from visual controls. Use this parser when you already have an expression and need validation, an explanation, or next-run debugging.

Unix vs Quartz vs Spring cron

Unix cron normally has five fields. Quartz and Spring cron include seconds. Quartz is the profile that may include an optional year and Quartz-only day tokens.

Common cron mistakes

Common issues include using six fields by accident, writing 24 as an hour, using Quartz-only tokens, forgetting the host timezone, or restricting both day fields without knowing Unix cron treats them as alternatives.

Keep working

Cron Expression GeneratorBuild Unix, Quartz, and Spring cron schedules with visual controls and local run previews.Unix Timestamp ConverterConvert Unix timestamps to readable dates and dates back to epoch time.Regex TesterTest patterns, capture groups, flags, and multiple values locally.JSON FormatterFormat, validate, inspect, and export JSON locally.
URL Encoder/DecoderComing soon
Encode and decode URL components and query-string values.

Frequently asked questions

Why does my cron expression have 6 fields?

Six-field cron usually includes seconds first. Spring uses exactly six fields, and Quartz commonly uses six fields when no year is needed.

Why does my cron expression have 7 fields?

A seven-field cron expression is usually Quartz cron with an optional year field at the end.

How do I know if my cron is Unix, Quartz, or Spring?

Five fields usually means Unix. Six fields with Quartz-only tokens such as ? usually means Quartz; six fields without those tokens is often Spring. Seven fields points to Quartz.

Why is my cron expression invalid?

The most common causes are the wrong field count for the selected format, an out-of-range number, Quartz-only syntax in Unix or Spring mode, or a misplaced Quartz day-field token.