Convert CEST (Central European Summer Time) to EST (Eastern Standard Time)

Best time to schedule a meeting

Standard 9–5 working hours overlap for 1 hour: 4:00 PM–5:00 PM CEST (9:00 AM–10:00 AM EST). Schedule meetings inside that window.

CEST to EST conversion table

About CEST

Central European Summer Time (CEST) is UTC+2. It is used in Paris, Berlin, Madrid and Rome from late March to late October.

Central European Summer Time is UTC+2, in force from the last Sunday in March to the last Sunday in October. The European changeover happens at 01:00 UTC everywhere simultaneously, unlike the US which changes at 2am local time in each zone — so Europe's internal offsets never break during the transition, while North America's briefly do.

About EST

Eastern Standard Time (EST) is UTC−5. It is used in New York, Toronto, Miami and Atlanta in winter.

Eastern Standard Time is UTC−5 and applies in New York, Toronto, Miami and Atlanta only from November to March. For the other eight months those cities are on EDT, UTC−4. Americans routinely write "EST" year-round to mean "east coast time", so a date given as EST in July is usually meant as EDT and is an hour earlier than written — one of the most common scheduling errors there is. Note also that Panama and Jamaica are on UTC−5 all year and never switch.

Does this gap change with the seasons?

This gap is seasonal. The abbreviations themselves are fixed offsets, but the region on CEST switches to CET (UTC+1) from late October to late March, and the region on EST switches to EDT (UTC−4) from March to November. So the 7-hour figure on this page is correct for the part of the year when both places are actually on these abbreviations, and changes by an hour outside it.

Because both sides shift, there are also short windows each spring and autumn when one has changed and the other has not — the two regions do not switch on the same date. A recurring meeting set during one of those windows is an hour out for a week or two, which is the most common way this catches people.

This is the reason scheduling systems store an IANA zone such as Region/City rather than an offset or an abbreviation: the zone knows its own rules and the offset does not.

Frequently asked questions