Does it account for timezone and DST changes?
Yes. It is designed to help you preview timezone behavior and daylight saving time changes before a schedule goes live.
DevToolkit
Cron / Timezone / DST Preview
First-time friendly
Check how a cron expression maps to UTC and local time before using it in a scheduler.
What is Cron?
Cron is a scheduling format used to automate tasks.
Example
0 9 * * 1-5 = Every weekday at 09:00
Try a schedule
Start with an example
How to read the five fields
0
Minute
9
Hour
*
Day
*
Month
1-5
Weekday
A five-part cron expression is read from left to right: Minute Hour Day Month Weekday.
Unix cron is usually evaluated in the server's local timezone.
This preview evaluates the cron expression in the selected timezone.
This tool is provided for informational and preview purposes only. Always verify scheduler behavior in your production environment.
Preview
This means:
Every weekday at 09:00. The schedule is evaluated in UTC.
Human-readable detail
At 09:00, Monday through Friday
Schedule timezone
UTC
Local display: UTC
Fri, Jun 05, 2026, 09:00:00 UTC
UTC: Fri, Jun 05, 2026, 09:00:00 UTC
Offset: UTC+0
Mon, Jun 08, 2026, 09:00:00 UTC
UTC: Mon, Jun 08, 2026, 09:00:00 UTC
Offset: UTC+0
Tue, Jun 09, 2026, 09:00:00 UTC
UTC: Tue, Jun 09, 2026, 09:00:00 UTC
Offset: UTC+0
Wed, Jun 10, 2026, 09:00:00 UTC
UTC: Wed, Jun 10, 2026, 09:00:00 UTC
Offset: UTC+0
Thu, Jun 11, 2026, 09:00:00 UTC
UTC: Thu, Jun 11, 2026, 09:00:00 UTC
Offset: UTC+0
Fri, Jun 12, 2026, 09:00:00 UTC
UTC: Fri, Jun 12, 2026, 09:00:00 UTC
Offset: UTC+0
Mon, Jun 15, 2026, 09:00:00 UTC
UTC: Mon, Jun 15, 2026, 09:00:00 UTC
Offset: UTC+0
Tue, Jun 16, 2026, 09:00:00 UTC
UTC: Tue, Jun 16, 2026, 09:00:00 UTC
Offset: UTC+0
Wed, Jun 17, 2026, 09:00:00 UTC
UTC: Wed, Jun 17, 2026, 09:00:00 UTC
Offset: UTC+0
Thu, Jun 18, 2026, 09:00:00 UTC
UTC: Thu, Jun 18, 2026, 09:00:00 UTC
Offset: UTC+0
Deep dive
Useful when you want to sanity-check cron timing across UTC, local timezones, and DST boundaries before you ship a schedule.
Overview
It previews cron expressions locally in your browser and shows how the schedule behaves in UTC, local timezones, and common platform contexts such as GitHub Actions, Kubernetes CronJob, and Vercel Cron.
Input samples
Weekday morning job
Input: 0 9 * * 1-5 Timezone: America/New_York Output: Runs at 09:00 local time on weekdays, with the UTC time shifting when DST changes.
Every six hours
Input: 0 */6 * * * Timezone: UTC Output: Runs at 00:00, 06:00, 12:00, and 18:00 UTC every day.
Platform scheduling
Input: 15 2 * * * Platform: GitHub Actions / Kubernetes CronJob / Vercel Cron Output: Review the run time in the platform context before you rely on it in production.
When to use it
Navigation
Keep moving through the collection, workflow, and adjacent tools that usually belong with this page.
Related workflow
Continue with the tool chain that usually goes together here.
Check dates, schedules, and timezones
Preview cron schedules, inspect timestamps, and compare time values before a change reaches production.
Related tools
Open the closest adjacent tools without leaving the current context.
Answers
Does it account for timezone and DST changes?
Yes. It is designed to help you preview timezone behavior and daylight saving time changes before a schedule goes live.
Can I use it for GitHub Actions, Kubernetes CronJob, or Vercel Cron?
Yes. Those are common use cases for the tool, and the preview helps you compare how the same cron expression behaves in those environments.
Is this a full cron engine?
No. It is a browser-side preview tool for common cron patterns, so you should still confirm the final scheduler behavior in the platform you use.
Does it understand UTC and local timezones?
Yes. It is intended to make the UTC versus local-time difference obvious so you can catch off-by-one-hour mistakes early.
Disclaimer
This is a best-effort cron preview tool, not a complete scheduler emulator. Platform-specific rules, DST edge cases, and managed cron services can still differ, so always verify the final schedule in the system where it will run. All parsing and previewing happen locally in your browser and are not uploaded to a server.
Privacy
Previewing happens entirely in your browser. No backend request is made, no login is required, and DevToolkit does not store the cron content you paste here.