Cron parser

crontab -e language: minute hour day month weekday. Paste a six-field Spring expression and the preview will be wrong.

A deploy ticket says 15 3 * * 1-5 and someone asks “is that London or UTC.” This page parses five fields and previews in UTC. It is not systemd OnCalendar= and not Quartz.

Chinese and Java teams hit this constantly: a Linux line pasted into Spring throws “must consist of 6 fields.” Add a seconds field there — do not expect this preview to match.

JSON schedules and app crons still belong in the app. Timestamps of a single instant are timestamp converter.

Five fields, not Spring’s six

Linux crontab is minute hour day month weekday. Spring @Scheduled usually wants seconds first (six fields). Paste a Unix line into Spring and you get a field-count error — prepend 0, do not trust this preview. We explain UTC next-runs. Quartz ? / L / a year field are out of scope.

How to use it

1. Paste a 5-field expression.
2. Read the English-ish explanation and the next UTC instants.
3. If you needed seconds or ?, use the scheduler’s own docs.

Honest limits

Not a job runner. Not L (last day). Not a guarantee your Kubernetes CronJob timezone field matches.