---
title: "CET vs CEST: what's the difference?"
url: https://meet.barq.dev/glossary/cet-vs-cest
updated: 2026-11-17
author: "Hammad Ali"
---

# CET vs CEST: what's the difference?

> **Short answer:** CET, Central European Time, is UTC+01:00; CEST, Central European Summer Time, is UTC+02:00. The labels differ by one hour. In Berlin, 14:00 on 15 January 2026 is 13:00 UTC, while 14:00 on 15 July is 12:00 UTC. A dated location is clearer than using CET throughout the year.


## How do CET and CEST change the UTC calculation?

CET adds one hour to UTC, while CEST adds two. Converting a local appointment back to UTC therefore means subtracting one or two hours, so the same 14:00 clock label produces different reference times when Berlin changes between its winter and summer rules.


Keep the sign straight.


| Label | Offset | UTC equivalent of 14:00 local | Berlin example date |
| --- | --- | --- | --- |
| CET | UTC+01:00 | 13:00 | 15 January 2026 |
| CEST | UTC+02:00 | 12:00 | 15 July 2026 |

Method: computed with Luxon using Europe/Berlin on the two dates. Sources: [IANA's local-time database](https://www.iana.org/time-zones) and [its update history](https://data.iana.org/time-zones/tzdb/NEWS), as of 17 November 2026.


Our [meeting-time abbreviation guide](https://meet.barq.dev/glossary/time-zone-abbreviations) explains why a short label doesn't replace the date or establish the location you meant. Keep those inputs together in manual invitations.


## What goes wrong if you write CET for Berlin in July?

Writing CET for an appointment intended to follow Berlin's July clock gives a one-hour-later instant when the recipient reads the label literally. For 15 July 2026 at 10:00 Berlin time, the intended UTC start is 08:00; 10:00 at fixed UTC+01:00 becomes 09:00 UTC.


The conversion is consistent. The wording is the problem: the sender meant summer-local time but supplied the standard-time offset instead.


Those values were computed with Luxon using Europe/Berlin and a fixed plus-one offset. Say "15 July 2026, 10:00 Berlin time" when the city determines the hour, then check the invitation before sending it.


Don't assume "European time" fixes the ambiguity. State the location whose clock governs the meeting, especially when other participants arrange appointments across several regions.


## When do Berlin's CET and CEST clocks change?

The checked EU transition schedule gives 29 March and 25 October for 2026, with changes at 01:00 UTC. The corresponding dates are 28 March and 31 October for 2027; local clock readings at the transition depend on the applicable offset.


Check each participant's dates. Sources: timeanddate's [2026 spring changes](https://www.timeanddate.com/time/dst/2026a.html), [2026 autumn changes](https://www.timeanddate.com/time/dst/2026b.html), [2027 spring changes](https://www.timeanddate.com/time/dst/2027a.html) and [2027 autumn changes](https://www.timeanddate.com/time/dst/2027b.html), as of 17 November 2026.


The [daylight saving term explained](https://meet.barq.dev/glossary/daylight-saving-time) covers why skipped and repeated clock hours matter. The [scheduling terms index](https://meet.barq.dev/glossary/scheduling-glossary) connects those seasonal changes to named zones and offsets.


## How should Berlin availability be configured in Barq Meet?

Use Europe/Berlin when your offered hours should follow Berlin's local clock. We use the availability schedule's named zone to interpret those hours, so a summer appointment doesn't depend on the host remembering to replace a fixed CET offset manually.


We let guests choose a separate display zone. We then check the host's selected Google calendars at booking submission, because a correct clock conversion still needs a conflict-free appointment.


Check the final calendar invitation. An appointment viewed in another zone can have different digits while describing the same instant; use rescheduling if the actual reserved time needs to change. Check [Pacific standard and daylight time](https://meet.barq.dev/glossary/pst-vs-pdt) before applying the same abbreviation to every occurrence of a continuing west-coast appointment.


The Google-only host connection matters if your real diary is elsewhere. A Berlin zone selection won't make Outlook or iCloud events participate in conflict checking.


Review [the supported scheduling features](https://meet.barq.dev/pricing), then [offer appointments using Berlin's named local zone](https://meet.barq.dev/app/sign-in) after checking a date in each season.

## Frequently asked questions

### Is CEST two hours ahead of CET?

No. CEST is two hours ahead of UTC, while CET is one hour ahead of UTC. The difference between CET and CEST is therefore one hour, which is the error caused by substituting one label for the other. Compare both abbreviations with UTC on the stated date, instead of adding their two offset values to each other.

### Can a fixed CET meeting be intentional in summer?

Yes. A fixed UTC+01:00 commitment can be deliberate, but it won't follow Berlin's July local clock hour. Say explicitly that the offset is fixed so participants don't reinterpret it as a city-local appointment. Say explicitly that the appointment follows a fixed offset if that is your agreement, instead of a city's changing local clock.

### Should I use one CET conversion for the whole year?

Only when the commitment intentionally follows a fixed plus-one offset. If the agreement follows a place such as Berlin, use its named zone and dated rules so summer appointments keep the intended local hour. Use the dated city's rules for a continuing conversation, and check a future occurrence after the seasonal transition before distributing the schedule.

## Related pages

- [Time zone abbreviations list for scheduling](https://meet.barq.dev/glossary/time-zone-abbreviations)
- [What is daylight saving time (for schedulers)?](https://meet.barq.dev/glossary/daylight-saving-time)
- [Scheduling glossary: booking and calendar terms explained](https://meet.barq.dev/glossary/scheduling-glossary)
- [PST vs PDT: what's the difference?](https://meet.barq.dev/glossary/pst-vs-pdt)

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