GitHub Actions cron time zone converter

GitHub Actions reads a cron schedule in UTC unless you add timezone: with an IANA zone name under the cron line, which GitHub.com supports. Without it, 9:00 in New York is 0 14 * * * in winter and 0 13 * * * in summer. Pick your time and zone to get both versions.

Free, and it runs in your browser: nothing you type here is sent anywhere.

Days (none selected means every day)

Schedule: 09:00 Mon, Tue, Wed, Thu, Fri in America/New_York

GitHub.com, GitHub Enterprise Cloud, GHES 3.22 and later

Keep the cron in local time and add the timezone key. GitHub follows the zone through daylight saving changes.

on:
  schedule:
    - cron: '0 9 * * 1-5'
      timezone: 'America/New_York'
  workflow_dispatch:

UTC only (GHES before 3.22, or any tool that reads cron in UTC)

0 14 * * 1-5
Runs at 14:00 UTC while America/New_York is at UTC-05:00 (Jan 1 to Mar 7 and Nov 1 to Dec 31, 2026)
0 13 * * 1-5
Runs at 13:00 UTC while America/New_York is at UTC-04:00 (Mar 8 to Oct 31, 2026)
  • America/New_York changes its UTC offset during 2026, so no single UTC cron line keeps 09:00 local all year. Listing both lines makes the workflow fire twice a day, once at the right time and once an hour off, so the UTC YAML below adds a check job that lets only the line matching today's offset continue.
on:
  schedule:
    - cron: '0 14 * * 1-5' # UTC-05:00, Jan 1 to Mar 7 and Nov 1 to Dec 31
    - cron: '0 13 * * 1-5' # UTC-04:00, Mar 8 to Oct 31
  workflow_dispatch:

jobs:
  check:
    runs-on: ubuntu-latest
    outputs:
      run: ${{ steps.offset.outputs.run }}
    steps:
      - id: offset
        env:
          SCHEDULE: ${{ github.event.schedule }}
        run: |
          now=$(TZ='America/New_York' date +%z)
          case "$SCHEDULE|$now" in
            '0 14 * * 1-5|-0500'|'0 13 * * 1-5|-0400'|'|'*) echo "run=true" >> "$GITHUB_OUTPUT" ;;
            *) echo "run=false" >> "$GITHUB_OUTPUT" ;;
          esac
  main:
    needs: check
    if: needs.check.outputs.run == 'true'
    runs-on: ubuntu-latest
    steps:
      - run: echo "Your steps go here"

How to schedule a workflow in your own time zone

  1. Choose the local time you want the workflow to run and your time zone.
  2. Select the days of the week, or leave them all off for every day.
  3. On GitHub.com, copy the YAML with the timezone key into the on: section of your workflow file.
  4. On a server without the timezone key, copy the UTC YAML instead. If your zone has daylight saving, keep the check job so only one of the two lines runs each day.
  5. Hit the delay problem anyway? Read why GitHub Actions cron runs late.

What GitHub documents about scheduled workflows

  • Schedules use POSIX cron syntax and run in UTC by default.
  • An optional timezone key takes an IANA zone name, on GitHub.com, GitHub Enterprise Cloud and GitHub Enterprise Server 3.22 and later.
  • With a daylight saving zone, a run in a skipped spring hour moves to the next valid time.
  • The shortest interval is once every 5 minutes.
  • Runs start from the latest commit on the default branch.
  • The github.event.schedule context holds the cron line that started the run.
  • High load can delay a run, and some queued jobs may be dropped.
  • Scheduled workflows in public repositories are disabled after 60 days with no repository activity.

Source: GitHub Docs, Events that trigger workflows, schedule (checked November 2026). Want to read a cron line instead of writing one? Use the cron expression explainer.

Questions

What time zone does a GitHub Actions cron use?

UTC by default. GitHub.com, GitHub Enterprise Cloud and GitHub Enterprise Server 3.22 and later also accept a timezone key with an IANA name such as America/New_York under the cron line, and the schedule then runs in that zone.

How does daylight saving work with the timezone key?

GitHub keeps the run at the same local time across the change. If the time falls in the hour that clocks skip in spring, GitHub documents that the run moves to the next valid time, so 2:30 becomes 3:00. The docs do not say what happens in the hour that repeats in autumn.

My GitHub Enterprise Server only reads UTC. How do I handle daylight saving?

List one UTC cron line per offset and add a job that compares github.event.schedule with the zone's current offset, so only the line that matches today continues. Listing both lines without that check runs the workflow twice a day. The UTC output above includes the check job.

Why did my scheduled workflow run late or not at all?

GitHub queues scheduled runs on shared capacity and can delay them at busy times, or drop some when load is high, and the timezone key does not change that. Scheduled workflows also only run from the default branch, and in public repositories they are disabled after 60 days without repository activity.

Why did the day of the week change in my UTC cron?

If the UTC time falls on the other side of midnight from your local time, the day shifts with it. Monday 02:00 in Tokyo is Sunday 17:00 UTC, so the day field becomes 0. The converter shifts it for you. With the timezone key you keep your local day.

What is the shortest interval GitHub Actions allows?

Once every 5 minutes, whether or not the schedule sets a time zone.

Need the run to start on time, not just in the right zone?

The timezone key fixes the hour, but GitHub can still start scheduled runs late or drop them when it is busy. RunLater calls your endpoint or a workflow dispatch URL at the exact time in the zone you pick, follows daylight saving, retries failures, and logs every run.

Starter is $15/month for 250 scheduled requests and 25,000 runs. Cancel before day 14 and you pay nothing.