⭐ 0
🔍
Text Image PDF & Docs Audio Music Electronics Time Utilities Validators Esoteric Games

Cron Job Every Monday — 0 0 * * 1

Build cron expressions with dropdowns and instantly see a plain-language schedule plus the next 5 real run times.

Processing... 0%

Result

This page opens the builder preloaded with 0 0 * * 1 — one run per week, at midnight on Monday. The final field is the day of week, where 0 is Sunday, 1 is Monday, and so on through 6 for Saturday; most cron implementations also accept 7 as another Sunday.

Weekly Monday jobs are typical for business-cycle work: weekly summary e-mails, sales or analytics reports covering the previous week, archive rotation and batch housekeeping that would be too heavy nightly. Prefer a different hour? Change the hour field — for example 0 9 * * 1 sends your report at 09:00 Monday morning instead of midnight.

One trap to know: if you also restrict the day-of-month field, POSIX cron treats the two day fields as OR, not AND — 0 0 1 * 1 runs on the 1st of the month AND on every Monday, not only on Mondays that fall on the 1st. This builder implements the same rule, so the next-run list always reflects what a real crontab would do.

🛡️
Executed in Browser

Your files and inputs never leave this device. Processing runs completely offline. 100% Secure.

Accepted Formats & Rules

  • Per-field builders for minute, hour, day of month, month and day of week: every value, every N, or specific lists and ranges (0,30 or 9-17).
  • Live human-readable explanation of the schedule with localized month and weekday names.
  • Next 5 run times computed with real calendar math, including the POSIX day-of-month OR day-of-week rule.

Key Benefits

✓ No syntax to memorize: choose 'every', 'every N' or specific values per field and the five-part cron expression assembles itself.
✓ Instant feedback — a plain-language description and the next 5 computed run times show whether the schedule really does what you meant.
✓ Runs entirely in your browser and works offline, so server schedules and job names never leave your machine.

Use Cases

  • • Build the cron expression for a nightly backup job without memorizing the five-field syntax.
  • • Verify when a schedule will actually fire by reviewing the next five computed run times before deploying it.
  • • Turn 'every weekday during business hours' into a valid crontab line for a monitoring script.