What timezone does GitHub Actions schedule run in?

All GitHub Actions scheduled triggers evaluate exclusively in UTC (Coordinated Universal Time). Convert your local time to UTC before configuring the cron expression.

Updated: August 2026 • Verified v1.2

Crontab to GitHub Actions Workflow Schedule Converter

Developer ToolsHigh Usage

Local Browser Execution: Your input is processed locally in your browser and is not sent to UTL servers.

Workflow Synthesis: on.schedule: - cron: '[m h dom mon dow]' + workflow_dispatch

Was this calculation helpful?

Understanding Your Results

Generates complete `.github/workflows/` YAML workflow files with `on.schedule: - cron: '...'`, includes manual `workflow_dispatch` triggers, and enforces GitHub's 5-minute minimum frequency requirement.

Practical Guidance & Next Steps

GitHub Actions schedules evaluate exclusively in UTC. During periods of high load across GitHub, scheduled workflows may experience slight queue delays.

What is this?

A CI/CD automation utility that translates Linux crontabs into GitHub Actions scheduled workflow YAML files.

How does it work?

1. Enter a crontab expression, workflow name, and run command. 2. Validates execution frequency against GitHub limits. 3. Copy the production `.github/workflows/scheduled-job.yml` file in 1 click.

Why use it?

Prevents CI/CD configuration bugs and ensures scheduled automation runs reliably on GitHub.

Technical Scope & Calculation Limitations

Translates standard 5-part POSIX cron syntax into GitHub Actions YAML.

Frequently Asked Questions

No. GitHub Actions limits scheduled workflows to run no more frequently than once every 5 minutes (`*/5 * * * *`). Higher frequency requests will be queued or dropped by GitHub's scheduler.

Windows Desktop & Widget Options