Let's Sort This Out
Georgia is in the Eastern Time Zone. That's the whole answer, honestly. But the confusion around it makes sense if you've ever tried to explain US time zones to someone or set up a conference call across the country. There are four main time zones in the continental US: Eastern, Central, Mountain, and Pacific. Alaska and Hawaii have their own. Some states are split between zones, and some territories don't follow daylight saving time at all. That's where people get tripped up.
Is Georgia In The Eastern Time Zone Clarifying The Confusion Around Us State Time Zones
Georgia has always been on Eastern Time. It observes daylight saving time like most of the country. That means UTC-5 in standard time and UTC-4 during DST, which runs from the second Sunday in March to the first Sunday in November. I once spent about forty-five minutes trying to figure out why a client in Savannah was showing up as being three hours off during a video demo. The issue wasn't Georgia's zone at all. Their laptop was set to Central time because they'd previously worked for a company headquartered in Atlanta but scheduled their team meetings using Chicago time by habit. The system had picked up the wrong zone from their old configuration. I had them run timedatectl on Linux or check the system tray on Windows, switch it to America/New_York, and everything synced up. Took about two minutes after the investigation. Here's the thing most people miss: time zone boundaries don't follow state lines neatly. You can drive ten miles in some places and cross from Eastern to Central. That happened to me once in northwest Florida near the Alabama border. I was scheduling something and assumed the whole state was one zone. It isn't. Jackson, Liberty, and Walton counties in the Florida Panhandle are on Central Time. If you're booking a call with someone in Panama City and someone in Miami, they're in different zones even though both are in Florida.
The same problem exists in Indiana. Before 2006, several counties in the northwest and southwest corners of the state were on Central Time while the rest was Eastern. Now most of Indiana is on Eastern, but a few counties near Chicago and Cincinnati still observe Central. If you're writing software that handles schedules and you only map "Indiana = Eastern," you'll have bugs. I learned this the hard way when a delivery notification went out at the wrong local time to a warehouse in Evansville. Another thing that trips people up is the difference between a state and a time zone. Arizona doesn't observe DST except for the Navajo Nation, which does. So most of Arizona stays on MST year-round, which is the same offset as PDT during the summer. If you schedule something at noon Arizona time in July, that's 1 PM in Georgia. People forget to account for that shift and assume "no DST means no change," which is true for the offset but not for how it compares to states that do change.
Get the Full Details
How to Actually Get This Right
Stop using named offsets like "EST" or "CST" in your code or documentation. Those are ambiguous. EST is UTC-5, but so is Eastern Daylight Time, which people sometimes incorrectly label as EST when they mean EDT. Use IANA timezone identifiers instead. For Georgia, that's America/New_York. For the Florida Panhandle counties I mentioned, it's America/Chicago. If you're building something that handles dates and times, store everything in UTC internally. Convert to local time only at the edges when you're displaying to a user or sending a notification. This single practice will eliminate about eighty percent of the bugs I see in production involving time zones. There's a gotcha though. The IANA database gets updated regularly when governments change their time zone rules. I had a situation where a client's calendar integration broke because a policy change in a territory we didn't even serve got rolled into an automatic update. We pinned our timezone data to a specific version of the tz database and set up a quarterly review cycle. It added maybe twenty minutes of maintenance per quarter and prevented a production outage that would have cost us several days of debugging.
For regular people just trying to remember which state is in which zone, here's a quick reference that actually works. Eastern Time covers Maine, New Hampshire, Vermont, Massachusetts, Rhode Island, Connecticut, New York, New Jersey, Pennsylvania, Delaware, Maryland, Virginia, West Virginia, North Carolina, South Carolina, Georgia, Florida (most of it), Kentucky (most of it), Tennessee (most of it), Michigan, Ohio, Indiana (most of it), Alabama, Mississippi, and the District of Columbia. If you're in one of those places and someone says "let's meet at three Eastern," you know what they mean. Central Time covers Texas, Oklahoma, Kansas, Nebraska, South Dakota, North Dakota, Minnesota, Iowa, Missouri, Arkansas, Louisiana, Wisconsin, Illinois, Mississippi (part), Alabama (part), Tennessee (part), Kentucky (part), and the Florida Panhandle. Mountain Time covers Colorado, Utah, Arizona (mostly), New Mexico, Montana, Wyoming, and parts of Idaho. Pacific Time covers California, Oregon, Washington, Nevada, and parts of Idaho. The real confusion comes from the parts that don't fit neatly into those lists. Most of it is just remembering that state lines and time zone lines aren't the same thing. Once you accept that, the rest is memorization or a quick lookup.
