Skip to content
SkedCast
Start free

Free tool

Daylight saving scheduled posts checker

This daylight saving scheduled posts checker: pick a time zone and see the next real daylight-saving transition, computed day-by-day from actual UTC offsets (not a hand-maintained date table), plus how a recurring local post time shifts in UTC across it — useful for anyone scheduling in UTC, coordinating across zones, or running a system whose dispatch queue stores times in UTC rather than local wall-clock time.

Check your daylight saving scheduled posts

Next transition: clocks fall back on Sunday, November 1, 2026

Local wall-clock times don’t change — the underlying UTC instant behind each recurring time shifts by an hour instead.

  • 09:00 local

    UTC instant shifts by +60 minutes across the transition — a UTC-based system dispatching at a fixed UTC time would fire at a different local hour before vs. after.

  • 17:00 local

    UTC instant shifts by +60 minutes across the transition — a UTC-based system dispatching at a fixed UTC time would fire at a different local hour before vs. after.

How to use the DST schedule checker

  1. Pick your scheduling time zone. Choose the zone your recurring posts are actually planned in.
  2. Enter your recurring local post times. Comma-separated 24-hour times, e.g. "09:00, 17:00".
  3. Read the next transition date. Computed by scanning real UTC offsets forward, so it stays correct even when a government changes its DST rules.
  4. Check each post time’s UTC shift. A 60-minute shift means a UTC-based system firing at a fixed UTC time will land on a different local hour before vs. after the transition.
  5. Adjust a UTC-based schedule if needed. If your scheduler stores times in UTC rather than local wall-clock time, this is the shift you’d need to account for around the transition date.

Worked examples

A 9am America/New_York post across the March 2026 transition

Clocks spring forward on March 8, 2026; a recurring 9am Eastern post’s underlying UTC instant shifts by 60 minutes earlier, even though the local wall-clock time stays 9am both before and after.

The same check for Asia/Tokyo

Japan does not observe daylight saving, so the checker reports no transition in the next year and every entered post time shows a 0-minute shift.

Daylight saving scheduled posts FAQ

How does this tool find the next DST transition?
It scans forward day by day, comparing each day’s real UTC offset (via Intl.DateTimeFormat) to the day before, and reports the first day the offset changes — a computed check, not a hand-maintained table of transition dates.
Does my local scheduled post time actually change?
No — the local wall-clock time you set stays the same. What shifts is the UTC instant behind it, which matters only if something (a UTC-based dispatch system, or an audience in another zone) cares about the underlying UTC time.
Why do some time zones show no transition?
Several zones in the list don’t observe daylight saving at all (e.g. Tokyo, Shanghai, Dubai) — the checker correctly reports no upcoming transition for those.
Can DST transition dates change from year to year?
Yes — and occasionally a government changes its DST rules entirely, which is exactly why this tool computes the date live rather than relying on a fixed table.
What direction does "spring forward" shift the schedule?
Clocks jump ahead one hour, so a post kept at the same local wall-clock time now fires earlier in UTC terms than it did the week before.
Does this tool store or send my post times anywhere?
No — every calculation happens in your browser using the same Intl.DateTimeFormat-backed logic as SkedCast’s own multi-time-zone planner; nothing is uploaded.

More on this topic

Ready to broadcast everywhere?

Sign up free — no credit card. You land on the Free plan, and you can start a one-time 7-day Studio trial from your workspace whenever you are ready. Connect your first accounts, import a batch, and watch one post fan out across every platform.

Start freeLog in to your console