Current time, time-zone comparisons, and practical planning tools.
How daylight saving time changes local clocks and why some regions avoid it entirely.
Answer first
DST is a local time-policy choice. A region shifts its displayed civil time, usually by one hour, to change how daylight aligns with working and evening hours.
It does not change UTC itself. It changes how a city or zone lines up against UTC and against other locations throughout the year.
Changes UTC itself
No
Changes local offset from UTC
Yes
Common shift amount
1 hour
Global adoption
Mixed and inconsistent
Teams assume a time difference is stable, then a spring or autumn clock change breaks recurring meetings, cron jobs, and support handoff expectations.
The pain gets worse when two regions change on different dates or when one region changes and another does not.
Anchor planning in UTC, then convert to local time at the last step. For recurring operations, document whether a task is fixed to UTC or fixed to a local civil clock.
No. UTC stays fixed. Only local civil zones move relative to it.
Because some regions apply DST and others do not, or they apply it on different start and end dates.