UTC, or Coordinated Universal Time, is the main time standard used to coordinate clocks around the world. It does not belong to a particular country or time zone. Instead, it acts as a shared reference from which local times are calculated.
If a city is described as UTC+2, its standard local time is two hours ahead of UTC. A location at UTC−5 is five hours behind. This simple relationship allows people, computers, airlines, financial markets, and scientific institutions to describe the same moment without relying on local clock settings.
UTC is closely related to Greenwich Mean Time, commonly known as GMT. Both are centered on the time at the prime meridian, which runs through Greenwich in London. GMT began as an astronomical time standard, while UTC is the modern international standard used for precise timekeeping. In everyday conversation, the two are often treated as equivalent, but UTC is the more accurate and technically appropriate term.
The system combines two ideas. Atomic clocks provide an extremely stable measurement of time, while observations of Earth’s rotation help keep civil time connected to the natural day. Earth does not rotate at a perfectly constant speed, so these two measurements do not always remain aligned. To manage the difference, leap seconds have historically been added to UTC occasionally. A leap second may make a minute last 61 seconds instead of the usual 60.
Leap seconds can be useful for keeping UTC close to astronomical time, but they also create difficulties for computer systems. Software often assumes that time moves in a regular sequence, and an extra second can cause errors in databases, networks, or automated processes. For this reason, international timekeeping authorities have decided to work toward ending the use of leap seconds by or before 2035. UTC will remain the global reference, but its relationship with Earth’s rotation may gradually become less exact.
For ordinary users, UTC appears most often in travel schedules, online services, weather reports, satellite systems, and software settings. A meeting scheduled for 15:00 UTC happens at different local clock times depending on the season and location. Someone in London may see it as 3 p.m. during part of the year, while someone in New York may see it as 10 a.m. The local time can change when daylight saving time begins or ends, but the UTC moment remains fixed.
This is why international teams often record events in UTC. A server log showing 08:42 UTC gives engineers around the world a single point of reference. Without UTC, comparing records from different countries could involve several layers of conversion, including time zones, daylight saving rules, and regional changes to official clocks.
UTC is also important when using timestamps. Formats such as 2025-03-08T14:30:00Z indicate a time expressed in UTC, with the letter Z meaning “Zulu,” a term commonly used in aviation and military communications. A timestamp with an offset, such as 2025-03-08T09:30:00−05:00, identifies the same kind of moment by stating the local difference from UTC.
Understanding UTC does not require memorizing every time zone. The practical habit is to check whether a displayed time is local, UTC, or accompanied by an offset. That small detail can prevent missed meetings, incorrect data analysis, and confusion when people work across borders.