Pick when a job should run and get the cron expression — or paste an expression to see what it means in plain English and exactly when it will run next.
Scheduled jobs are the backbone of automation. Pyalm designs reliable automated workflows — reports, reminders, data syncs and approvals that run themselves.
A standard cron expression has five fields: minute, hour, day of month, month and day of week. Each accepts a value, a list (1,15), a range (1-5), a step (*/10) or * for every value. The builder writes the syntax for you and the preview shows the real run times, so there are no surprises at 3 a.m.
Cron runs in the time zone of the server or scheduler — often UTC on cloud platforms. A job set for 0 9 * * * fires at 9:00 UTC, which is 1 p.m. in Dubai and 2:30 p.m. in India. The next-run preview lets you check both.
📖 Read the full guide: Cron Expression Syntax: A Plain-English Guide with Examples
Convert Unix timestamps to dates and back — seconds or milliseconds, any time zone.
Compare times across cities and find a meeting slot that works — Dubai, India, London, New York and more.
Format, validate, minify and syntax-highlight JSON — with exact error line and column.
A step value: every 5th unit. */5 in the minute field means every five minutes (0, 5, 10 … 55).
In standard cron, if both fields are restricted the job runs when either matches. 0 9 1 * 1 runs at 9:00 on the 1st of every month and on every Monday.
Standard crontab has no seconds field. Some schedulers (Quartz, Spring) add a sixth seconds field; this tool uses the standard five-field format used by Linux, Kubernetes, GitHub Actions and most cloud schedulers.
Both work in most implementations. 0 and 7 both mean Sunday; 1 is Monday.