UTC is the time standard that keeps the world synchronized. When a developer in Bangalore deploys code at 14:00 UTC, a teammate in San Francisco knows exactly when that happened without doing timezone math. The UTC clock on this page updates every second so you always have a reference point.
Server logs almost always use UTC. If you are debugging a production incident that occurred at 02:30 UTC, you need to know what that means in your local time to coordinate with your team. This page shows your local offset alongside UTC so you can convert at a glance.
Flight schedules, financial market open and close times, and international event broadcasts all use UTC as their reference. A trader in Johannesburg watching the New York Stock Exchange open at 14:30 UTC can check this page to confirm the current UTC time before placing orders.
API documentation frequently references UTC. A webhook that fires at 00:00 UTC daily, or a rate limit that resets at the top of the UTC hour, requires you to know the current UTC time to plan your requests.
UTC (Coordinated Universal Time) is based on International Atomic Time, which is measured by a network of atomic clocks around the world. Unlike GMT, which is based on Earth's rotation, UTC is maintained by the Bureau International des Poids et Mesures (BIPM) and is the basis for civil time worldwide.
Every timezone is defined as an offset from UTC. New York during standard time is UTC-5, during daylight saving time it is UTC-4. Tokyo is always UTC+9 because Japan does not observe daylight saving. This page uses the IANA timezone database to calculate offsets and display times accurately.
The live clock uses your device's system time, which is synchronized with internet time servers. The ISO 8601 format shown on this page (for example, 2026-07-28T15:30:00.000Z) is the standard format used in APIs, databases, and configuration files.
Input
UTC time is 15:30:00
Output
New York (UTC-4): 11:30:00, London (UTC+1): 16:30:00, Tokyo (UTC+9): 00:30:00 (next day)
During July with daylight saving time active in New York and London
Input
UTC time is 09:00:00
Output
Mumbai (UTC+5:30): 14:30:00, Sydney (UTC+10): 19:00:00, Los Angeles (UTC-7): 02:00:00
During July with daylight saving time active in Los Angeles
Input
UTC time is 00:00:00 (midnight)
Output
ISO 8601: 2026-07-28T00:00:00.000Z, Unix timestamp: 1753977600
Start of a new UTC day
Input
Local time in Johannesburg (UTC+2)
Output
If UTC is 15:30, Johannesburg is 17:30. Offset is UTC+2 year-round (no DST).
South Africa does not observe daylight saving time
Pitfalls to avoid
What is UTC?
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 and has no timezone offset. It is equivalent to GMT for most practical purposes.
How is UTC different from GMT?
GMT is a timezone based on the Earth's rotation, while UTC is a time standard based on atomic clocks. For everyday use, they are the same. UTC is the technical standard used in computing, aviation, and scientific contexts.
Why do developers use UTC?
UTC is timezone-independent, which makes it ideal for storing timestamps in databases, logging events, and exchanging data between systems in different timezones. When you store a timestamp in UTC, it represents the same moment regardless of where the server or user is located.
Does UTC change with daylight saving time?
No. UTC never changes. It remains constant year-round. Timezones like British Summer Time (BST, UTC+1) or Pacific Daylight Time (PDT, UTC-7) shift relative to UTC, but UTC itself stays at +00:00 always.
How do I convert UTC to my local time?
Find your UTC offset and add or subtract it from the UTC time. For example, if you are in New York during daylight saving time, your offset is UTC-4. If the UTC time is 14:00, your local time is 10:00 (14 minus 4).
What is ISO 8601 format?
ISO 8601 is an international standard for representing dates and times. The format is YYYY-MM-DDTHH:MM:SS.sssZ, where T separates the date and time, and Z indicates UTC. For example, 2026-07-28T15:30:00.000Z.
Why does the date differ across timezones at the same UTC moment?
Because timezones are offset from UTC, the local date can differ. When it is 23:00 UTC on July 28, it is already July 29 in Tokyo (UTC+9) but still July 28 in Los Angeles (UTC-7). The UTC date only changes at 00:00 UTC.
Is the UTC clock on this page accurate?
The clock uses your device's system time, which is typically synchronized with internet time servers (NTP). For most purposes, it is accurate to within a few hundred milliseconds. For applications requiring sub-second precision, use a dedicated NTP client.
The UTC clock on this page uses your device's system clock, which is typically synchronized with NTP servers. Timezone offsets are calculated using the IANA Time Zone Database. For applications requiring leap second accuracy or sub-millisecond precision, consult a dedicated time service.