UTC vs GMT vs BST: Why London Time Changes in Summer

Quick summary: UTC and GMT are both fixed at UTC+0 and never change for daylight saving — they're aligned all year. What actually changes is the UK's local civil time: in winter, the UK runs on GMT (UTC+0); in summer, it switches to British Summer Time (BST, UTC+1). The common mistake is using "GMT" as a stand-in for "UK time" year-round, which is only accurate for half the year. Use the Time Zone Converter to see the real offset for any date.

Why the Confusion Happens

"GMT" started out as a place-based standard — Greenwich Mean Time, the local solar time at the Royal Observatory in Greenwich, London. For a long time, "GMT" and "the reference point everyone else measures against" were the same thing, and people got used to treating them as synonyms.

UTC (Coordinated Universal Time) came later, as a more precise, timezone-neutral standard that doesn't belong to any single country or shift with any country's clock-change laws. UTC and GMT are actually aligned at UTC+0 all year — neither one moves. What creates the confusion is that people also use "GMT" casually to mean "whatever time zone the UK is currently on," and that part does change twice a year.

What Actually Changes

The UK observes daylight saving time, just like much of the US, Canada, and Europe. For roughly half the year (spring through fall), the UK's local clocks run on British Summer Time (BST), which is UTC+1 — one hour ahead of GMT and UTC. For the other half of the year, the UK's local clocks run on GMT, which does equal UTC+0.

So the accurate way to think about it: UTC and GMT both stay fixed at UTC+0, always. What moves is the UK's local civil time, which switches between the GMT designation in winter and the BST designation in summer — the same kind of seasonal switch you'd see with EST/EDT in the US, just under different names.

A Worked Example: The Same Conversion, Two Different Offsets

Here's a clean way to see it. Converting the same time of day, from the same origin zone, to London, on two dates six months apart:

• January 15, 2026, 12:00 PM Eastern Time → 5:00 PM in London. The offset used: EST (UTC−5) → GMT (UTC+0). This is winter, so London is genuinely on GMT, and GMT does equal UTC here.
• July 15, 2026, 12:00 PM Eastern Time → 5:00 PM in London. The offset used: EDT (UTC−4) → BST (UTC+1). The calculator itself labels this offset "GMT+1" — that's the same hour commonly known as British Summer Time (BST); London is no longer on GMT itself by this date. Same clock result as the January example — but only because Eastern Time also shifted forward for its own daylight saving at the same time. London's local civil time moved from GMT to BST between these two dates, a full hour ahead of UTC.

If you assumed London was always on GMT (UTC+0) and used that assumption for the July conversion, you'd be off by a full hour — not because GMT itself changed, but because London wasn't actually on GMT in July.

Why This Matters for Scheduling and Software

If you're scheduling an international meeting, setting a server timestamp, or writing code that stores times, saying "GMT" when you actually mean "UK local time" is genuinely risky for anything happening between spring and fall — the person or system on the other end might take "GMT" literally as UTC+0, when the UK is actually running an hour ahead on BST. UTC has no such ambiguity: it's the same offset every single day of the year, which is exactly why programmers, pilots, and international schedulers default to UTC for anything that needs to be unambiguous.

GMT itself isn't wrong or inconsistent — it's a fixed standard, same as UTC. The risk is entirely in using "GMT" as loose shorthand for "UK time," when UK time only matches GMT for half the year.

Related Calculators

• Time Zone Converter — compare local times and UTC offsets for any date
• Unix Timestamp Converter — Unix timestamps are always based on UTC, making this a natural companion to time zone conversion
• Days Between Dates — useful when coordinating events or deadlines across time zones
• Date Add/Subtract Calculator — add or subtract time from a date before converting it to another zone

Frequently Asked Questions

What's the actual difference between UTC and GMT? UTC is the modern, precise global time standard. GMT corresponds to UTC+0 for everyday civil-time use, and the two stay aligned all year. The confusion comes from people using "GMT" as shorthand for UK local time — but the UK only runs on GMT in winter, switching to British Summer Time (UTC+1) in summer.

Does GMT change with Daylight Saving Time? No — GMT stays fixed at UTC+0 all year, the same as UTC. What changes is the UK's local civil time, which switches from GMT (winter) to British Summer Time, UTC+1 (summer).

Is UTC the same all year round? Yes. UTC never shifts for daylight saving anywhere, for any country. That's exactly why it's used as the neutral reference point that all named time zones are defined relative to.

Why do some time zones show two offsets, like UTC+0/+1? Many time zones — including London's — shift by one hour for daylight saving. Showing both offsets (standard time first, then daylight time) reflects that the zone's actual UTC offset depends on the date, not just the location.

Should I use UTC or GMT when scheduling something international? UTC, whenever precision matters. GMT itself is reliable, but "GMT" is frequently misused as loose shorthand for UK local time — and using it that way for a date that falls in the UK's daylight saving period can introduce a one-hour error that UTC avoids entirely.