Regex and cron

Cron Expression for Every Weekday

At 00:00 on Monday, Tuesday, Wednesday, Thursday and Friday. Copy it, check the next runs in your time zone and grab a snippet for your platform.

  • Free foreverNo trial, no paywall, no usage limits.
  • No sign-upOpen the page and start. We never ask for an email to use a tool.
  • PrivateEverything runs in your browser. Your input is never uploaded or stored on our servers.
  • Works offlineOnce the page has loaded, the tool keeps working without a connection.

Cron expression

0 0 * * 1-5
Customize
0minuteMinute: at minute 0 (on the hour)0hourHour: at hour 0 (midnight)*day (month)Day of month: every day of the month*monthMonth: every month1-5day (week)Day of week: Monday through Friday

At 00:00 on Monday, Tuesday, Wednesday, Thursday and Friday.

Time zone
Run times, the week view and the snippets use this zone. It starts as your device's zone.
Show times as 9:00 AM instead of 09:00.

Next runs

Each run in your selected time zone, with the same moment in UTC. Daylight saving changes follow cronie, the cron on most Linux servers.
Copy run times (ISO 8601)

Next 7 days

Each square is one hour of local time in your selected zone. Darker squares have more runs. Daylight saving changes are not drawn.

Use it on your platform

Copy-ready config for each scheduler. Dialects differ: some only run in UTC, some can't do seconds, Cloudflare and AWS number weekdays from 1 = Sunday. The snippet handles the conversion and says what changed.
A line for crontab -e on Linux or macOS (Vixie cron, cronie).on.schedule for a workflow, with the timezone field GitHub added in March 2026 (UTC when omitted).A CronJob manifest with the timeZone field (Kubernetes 1.27+).Cron Triggers in wrangler.toml for a Worker. Runs in UTC and numbers weekdays from 1 = Sunday.crons in vercel.json plus the route it calls. Runs in UTC.EventBridge Scheduler (any time zone, recommended by AWS) and a legacy EventBridge scheduled rule (UTC).A .timer unit with OnCalendar=, the systemd replacement for cron.
Runs as writtenRuns in your time zone
crontab -e
Copy crontab -eDownload my-job.crontab
# ┌───────────── minute (0–59)
# │ ┌─────────── hour (0–23)
# │ │ ┌───────── day of month (1–31)
# │ │ │ ┌─────── month (1–12)
# │ │ │ │ ┌───── day of week (0–6, Sunday = 0)
# │ │ │ │ │
# * * * * *  command
CRON_TZ=UTC
0 0 * * 1-5  /path/to/my-job.sh >> /var/log/my-job.log 2>&1
  • CRON_TZ=UTC is honored by cronie (Fedora, RHEL, Arch). Other cron daemons ignore it and use the server's time zone, so check timedatectl first.
  • Edit with crontab -e. Cron starts the next run even if the last one is still going; wrap the command in flock -n /tmp/my-job.lock to prevent overlaps.

Need scheduled jobs, queues and monitoring that never miss a run? Talk to our team

Quick answer

The cron expression for every weekday is 0 0 * * 1-5. The day-of-week field 1-5 is a range from Monday (1) to Friday (5), and the first two fields run it at 00:00. Saturday (6) and Sunday (0 or 7) are skipped. To run at another time on weekdays, change the minute and hour, for example 0 9 * * 1-5 for 9 AM.

  • Live next runs
  • Any time zone
  • Field-by-field breakdown
  • Seven platform snippets
  • Daylight saving aware

How to use this schedule

  1. 1Copy 0 0 * * 1-5 with the Copy expression button.
  2. 2Check Next runs in your time zone to confirm it fires when you expect, including around daylight saving changes.
  3. 3Pick your platform under Use it on your platform and copy the ready-made crontab line, workflow, manifest or timer.
  4. 4Need a different time or day? Click Customize to open it in the cron expression generator and change any field.

How does cron number the days of the week?

The fifth field accepts 0 to 7, plus three-letter names:

DayNumberName
Sunday0 or 7SUN
Monday1MON
Tuesday2TUE
Wednesday3WED
Thursday4THU
Friday5FRI
Saturday6SAT

So 1-5 covers Monday through Friday, inclusive at both ends. In crontab you can write the same thing with names, MON-FRI, in any letter case, which reads better in a code review. Neither form travels everywhere: some schedulers, Vercel among them, only accept numbers, while AWS EventBridge, Quartz and Cloudflare Workers count Sunday as 1, so their weekdays are 2-6 and a copied 1-5 runs Sunday to Thursday. Check the target's numbering, and use names where they are accepted.

Is midnight the right time for a weekday job?

0 0 * * 1-5 fires at the very start of each weekday. The Monday run happens in the first minute of Monday, and the last run of the week is at 00:00 on Friday, not on Friday evening. That is ideal for jobs that prepare the working day: building reports before people log in, rotating an on-call schedule or opening a new batch. If something should happen at the end of each working day instead, use 0 18 * * 1-5 or similar, and remember that a Friday-night job belongs to Friday (5), while anything after midnight on Friday night is already Saturday (6) and won't match.

What does each field in 0 0 * * 1-5 mean?

FieldValueAllowedMeaning
Minute00–59at minute 0 (on the hour)
Hour00–23at hour 0 (midnight)
Day of month*1–31every day of the month
Month*1–12, JAN–DECevery month
Day of week1-50–7 (0 and 7 are Sunday), SUN–SATMonday through Friday

Read together: At 00:00 on Monday, Tuesday, Wednesday, Thursday and Friday.

How do I adjust 0 0 * * 1-5 to my own schedule?

Small edits to 0 0 * * 1-5 cover most real-world needs:

ExpressionWhat it does
0 9 * * 1-59 AM on weekdays
0 0 * * MON-FRIThe same schedule written with day names
*/15 9-17 * * 1-5Every 15 minutes during business hours on weekdays
0 18 * * 1-56 PM at the end of each working day
0 0 * * 6,0Midnight on weekends instead

Need something else? Click Customize at the top of the page to open this schedule in the cron expression generator and change any field.

Related schedules: Every weekday at 9am · Every weekend · Business hours (every hour) · Every Monday

Browse all schedules in the cron schedule library.

How do I run 0 0 * * 1-5 in crontab, GitHub Actions, Kubernetes and the cloud?

PlatformWrite it asTime zone
Linux crontab0 0 * * 1-5Server's time zone; CRON_TZ= in cronie
GitHub Actions- cron: "0 0 * * 1-5"UTC by default; add timezone: (IANA name)
Kubernetes CronJobschedule: "0 0 * * 1-5"Set timeZone: (1.27+)
Cloudflare Workers0 0 * * MON-FRIUTC only; numbers weekdays from 1 = Sunday, so use names
Vercel Cron Jobs0 0 * * 1-5UTC only; Hobby runs it within the hour (±59 min)
AWS EventBridge Schedulercron(0 0 ? * MON-FRI *)Takes a time zone; legacy scheduled rules are UTC only
systemd timerOnCalendar=Mon..Fri *-*-* 00:00:00Add a zone after the time, e.g. Europe/London

In a crontab (crontab -e), the full line looks like this:

0 0 * * 1-5  /path/to/job.sh >> /var/log/job.log 2>&1

The live panel at the top of the page builds complete, copy-ready files for each platform (workflow, CronJob manifest, wrangler.toml, vercel.json, AWS CLI and systemd units) and can shift the schedule to UTC for platforms that need it.

What can go wrong with 0 0 * * 1-5?

  • 1-5 means Monday to Friday only in cron numbering. In AWS EventBridge, Quartz and Cloudflare Workers, Sunday is 1, so the same range runs Sunday to Thursday.
  • Public holidays are still weekdays. Cron has no holiday calendar, so have the job check a holiday list if it must skip them.
  • Ranges can't wrap around the end of the week: 5-1 (Friday to Monday) is invalid. Write a list such as 5,6,0,1 instead.
  • A weekday job at 00:00 UTC runs on Sunday evening in the Americas, so the first run of the week happens before Monday starts there.
  • On UTC-only platforms (Cloudflare Workers, Vercel, legacy EventBridge rules), the local time this runs at moves by an hour when daylight saving time starts or ends. Use GitHub's timezone:, Kubernetes timeZone, EventBridge Scheduler or cronie's CRON_TZ to pin it to local time.

Frequently asked questions

0 0 * * 1-5 runs at midnight Monday through Friday. Change the first two fields for a different time, such as 0 9 * * 1-5 for 9 AM.
Yes. Crontab accepts three-letter day names in any letter case, so mon-fri works the same as 1-5. No form works everywhere: Vercel only accepts numbers, while Cloudflare Workers and AWS EventBridge read 1-5 as Sunday to Thursday, so names are safer there.
Yes. Cron ranges include both ends, so 1-5 covers Monday, Tuesday, Wednesday, Thursday and Friday.
Cron can't do it by itself. Keep the 1-5 schedule and have the job check a holiday list or calendar at startup, then exit early on a holiday.

Last updated by the Playxoft engineering team.

From the engineers who built this tool

Need scheduled jobs that never miss a run?

Cron is the easy part. Retries, overlapping runs, time zones, queues and alerts when a job silently stops are where schedules break. We build background job systems you can trust, and we will review your setup for free.

Get a free job-scheduling reviewSee backend services

More free tools

See all tools

Regex Tester

Test regex live with highlighted matches, plain-English explanations and code export.

Open tool

Cron Expression Generator

New

Build and explain cron schedules, see the next runs in any time zone, copy platform snippets.

Open tool

SQL Formatter

Beautify or minify SQL in 12 dialects, with keyword case, indent and line:column errors.

Open tool

cURL to Python Converter

New

Convert cURL commands into Python requests or httpx code with params, json, files and auth.

Open tool

cURL to Fetch Converter

New

Turn any cURL command into JavaScript fetch() code with headers, JSON, forms and auth.

Open tool

cURL to Axios Converter

New

Convert cURL commands into an Axios request config with params, data, auth and timeouts.

Open tool