GitHub Actions Cron Explainer

Paste a five-field cron expression and see what GitHub Actions will run next in UTC and local time.

Also useful for: github actions cron github actions schedule cron github workflow cron GitHub Actions Cron Explainer

GitHub Actions Cron Explainer

Runs in your browser. Inputs are not uploaded.
Input
Results
Summary: 8 upcoming runs previewed. No issues found.

Stats
- Next Runs: 8

Issues
- No issues found.

Output
Schedule
Runs at 00:17, 06:17, 12:17, and 18:17 UTC on Monday through Friday.

Timezone
GitHub Actions evaluates scheduled workflows in UTC. Local times below use this browser's timezone.

Fields
- Minute: 17 minutes past the hour
- Hour: every 6 hours
- Day of month: any calendar day
- Month: every month
- Day of week: Monday through Friday

Next runs
1. Today at 12:17 PM UTC local (Mon, May 18, 12:17 PM UTC)
2. Today at 6:17 PM UTC local (Mon, May 18, 6:17 PM UTC)
3. Tomorrow at 12:17 AM UTC local (Tue, May 19, 12:17 AM UTC)
4. Tomorrow at 6:17 AM UTC local (Tue, May 19, 6:17 AM UTC)
5. Tomorrow at 12:17 PM UTC local (Tue, May 19, 12:17 PM UTC)
6. Tomorrow at 6:17 PM UTC local (Tue, May 19, 6:17 PM UTC)
7. Wed, May 20 at 12:17 AM UTC local (Wed, May 20, 12:17 AM UTC)
8. Wed, May 20 at 6:17 AM UTC local (Wed, May 20, 6:17 AM UTC)

GitHub Actions Cron Explainer Example Run

Preview a weekday scheduled workflow in UTC.

Sample inputs
Cron expression: 17 */6 * * 1-5

Generated result
Summary: 8 upcoming runs previewed. No issues found.

Stats
- Next Runs: 8

Issues
- No issues found.

Output
Schedule
Runs at 00:17, 06:17, 12:17, and 18:17 UTC on Monday through Friday.

Timezone
GitHub Actions evaluates scheduled workflows in UTC. Local times below use this browser's timezone.

Fields
- Minute: 17 minutes past the hour
- Hour: every 6 hours
- Day of month: any calendar day
- Month: every month
- Day of week: Monday through Friday

Next runs
1. Today at 12:17 PM UTC local (Mon, May 18, 12:17 PM UTC)
2. Today at 6:17 PM UTC local (Mon, May 18, 6:17 PM UTC)
3. Tomorrow at 12:17 AM UTC local (Tue, May 19, 12:17 AM UTC)
4. Tomorrow at 6:17 AM UTC local (Tue, May 19, 6:17 AM UTC)
5. Tomorrow at 12:17 PM UTC local (Tue, May 19, 12:17 PM UTC)
6. Tomorrow at 6:17 PM UTC local (Tue, May 19, 6:17 PM UTC)
7. Wed, May 20 at 12:17 AM UTC local (Wed, May 20, 12:17 AM UTC)
8. Wed, May 20 at 6:17 AM UTC local (Wed, May 20, 6:17 AM UTC)

What the GitHub Actions Cron Explainer Checks

  • Five-field cron syntax

    GitHub Actions uses minute, hour, day of month, month, and day of week fields.

  • Ranges, steps, lists, and wildcards

    Common cron patterns such as */6, 1-5, and comma-separated values are expanded for the preview.

  • UTC scheduling

    The explanation calls out UTC so local-time assumptions are visible before you commit a workflow.

  • Upcoming run preview

    The tool calculates the next scheduled matches instead of only translating the expression into words.

  • GitHub caveats

    Service delays and top-of-hour load caveats are presented as practical notes, not ignored.

GitHub Actions Cron Explainer Questions

  • Q: Does the GitHub Actions cron explainer upload my schedule? A: No. Inputs are processed in your browser, and pasted content is not sent to analytics or a server.
  • Q: What should I paste into the GitHub Actions cron explainer? A: Paste a five-field cron expression from an on.schedule workflow entry.
  • Q: What can I copy or download? A: You can copy the plain-English explanation and next-run preview.
  • Q: What does the GitHub Actions cron explainer not verify? A: It does not inspect your repository, workflow permissions, disabled schedules, or GitHub service load at runtime.

Related Tools

Updates

  • v1.0.0 New 2026-05-17: Initial cron parser, explanation, and next-run preview added.

Use GitHub Actions Cron Explainer with an LLM

Copy the prompt or pass the llms.txt contract link to your assistant.

Prompt
Use the CleanUtils GitHub Actions Cron Explainer tool for this request.
Tool contract: https://cleanutils.com/developer-tools/github-actions-cron-explainer/llms.txt

Read the llms.txt contract, ask me for any missing required input, then follow the contract exactly. If the contract includes JavaScript, run `runCleanUtilsTool(userInput)` in a sandboxed JavaScript runtime and return the result with any warnings or errors.