Regex and cron

Cron Expression for Every Weekday at 9 AM

At 09:00 on every weekday, Monday through 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 9 * * 1-5
Customize
0minuteMinute: at minute 0 (on the hour)9hourHour: at hour 9 (9 AM)*day (month)Day of month: every day of the month*monthMonth: every month1-5day (week)Day of week: Monday through Friday

At 09:00 on every weekday, Monday through 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 9 * * 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 at 9am is 0 9 * * 1-5. Minute 0 and hour 9 set the time to 09:00, and 1-5 in the day-of-week field limits it to Monday through Friday, while the day-of-month and month fields stay as asterisks. It runs five times a week, at 9 AM in the time zone of whatever evaluates the schedule.

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

How to use this schedule

  1. 1Copy 0 9 * * 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 do I run a cron job at 9am on weekdays in my time zone?

The expression is the easy part; the time zone is where this schedule usually breaks. 0 9 * * 1-5 means 09:00 in the scheduler's zone, and several popular schedulers default to UTC or only support it. For a team in New York:

PeriodNew York offsetUTC expression for 9 AM local
Daylight saving time (March to November)UTC−40 13 * * 1-5
Standard time (November to March)UTC−50 14 * * 1-5

One UTC expression can't follow the clock change, so you have three options:

  1. Use a scheduler with a time zone setting: GitHub Actions with timezone: America/New_York next to the cron line, a Kubernetes CronJob with timeZone, AWS EventBridge Scheduler, systemd with a zone in OnCalendar, or cronie with CRON_TZ.
  2. Update the UTC expression twice a year, and accept being an hour off if you forget.
  3. Run at both candidate UTC hours (0 13,14 * * 1-5) and let the job exit unless the local hour in New York is 9.

Why is 9am on weekdays such a popular schedule?

It lines up with the start of the working day, so its output is fresh when people arrive: a stand-up digest in Slack, a report of yesterday's signups, a reminder about overdue invoices or a check that last night's backups finished. Because the audience is human, timing errors are noticed immediately, which is why the time zone question matters more here than for a backup nobody watches. If the job sends anything to people, make it idempotent so a manual rerun after a failure doesn't send duplicates.

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

FieldValueAllowedMeaning
Minute00–59at minute 0 (on the hour)
Hour90–23at hour 9 (9 AM)
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 09:00 on every weekday, Monday through Friday.

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

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

ExpressionWhat it does
0 13 * * 1-59 AM New York time during daylight saving time, written in UTC
0 14 * * 1-59 AM New York time during standard time, written in UTC
30 8 * * 1-58:30 AM on weekdays
0 9 * * 19 AM on Mondays only
0 9,17 * * 1-59 AM and 5 PM on weekdays

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 · Every day at 9am · Business hours (every hour) · Every Friday at 5pm

Browse all schedules in the cron schedule library.

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

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

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

0 9 * * 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 9 * * 1-5?

  • Cloudflare Workers and Vercel only evaluate schedules in UTC, and GitHub Actions does too unless you add timezone:. A plain 0 9 * * 1-5 there runs at 09:00 UTC, which is 4 or 5 AM in New York.
  • Converting to UTC can move the weekday as well as the hour. 9 AM Monday in Sydney is Sunday evening in UTC, so the expression becomes 0 23 * * 0-4 (or 0 22 * * 0-4 during Australian daylight saving time).
  • Public holidays are still weekdays to cron. If a digest shouldn't go out on a holiday, check a holiday calendar in the job and exit early.
  • Several 09:00 jobs on one server start in the same second. Stagger them by a minute or two if they share a database or a rate-limited API.
  • 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 9 * * 1-5. It runs at 09:00 on Monday, Tuesday, Wednesday, Thursday and Friday in the scheduler's time zone.
Use 0 13 * * 1-5 while New York is on daylight saving time (UTC minus 4) and 0 14 * * 1-5 during standard time (UTC minus 5). A single UTC expression cannot follow the clock change.
Yes. Cron knows weekdays, not holidays. Add a holiday check to the job itself if it should skip them.
Yes. A schedule entry can carry a timezone field with an IANA name such as America/New_York next to its cron line, and GitHub then follows daylight saving time for you. Without it the schedule runs in UTC. Scheduled runs can still start late during busy periods.

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