UTC and local time: a practical explanation
Learn what an offset tells you, what it leaves out and how to write an unambiguous time.
One instant, several clock readings
UTC is the common reference used to express an instant independently of a person’s local clock. A UTC offset tells you how far a particular local reading is ahead of or behind that reference. At UTC+02:00, local time is two hours ahead of UTC; 12:00 UTC is therefore 14:00 locally. The offset is not a measure of distance, travel time or working-hour overlap. It is the arithmetic relationship between two clock readings at that instant.
An offset is not a complete time zone
A geographic time zone, such as Europe/Paris, contains rules that can vary with the date. Paris does not have the same offset throughout every year. Writing UTC+01:00 identifies an offset, but does not identify all the places or historical rules that might use it. For a future local appointment, keep the date and named location together. Our time-zone data guide explains where those changing rules come from.
Read a timestamp from left to right
In the common Internet format described by RFC 3339, 2026-10-11T15:00:00+02:00 means October 11, 2026 at 15:00 with an offset two hours ahead of UTC. The same instant is 2026-10-11T13:00:00Z; Z marks UTC. When converting, subtract a positive offset or add the magnitude of a negative one. Crossing midnight can change the date, so do not discard the date while checking the arithmetic.
Choose the right form for the task
For a single global deadline, provide an explicit instant and let readers convert it with the time converter. For a weekly local appointment, preserve the city’s time zone so seasonal rules can be applied. For logs, retain a precise timestamp and offset. Avoid guessing from abbreviations or a screenshot of a clock. The event-time guide shows how to combine a readable announcement with enough information for a reliable conversion.