Current UTC Time — Free Live Clock

UTC (Coordinated Universal Time) is the primary time standard by which the world regulates clocks and time. It is maintained by atomic clocks and does not change with seasons or daylight saving time. All other time zones are defined as offsets from UTC.

Unix timestamps are formally defined as seconds since January 1, 1970 00:00:00 UTC — not GMT. In practice the two are numerically identical for any moment after 1972, because UTC is kept within 0.9 seconds of GMT via leap seconds. However, GMT is an astronomical standard while UTC is atomic. For timestamp purposes they are interchangeable, but the official Unix epoch definition references UTC.

No. UTC never observes daylight saving time. It remains constant throughout the year. This is one reason it is preferred in computing, logging, and international communications — there is no ambiguity caused by clock shifts.

Always store timestamps in UTC in databases. This avoids ambiguity from daylight saving time transitions and makes it trivial to convert to any local timezone when displaying data to users. Most database engines (PostgreSQL, MySQL, SQLite) support UTC natively.

There are 38 distinct UTC offsets in use worldwide, ranging from UTC-12:00 to UTC+14:00. Several regions use non-whole-hour offsets such as UTC+5:30 (India), UTC+5:45 (Nepal), UTC+9:30 (Australia/Darwin), and UTC+12:45 (Chatham Islands).

To convert UTC to local time, add your timezone offset to the UTC time. For example, if you are in UTC+5:30 and UTC is 12:00, your local time is 17:30. In JavaScript use new Date().toLocaleString() with a timeZone option, or Intl.DateTimeFormat with the desired timezone.

UTC is used in programming because it is a stable, unambiguous reference that is not affected by daylight saving time or political timezone changes. Storing and transmitting timestamps in UTC prevents bugs caused by timezone differences and makes sorting and comparison of timestamps straightforward.