CST to EST: US Time Zone Conversion Explained

Central Standard Time is one hour behind Eastern Standard Time. To convert CST to EST you add an hour, so 9:00 AM CST is 10:00 AM EST. That single sentence answers the question most people arrive with, and for roughly half the year it is the whole story.

The other half of the year is where conversions quietly break. The gap between Central and Eastern stays at one hour all year, but the offsets on both sides move, and the abbreviation you were given may no longer describe the offset you need. This guide covers the arithmetic for every US zone pair, the daylight saving trap that causes most wrong answers, and how UTC, GMT and IST map onto US clocks.

CST to EST conversion chart

Add one hour. The table covers the times people look up most often.

That last row is worth pausing on. 11:00 PM in Chicago is already midnight in New York, so a Tuesday evening call at 11:00 PM Central is logged as Wednesday by anyone in Eastern. Conversions that cross midnight change the date, not only the clock, and a calendar invite built on the wrong date is harder to spot than one built on the wrong hour.

EST to CST, the same conversion in reverse

Going the other way you subtract an hour.

The letter in the middle changes the answer

CST and CDT are not two names for the same thing. The S stands for standard, the D stands for daylight, and they sit an hour apart.

Central Standard Time is UTC-6:00 and runs through the winter. Central Daylight Time is UTC-5:00 and runs from the second Sunday in March to the first Sunday in November. Eastern behaves the same way, moving from EST at UTC-5:00 to EDT at UTC-4:00 on those same dates.

Because both zones move together, the Central to Eastern gap is one hour in January and one hour in July. This is why people get away with the simple rule most of the time. The rule breaks in two specific situations.

The first is converting to or from a zone that does not move. Arizona stays on Mountain Standard Time all year. In winter, Arizona and Denver read the same clock. In summer, Denver moves to MDT and Arizona does not, so Arizona then matches Los Angeles instead. The gap between Phoenix and almost everywhere else changes twice a year even though Phoenix never touches its clocks.

The second is converting between a US zone and a country on a different daylight saving schedule. Europe changes its clocks on the last Sunday in March and the last Sunday in October, which does not line up with the US dates. For about two weeks each spring and one week each autumn, the gap between New York and London is four hours rather than the usual five.

The four zones of the contiguous United States

Each zone steps one hour from its neighbour, which makes the full set easy to hold in your head once the order is clear: Pacific, Mountain, Central, Eastern, running west to east and getting later as you go.

A few of the pairs people search for most, spelled out:

• Pacific time to central time adds two hours. 9:00 AM PST is 11:00 AM CST.
• PST to EST adds three hours. 9:00 PM PST is 12:00 AM EST, already the next day.
• Mountain time to eastern time adds two hours. 10:00 AM MST is 12:00 PM EST.
• Mountain time to central time adds one hour. 10:00 AM MST is 11:00 AM CST.
• MST to PST subtracts one hour. 10:00 AM MST is 9:00 AM PST.

Alaska sits one hour behind Pacific at UTC-9:00, and Hawaii sits two hours behind Pacific at UTC-10:00 and never changes its clocks. In summer, when the mainland has moved forward, the gap from Hawaii to the west coast stretches to three hours.

Eastern to Pacific, hour by hour

The three hour gap between the two coasts causes more scheduling friction than any other US pair, because it eats most of a working day. A 9:00 AM meeting on the east coast is a 6:00 AM meeting on the west coast, and a 5:00 PM finish in California is 8:00 PM in New York.

Reading the table the other way gives the Pacific to Eastern direction: 9:00 AM PST is 12:00 PM EST, and 9:00 PM PST is 12:00 AM EST on the following day.

The practical overlap between a standard nine to five on both coasts is 9:00 AM to 2:00 PM Pacific, which is 12:00 PM to 5:00 PM Eastern. Five hours. Anything outside that window asks somebody to start early or finish late, and a recurring call scheduled at the edge of it will collide with the daylight saving changeover at some point in the year.

The same abbreviation can mean two different zones

Zone abbreviations are not unique, and a few of the collisions sit on opposite sides of the planet.

A message reading "the call is at 9am CST" sent between a US office and a Chinese one is ambiguous by fourteen hours. The safest habit for anything crossing borders is to write the offset alongside the abbreviation, as in "9:00 AM CST (UTC-6:00)", or to state the city. Nobody misreads "9:00 AM in Chicago".

Why the United States has these zones at all

Before 1883 there was no such thing as Central or Eastern time. Towns kept their own solar noon, so clocks in Pittsburgh and Philadelphia genuinely disagreed, and it did not matter much while travel between them took days.

Railways made it matter. A timetable needs a shared clock, and by the 1880s American railroads ran on dozens of competing local times. On 18 November 1883 the railway companies adopted four standard zones by agreement, ahead of any law requiring it. Congress followed with the Standard Time Act in 1918, putting the zones into federal law and introducing daylight saving at the same time.

Daylight saving then spent decades being switched on and off: repealed nationally in 1919, brought back during the Second World War, then left to individual states, producing a patchwork where neighbouring towns changed clocks on different dates. The Uniform Time Act of 1966 fixed the schedule nationally while letting states opt out entirely, the provision Arizona and Hawaii use. The current March to November dates come from the Energy Policy Act of 2005.

States can opt out of daylight saving but cannot unilaterally pick a different zone, which is why Arizona stays on Mountain Standard Time rather than moving permanently to Pacific. The opt-out is at state level, which is why Indiana spent decades as a special case and why parts of it still sit in a different zone from the rest.

Daylight saving dates and the weeks when the gap changes

The United States moves its clocks on the second Sunday of March and the first Sunday of November. Europe moves on the last Sunday of March and the last Sunday of October. Because the dates differ, the gap between New York and London is not constant.

In 2026 the US moves forward on March 8 and Europe on March 29, so for three weeks New York is 4 hours behind London instead of 5. In the autumn Europe moves back on October 25 and the US on November 1, which creates one more week at 4 hours. Arizona and Hawaii never change, so their gap to every other zone shifts twice a year. Check the date, not just the zone, when converting in those windows.

Converting UTC and GMT to US time zones

UTC is the reference every other offset is measured from. GMT describes the same offset in everyday use, so for converting a meeting time the two behave identically.

To go from UTC to a US zone, subtract the zone's offset.

Notice how many cells land on the previous day. UTC-05:00 through UTC-08:00 means US clocks are behind UTC by a third of a day, so anything scheduled in UTC before mid-morning falls on the previous evening in North America. Flight schedules, server logs and international call times all trip over this.

In summer the subtraction shrinks by an hour on every US column, because each zone has moved to its daylight offset. 12:00 UTC is 7:00 AM EST in January and 8:00 AM EDT in July.

IST to EST and other long-haul conversions

India Standard Time is UTC+5:30, one of the offsets that is not a whole number of hours. Converting IST to EST means going back ten and a half hours, which usually changes the date as well.

7:30 PM IST is 9:00 AM EST the same day. 9:00 AM IST is 10:30 PM EST the previous day. The half hour is easy to drop when doing this in your head, and dropping it produces an answer that looks plausible and is wrong by thirty minutes.

Nepal goes further with UTC+5:45, a forty-five minute offset. Iran uses UTC+3:30 and parts of Australia use UTC+9:30. Any conversion involving these needs the minutes carried through rather than rounded to the nearest hour.

City and country time differences people search for

A handful of places account for a disproportionate share of time zone searches. Their offsets, plainly stated:

Time to Cancun. Quintana Roo, the Mexican state Cancun sits in, moved to UTC-5 year-round in 2015 and does not observe daylight saving, so it matches Eastern Standard Time all year and briefly matches Central Daylight Time each summer.

Time to Colorado. Mountain time, UTC-7 in winter and UTC-6 in summer, same as the rest of the Mountain zone covered earlier.

Time to Ireland. UTC+0 in winter and UTC+1 in summer under the name Irish Standard Time, which confusingly refers to the summer offset, not the winter one.

Dallas, Texas time difference and Memphis time difference. Both Central time, UTC-6 in winter and UTC-5 in summer, identical to the CST and CDT already covered above.

Time to Bangkok. UTC+7 year-round with no daylight saving, one of the simpler conversions here since the offset never changes.

Time difference Nepal. UTC+5:45, covered above, worth repeating since "time difference Nepal" is a common way people search for the same fifteen minute gap from India.

Time to Abu Dhabi. UTC+4 year-round.

Time difference Indianapolis. Eastern zone, UTC-5 in winter and UTC-4 in summer, why the Indiana FAQ above only flags the counties that differ, not the city itself. Louisville KY time zone and the Virginia time zone are also both Eastern. Wisconsin time zone is Central; Detroit time zone is Eastern, the correct side of the Michigan split mentioned earlier.

Time to Brisbane. Queensland opted out of daylight saving, so it stays on UTC+10 all year while the rest of eastern Australia shifts between UTC+10 and UTC+11.

Time zones Hawaii to west coast. Hawaii is fixed at UTC-10, so its gap to the west coast is two hours in winter and three in summer once Pacific time moves to PDT.

Time difference in Georgia. The US state, not the country: Eastern time, UTC-5 in winter and UTC-4 in summer.

Norwegian time difference. Central European Time, UTC+1 in winter and UTC+2 in summer, the same offset already covered for CET to EST.

Three mistakes that account for most wrong answers

Using the abbreviation someone else wrote without checking the date. If a colleague writes "3pm CST" in July, they almost certainly mean 3pm Central, which is CDT in July. Treating it literally as CST puts the meeting an hour out. When the date and the abbreviation disagree, the date is usually right and the abbreviation is shorthand.

Forgetting that the date can change. Any conversion spanning enough hours crosses midnight. A 9:00 PM PST call is a midnight EST call on the following date. Check the day of the week on the result, not only the time.

Assuming everyone changes clocks on the same day. The US and Europe both observe daylight saving and do it on different dates. The window where their usual gap is off by an hour is short, and it reliably catches out recurring meetings set up months earlier.

Working it out without the mental arithmetic

The time zone calculator takes a date, a time and the two zones, and returns the converted time with the calendar date attached, so a conversion that crosses midnight is visible rather than assumed. Zones are listed by the names used here, with EST and EDT as separate entries, so the standard or daylight choice is explicit instead of guessed.

For working out how long something lasts rather than what it reads elsewhere, the time calculator adds and subtracts durations, and the hours calculator totals hours worked across a set of start and finish times. If the question is how many days sit between two dates rather than how many hours, the date calculator covers that.