---
title: "GMT vs UTC: what's the difference?"
url: https://meet.barq.dev/glossary/gmt-vs-utc
updated: 2026-11-17
author: "Hammad Ali"
---

# GMT vs UTC: what's the difference?

> **Short answer:** GMT means Greenwich Mean Time; UTC means Coordinated Universal Time. For ordinary appointment conversion, both indicate zero offset, so 10:00 GMT and 10:00 UTC give the same clock reading. The scheduling trap is using GMT to mean London time all year: London's July clock is one hour ahead of UTC.


## What does GMT vs UTC change in a meeting message?

For a dated appointment explicitly written at zero offset, choosing the label GMT or UTC doesn't introduce a one-hour conversion difference. The error appears when the writer intends a location's seasonal local time but labels it as a fixed zero-offset instruction.


Make the intention explicit. "15 July 2026 at 14:00 London time" and "15 July 2026 at 14:00 UTC" identify different instants under London's rules for that date.


| Instruction on 15 July 2026 | London clock | UTC clock |
| --- | --- | --- |
| 14:00 London time | 14:00 | 13:00 |
| 14:00 UTC | 15:00 | 14:00 |
| 14:00 at GMT's zero offset | 15:00 | 14:00 |

Method: computed with Luxon using Europe/London and a fixed zero offset. [IANA's zone database](https://www.iana.org/time-zones) and [release notes](https://data.iana.org/time-zones/tzdb/NEWS) describe local-clock rules and updates, as of 17 November 2026.


## Is London always on GMT?

No. The dated Europe/London examples use UTC+00:00 in January and UTC+01:00 in July, so "London time" can't be replaced by GMT across the whole year. Keep the named location when the intention is to follow its clock.


Compare two dates. At 14:00 on 15 January 2026, London matches 14:00 UTC; at 14:00 on 15 July, London matches 13:00 UTC.


Those results use the same local hour. The date changes the applicable offset, which is why copying a winter conversion into a summer invitation gives the wrong appointment. Check [CET versus CEST](https://meet.barq.dev/glossary/cet-vs-cest) before using a winter offset for an appointment that follows Berlin's summer working day.


The [UTC explanation](https://meet.barq.dev/glossary/utc) covers the shared reference itself, while our [time zone abbreviation reference](https://meet.barq.dev/glossary/time-zone-abbreviations) explains why short labels can conceal the place you intended.


## How should you write an invitation instead of "2pm GMT"?

Write a complete date and say whether the commitment follows a location or a fixed reference. For a London-local appointment, use "15 July 2026, 14:00 London time"; for an appointment deliberately fixed to UTC, say "15 July 2026, 14:00 UTC".


Don't leave readers guessing. Include an end time or duration too, so a correct conversion doesn't leave one person expecting 30 minutes while the other reserves an hour.


Our [scheduling glossary of related terms](https://meet.barq.dev/glossary/scheduling-glossary) defines the named-zone and offset concepts behind those instructions. You can use precise meeting wording without getting into scientific timekeeping distinctions that don't change the booking decision.


## How does Barq Meet avoid a year-round GMT assumption?

Barq Meet uses the availability schedule's named zone for working hours and lets guests read available appointments in another zone. We apply the schedule's local-time rules to the chosen date, so a London schedule isn't reduced to a permanent zero offset.


We show guests their selected display zone. We include calendar invitations in booking confirmations, giving people an appointment record to check instead of relying only on a manually typed GMT suffix.


Check before making changes. If the appointment is wrong, reschedule it through the booking process; changing a phrase in a reminder doesn't itself move the reserved time.


The host's calendar connection must be Google. Choosing UTC or GMT in your wording doesn't add an Outlook or iCloud connection for conflict checking.


Review [the available calendar features](https://meet.barq.dev/pricing), then [offer a dated appointment through a booking page](https://meet.barq.dev/app/sign-in) when you want the guest to choose using their own local clock.

## Frequently asked questions

### Will changing GMT to UTC fix a one-hour London error?

Not by itself. If the intended meeting follows London's summer clock, both zero-offset labels still describe the wrong local hour. Check the appointment's date and intended location, then correct the reserved instant if needed. Check whether the date falls in British Summer Time before changing labels, because both UTC and GMT describe zero-offset time in this comparison.

### Is GMT+1 a year-round name for London?

No. A plus-one offset describes a difference from zero, while London has date-dependent rules. Use Europe/London for a schedule intended to follow the city, and check the offset on the particular appointment date. Use Europe/London for a meeting that follows London's local workday, with the actual offset checked for the specific appointment date.

### Should I explain atomic timekeeping to a guest?

Usually the guest needs a complete appointment instruction: date, time and intended zone. Keep the message focused on those inputs and the joining instructions; deeper timekeeping history doesn't resolve an omitted date or an incorrectly labeled local hour. Give the guest a dated local start and a clear zone; the history of time standards rarely helps them join the right conversation.

## Related pages

- [What is UTC (Coordinated Universal Time)?](https://meet.barq.dev/glossary/utc)
- [Time zone abbreviations list for scheduling](https://meet.barq.dev/glossary/time-zone-abbreviations)
- [Scheduling glossary: booking and calendar terms explained](https://meet.barq.dev/glossary/scheduling-glossary)
- [CET vs CEST: what's the difference?](https://meet.barq.dev/glossary/cet-vs-cest)

[Create your free booking link](https://meet.barq.dev/app/sign-in)
