Timezone Guide

UTC stands for Coordinated Universal Time. It is the primary time standard by which the world regulates clocks and time. UTC does not observe daylight saving time—it runs at a constant rate regardless of season or location. When someone says a server or timestamp is in UTC, they mean the time has no local clock adjustment applied.

A UTC offset is the number of hours (and sometimes minutes) that a timezone differs from UTC. UTC+5:30 is India Standard Time: 5 hours and 30 minutes ahead of UTC. UTC−5 is Eastern Standard Time in North America: 5 hours behind UTC. Adding the offset to UTC gives the local clock reading.

Offsets can be fractional. Nepal Standard Time is UTC+5:45. India Standard Time is UTC+5:30. These half-hour and quarter-hour offsets were set historically to align local noon with solar noon.

UTC+0 and UTC are the same thing. GMT (Greenwich Mean Time) is also equivalent to UTC in most practical contexts, though they differ slightly in technical definition. For date calculations, treat UTC, GMT, and UTC+0 as interchangeable.

Daylight saving time (DST) is a seasonal practice of advancing clocks by one hour in spring and returning them in autumn. The goal is to shift an hour of daylight from early morning to evening. Not all countries observe DST—Japan, China, India, and most of Africa and Southeast Asia do not.

When DST starts in the US (second Sunday in March), clocks spring forward: 2:00 AM becomes 3:00 AM and that hour does not exist. Eastern Time shifts from UTC−5 (Eastern Standard Time, EST) to UTC−4 (Eastern Daylight Time, EDT). When DST ends (first Sunday in November), clocks fall back: 2:00 AM becomes 1:00 AM and that hour occurs twice.

The EU historically observed a similar DST rule (last Sunday in March and October). Some EU member states have proposed abolishing DST; the current legal status varies. Always confirm DST dates for the current year if precision matters.

When scheduling across timezones during DST transitions, anchor to UTC and convert to local time at display. A meeting at 15:00 UTC is unambiguous even if local clock rules change.

UTC offsets like UTC−5 describe the offset at a moment in time but do not encode DST rules. IANA timezone identifiers—sometimes called tz database or Olson names—encode both the offset and the full historical and future DST rule for a location. America/New_York, Europe/London, and Asia/Tokyo are IANA identifiers.

IANA identifiers are the standard in most programming languages, operating systems, and calendar applications. When you set a timezone in JavaScript with Intl.DateTimeFormat or in Python with the zoneinfo module, you use an IANA identifier.

The identifier format is Region/City where the city is the largest city in the timezone zone, not necessarily the user's city. Residents of Boston use America/New_York. Residents of Glasgow use Europe/London. The city is a proxy for the rule set, not a geographic requirement.

Abbreviations like EST, PST, and IST are ambiguous—IST is India Standard Time, Irish Standard Time, and Israel Standard Time. Prefer IANA identifiers or explicit UTC offsets when precision matters.

The Timezone Converter on DateToolsHQ accepts a date and time in one timezone and outputs the equivalent time in one or more target timezones. Enter the source date, time, and timezone; the tool applies the correct UTC offset including DST for that date.

Manual conversion: convert the source time to UTC first by subtracting its offset, then add the destination offset. Los Angeles at 2:00 PM PDT (UTC−7) converts to UTC as 21:00 UTC, which is 17:00 EDT (UTC−4) in New York on the same day.

Date changes at timezone boundaries are the most common source of confusion. A meeting at 11:00 PM UTC is the next calendar day in UTC+3. When the local date matters—not just the clock time—confirm the date for each participant's timezone.

Unix timestamps sidestep timezone conversion entirely by representing an instant in UTC. If your system stores timestamps, convert to each local timezone at display time rather than storing local times in the database.

Storing local time without a timezone label: a datetime column with value 2026-06-15 14:00:00 and no timezone stored cannot be interpreted unambiguously after the fact. Always store UTC or include the offset.

Assuming all countries observe DST in the same direction and on the same dates: Australia's DST runs the opposite calendar months from North America and Europe. Countries near the equator often do not observe DST at all.

Using abbreviations in scheduling: EST means UTC−5 in North America but could be confused with Australian Eastern Standard Time (UTC+10). Write the IANA identifier or UTC offset instead.

Ignoring DST transitions when scheduling recurring events: a meeting at 9:00 AM Eastern every Monday shifts by one UTC hour when DST starts or ends. Systems that store the event as 14:00 UTC (9:00 EST) will display it as 10:00 EDT after the spring transition unless DST is accounted for.

The Days Until Calculator counts calendar days to any future date—or how many days ago a past date was—with an optional include-today setting for planning.

Countdown To Date adds an optional UTC time, event name, and hour/minute updates when you need more detail than calendar days alone.

Seasonal pages target the next occurrence automatically: Valentine's Day (February 14), Mother's Day (second Sunday in May), Independence Day (July 4), Halloween (October 31), Thanksgiving (fourth Thursday in November), Black Friday (the following Friday), Cyber Monday (the Monday after Thanksgiving), Easter Sunday (Gregorian), Christmas (December 25), and New Year's Day (January 1).

For a live second-by-second display with hours and minutes, use the Countdown Timer when the target includes a specific time of day in UTC.