Schedule a backup
Choose a daily UTC time to avoid confusion with your device’s time zone. Configure the command and its server permissions separately.
Create and inspect standard five-field cron expressions directly in your browser. Use presets or enter an expression, read a plain-language explanation and preview upcoming runs.
Standard order: minute, hour, day of month, month, day of week. minute hour day-of-month month day-of-week
Enter a valid standard five-field cron expression.
Build a five-field cron expression and inspect upcoming dates before adding it to a scheduler. An expression selects calendar minutes rather than a fixed elapsed delay between runs. The preview is calculated in your browser using either your device’s local time or UTC. It installs no program, saves no scheduled job and runs no command. Check that your destination service uses the same dialect and time zone before relying on the schedule.
The fields are minute, hour, day of month, month and day of week, in that order. Their ranges are 0–59, 0–23, 1–31, 1–12 and 0–7. Sunday accepts 0 or 7. English abbreviations JAN to DEC and SUN to SAT are supported. An asterisk selects every value, commas combine values, a hyphen describes a range, and a slash supplies a step over a range or *.
Steps refer to positions within a field: */15 in minutes selects 0, 15, 30 and 45 even when you request the preview at 09:07. When both day fields are restricted, the tool uses their union, following traditional cron. Therefore 0 9 1 * MON means the first of every month and Mondays, rather than only months whose first day is Monday.
Searching starts at the next minute and covers approximately five years at most. An impossible combination such as 31 February with no other matching day produces no occurrence. The interface shows up to five results. Local daylight saving changes may skip or repeat an hour; this preview does not promise the same catch-up policy as your scheduler. Seconds, years, @daily macros and Quartz extensions ?, L, W and # are unsupported.
Choose a preset and adjust it, or type the calendar expression. Leave out the username and command found in a full crontab line.
Select UTC or browser local time. This page cannot infer which time zone your server will use.
Analyze the rule and check dates across month boundaries. An accepted expression still needs checking against your destination scheduler’s documentation.
Choose a daily UTC time to avoid confusion with your device’s time zone. Configure the command and its server permissions separately.
Inspect upcoming weekday dates before copying a rule into configuration. Monday to Friday is not a holiday-aware business calendar.
Compare a step in the minute field with a specific minute each hour. Every fifteen minutes and minute fifteen of every hour describe different schedules.
Starting at 09:07 UTC on 21 October 2026, the next two runs are 09:15 and 09:30. The step starts from the field boundary, not from the time of your request.
Input
*/15 * * * *; 2026-10-21T09:07:00Z; UTCResult
2026-10-21T09:15:00.000Z
2026-10-21T09:30:00.000ZFrom midnight UTC on 21 October 2026, the next dates are Monday 26 October and Sunday 1 November, both at 09:00.
Input
0 9 1 * MON; 2026-10-21T00:00:00Z; UTCResult
2026-10-26T09:00:00.000Z
2026-11-01T09:00:00.000ZThis tool expects five fields without seconds or a year. Some services use six or seven fields; adapt to their dialect rather than deleting an arbitrary field.
If both are restricted, either one can match. When one starts with *, the other restricts the dates together with any step on the starred field.
No. It uses UTC or your browser’s time zone. Match that choice to the execution service, particularly around daylight saving changes.
No. It predicts a calendar match. Service availability, permissions, machine downtime and catch-up policies belong to the execution environment.
Related tools
Tools similar or complementary to this one.
Add up the hours you worked this week, breaks deducted, in hours and minutes and in decimal hours.
Calculate the time between two dates in years, months and days, in total days and in weeks.
Encode or decode common HTML entities to convert special characters in text.
Understand ISO 8601 week numbers, Unix timestamps in seconds or milliseconds, and the difference between human-readable dates and technical time values.