UTC vs GMT — what's the difference?
If you've ever stared at a calendar invite that says "GMT+0" and wondered if it's the same as "UTC," yes — almost. Both refer to a time that's neither east nor west of any time zone, both are used as references for everywhere else, and for any practical purpose you'll encounter, they're interchangeable.
Quick check: today's exact UTC time is on the UTC converter — pick any local zone and you'll see the offset.
The short answer
UTC = Coordinated Universal Time. The official global reference clock since 1972, defined by atomic clocks.
GMT = Greenwich Mean Time. A time-zone (technically a "civil" time) at the Royal Observatory in Greenwich, London. It was the world's reference clock from 1884 to 1972.
For day-to-day purposes, UTC and GMT show the same time. Down to the second. The differences are technical and historical.
What changed in 1972
Until 1972, GMT was the world's reference standard. It was based on the average position of the sun above the meridian at Greenwich. This worked fine until atomic clocks got accurate enough to expose a problem: Earth's rotation isn't perfectly steady. It speeds up and slows down by tiny amounts, so a "mean solar day" varies by milliseconds.
Atomic time doesn't have that problem. So in 1972, the international community switched the reference from solar time (GMT) to atomic time (Coordinated Universal Time, UTC), with leap seconds added occasionally to keep UTC within 0.9 seconds of GMT-style solar time.
After 1972, GMT was demoted from "global reference" to "the time zone of the United Kingdom in winter." The UK still uses GMT as the legal name for its winter time, switching to BST (British Summer Time, UTC+1) for daylight saving.
When the difference matters
For 99% of uses, it doesn't. UTC and GMT show the same wall-clock time within milliseconds. If you see "GMT" in a software setting, a calendar invite, a news report, or an aviation timestamp, it's safe to treat it as UTC.
The differences matter in three specific cases:
1. Astronomy and navigation. GMT (or its modern equivalent UT1) is tied to Earth's rotation. UTC is tied to atomic clocks. The two diverge by up to 0.9 seconds. Telescopes and GPS need to know which they're using. Most other software doesn't.
2. Leap seconds. Strict POSIX/Unix time and most computer systems don't include leap seconds — they pretend leap seconds never happened. UTC officially does include them. So a "Unix timestamp" in 2026 differs from "UTC seconds since 1970" by 27 seconds (the cumulative leap seconds added since 1972). Most software ignores this. The systems that care: GPS, scientific instruments, financial trading platforms.
3. The UK in summer. When the UK observes British Summer Time (BST), it's at UTC+1, not UTC+0. So in summer, "GMT" no longer matches "UK current time." The UK media often still says "GMT" colloquially even when it means BST — be careful with British TV listings in summer.
Why people still say GMT
Three reasons GMT persists in everyday language:
1. Historical inertia. GMT was the standard for nearly a century. It's deeply embedded in older infrastructure: timestamp strings in old log formats, time zone names in legacy software, the legal name of UK winter time.
2. The Greenwich brand. "Greenwich Mean Time" is a recognizable phrase. It evokes the meridian, the prime line dividing east and west, the historical center of global timekeeping. "Coordinated Universal Time" is bureaucratically precise but emotionally flat.
3. Linguistic convenience. "GMT+5" is shorter and easier to say than "UTC+05:00." Many old systems and many casual users still use the GMT prefix. Functionally, "GMT+5" and "UTC+05:00" mean the same thing.
You'll see both in modern usage:
- Tech / official: UTC. ISO 8601 format uses Z (which means UTC). Wikipedia uses UTC. GitHub timestamps are UTC.
- Aviation: Z (Zulu time = UTC).
- Casual / British media: GMT.
- Calendar invites: usually labeled with the offset only ("(GMT+5:30) Mumbai") — sometimes with GMT, sometimes with UTC, both common.
A common confusion: "GMT 0" in different software
Some calendar software and timezone pickers list "GMT" as a literal time zone choice. This sometimes means "UTC" (the global reference) and sometimes means "Europe/London time" (which is UTC+0 only in winter). Quick test: if your calendar says "GMT" and a meeting in summer shows the same hour as Paris, it's actually Europe/London, not UTC.
The IANA time zone database has both as separate entries:
- `Etc/UTC` — true UTC, never observes DST
- `Europe/London` — UK time, UTC+0 in winter and UTC+1 in summer
For a meeting that should always be at the same UTC hour year-round, pick `UTC` or `Etc/UTC`. For "London local time," pick `Europe/London`.
Quick reference table
| Property | UTC | GMT |
|----------|-----|-----|
| Official name | Coordinated Universal Time | Greenwich Mean Time |
| Defined by | Atomic clocks (BIPM) | Solar observation at Greenwich |
| Status | Current global reference (since 1972) | Historical reference; UK winter time |
| Includes leap seconds? | Yes (officially) | No (in original definition) |
| Observes DST? | No | UK switches to BST in summer |
| ISO 8601 suffix | "Z" or "+00:00" | "GMT" (informal) |
| Used by | International standards, software | UK media, aviation legacy, casual usage |
When to use UTC over GMT
Always, in code or technical writing. UTC is the modern standard. GMT is a historical name that's still used colloquially but not in formal specifications. Every modern programming language, database, and API uses UTC under the hood.
When to use GMT: when you're writing for a UK audience, when quoting British sources, when working with aviation legacy systems that explicitly call it GMT, or when the exact phrase "Greenwich Mean Time" is more recognizable than "UTC" for your readers.
For all practical purposes, the UTC converter treats UTC and GMT as identical — which is correct for almost any use case.
FAQ
Are UTC and GMT the same time right now?
To the second, yes — for any real-world purpose. They differ by less than 0.9 seconds technically (and usually by milliseconds). If you're scheduling a meeting, planning a flight, or coordinating with someone abroad, treat them as identical.
Why does my computer say "GMT" but my phone says "UTC"?
Different software conventions. Older operating systems (pre-2000) often labeled UTC as GMT for backward compatibility. Modern systems use UTC. Both are showing you the same time.
Is the UK on GMT or UTC?
In winter, both — the UK's official time is GMT, which equals UTC. In summer, the UK is on BST (British Summer Time), which is UTC+1, one hour ahead of UTC. The legal name "GMT" applies to UK winter time only.
What's UT1?
A more precise version of GMT — Universal Time 1. It's the modern astronomical equivalent of GMT, defined by Earth's rotation. UTC and UT1 are kept within 0.9 seconds of each other by adding leap seconds when needed.
Does GMT have daylight saving time?
GMT itself doesn't — it's a fixed reference. But the UK's "GMT" effectively shifts to BST (UTC+1) in summer because the UK observes daylight saving. So if someone in the UK says "GMT" in July, they likely mean BST. Be careful with British timestamps in summer.
Is "Zulu time" the same as UTC or GMT?
Zulu time = UTC, in aviation and military notation. The "Z" comes from the NATO phonetic alphabet's "Zulu" representing the letter Z, which is also the suffix used in ISO 8601 to indicate UTC (e.g., `2026-05-10T14:30:00Z`). Treat Z, Zulu, and UTC as identical.
Bottom line
UTC and GMT are the same time in everyday use. The technical differences (atomic vs solar, leap seconds, UK summer time) matter only in specific contexts: astronomy, GPS, scientific timekeeping, or anywhere you're handling pre-1972 timestamps.
For modern conversions, the UTC converter and world clock treat them interchangeably — which is right for nearly every situation you'll encounter.