Daylight Saving Transition Explorer

Inspect yearly clock-offset changes for a named zone, including skipped and repeated local ranges.

Inputs stay on your device No sign-up Free to use
How this works

The tool runs in this browser. Your file or text is not uploaded to UseFreeTools. Check this tool's limits for anything it may save on your device.

Privacy details

Inspect input controls

Showing an example. Edit to see your own.

Use a zone supported by your browser, such as Europe/London or Australia/Lord_Howe.

Find offset changes whose UTC instants fall in this year.

Processed in your browser. Your inputs stay on this device.

How to use Daylight Saving Transition Explorer

  1. Enter a named time zone and supported year.
  2. Choose the UTC calendar year to scan.
  3. Compare before/after offsets and the skipped or repeated local range.

Example: Daylight Saving Transition Explorer

A local worked example using the inputs and settings below for daylight saving transition explorer.

You add
IANA time zone: "UTC" UTC calendar year: "2026"
You get
0 offset changes for UTC in UTC year 2026. time-zone-transitions.csv

Options

IANA zone
Use a named zone supported by the browser. UTC has no seasonal clock changes; a region’s current civil rules come from the browser runtime.
Year
Select the bounded year to scan. The result describes runtime timezone data rather than a prediction that future law will stay unchanged.

Supported inputs and limits

One named zone and UTC calendar year from 1970 through 2100. The scan samples offsets every 15 minutes and refines detected changes to seconds; changes at the start of the UTC year are included. It uses installed browser timezone data, whose rules and version can differ. Offset changes may be political, seasonal, fractional-hour or date-line changes. This page does not update timezone rules.

Where your input is processed

This tool processes your input in this browser. Your text and files are not uploaded to UseFreeTools. Check this tool's limits for anything it may save on your device.

Check future civil times again nearer the date

A transition can create repeated or nonexistent local times. The reported offsets help identify those cases, but the browser’s data can differ from another system’s version. Recheck important future plans when authorities or timezone data change.

Questions about Daylight Saving Transition Explorer

Does every offset change mean daylight saving?

No. A government can change the base offset or its calendar policy for other reasons.

Can a transition be thirty minutes long?

Yes. The page shows the observed offset difference instead of assuming a one-hour change.

Why can another browser disagree?

Browsers can contain different timezone data versions, especially for changed or future rules.

Project manager: Tony Hines · Content updated 4 October 2026 · Report a problem