London's time zone situation is simpler than most people think, but the details trip up a lot of developers and schedulers.
London sits in the United Kingdom and uses two time standards throughout the year. For most of the winter, it's on GMT, which is UTC+0. From late March to late October, it switches to BST, which is UTC+1. The switch happens at 1:00 AM GMT on the last Sunday of March, moving clocks forward by one hour. In autumn, the clocks go back at 1:00 AM BST on the last Sunday of October, returning to GMT. The EU angle here is worth clarifying because people get confused by it. The European Union has no single mandated time zone for its member states. Individual countries choose their own offset from UTC. The UK left the EU in January 2020, but even before that, the EU never forced the UK to change its time zone rules. The EU did have a directive about summer time transitions that member states had to follow, and the UK implemented that through its own legislation. There was talk in 2018 about the EU proposing to abolish seasonal clock changes across member states, but that proposal never actually went through. So the EU decision you're probably thinking of didn't change anything for London. In practice, this means London follows the British Summer Time scheme, which aligns closely with the EU's summer time directive anyway. The real issue isn't political decisions, it's the mechanical fact that the clock changes happen on different dates in different places, and that causes problems when you're scheduling cross-border operations.
I spent months dealing with a production bug where our payment processing system would occasionally double-charge or miss a scheduled batch job during the spring and autumn transitions. The root cause was that the server was running in UTC and the application code was doing arithmetic on local time values without converting them properly. On the day clocks spring forward, there's a missing hour. On the day clocks fall back, there's a repeated hour. Our cron jobs were stored as local time strings in the database, so during the fall-back transition, the same job would execute twice because 2:30 AM BST happened once at UTC 1:30 PM and again at UTC 1:30 PM the next hour. The workaround was straightforward but required changes in three places. First, we moved all scheduling to UTC internally. Second, we used the Olson timezone database version with the correct transition rules rather than hardcoding offsets. Third, we added a validation layer that flagged any timestamps falling in the ambiguous hour during fall-back and defaulted them to the later occurrence. This cut our transition-day incident rate from about four per year to zero over the next two years. One thing beginners consistently get wrong is assuming that GMT and UTC are interchangeable in every context. They're practically the same for everyday purposes, but GMT is a time zone name while UTC is the time standard. The distinction matters when you're working with systems that need to report their time source, like financial trading platforms or scientific instruments. For scheduling meetings, ordering coffee, or building a web app, you can treat them as identical. For regulatory compliance work involving European financial markets, the difference shows up in audit logs and you'll wish you hadn't glossed over it.
Another counter-intuitive point is that the UK does not stay on GMT year-round like countries at similar latitudes sometimes do. Iceland is at roughly the same latitude and stays on UTC+0 all year. Portugal also stays on UTC+0. The UK chose to observe DST, and that choice has been consistent since World War Two, with a brief experiment in permanent BST during 1968 to 1971 that was abandoned because of low public support. The current system has been in place since 1996, harmonized with the EU directive at that point. If you need to convert London time to other zones, the most reliable approach is to use the IANA timezone identifier Europe/London in whatever library you're working with. Avoid using fixed offset strings like "GMT+0" or "BST+1" because they don't capture the transition dates and your code will break when the clock changes. Python's datetime module with zoneinfo, JavaScript's Intl.DateTimeFormat, and Java's java.time library all handle Europe/London correctly if you point them at the right identifier. The main limitation of this system is that the twice-yearly transitions are unavoidable and will keep causing issues for anyone who ignores them. Even with proper IANA timezone support, edge cases exist around legacy systems, hardcoded schedules, and databases that store timestamps without timezone awareness. Some organizations simply don't migrate their legacy code fast enough, and those systems will continue to produce errors on transition days. If you're maintaining an older application, the practical recommendation is to audit every place where local time strings are parsed or displayed, test the deployment against both transition dates, and maintain a runbook that documents what to expect.
Get the Full Details
For most people just trying to figure out what time it is in London, the answer is straightforward: London is on GMT now and will stay on GMT until the last Sunday in March, when it moves to BST. It will remain on BST until the last Sunday in October, then return to GMT. The EU isn't going to change this, and the UK has no plans to either. If you're building software around it, invest the time to do it correctly from the start.
