How the EST to PST Conversion Actually Works
The quick answer is 10 AM. One PM Eastern Standard Time converts to ten in the morning Pacific Standard Time because there is a three-hour gap between the two zones. But the reason this question keeps coming up in my inbox is that people tend to assume the math never changes. It does. I spent about forty-five minutes on a conference call last November trying to figure out why my counterpart kept showing up an hour late to our syncs. Turns out their system was auto-converting to PDT while I was manually computing against PST. We were technically three hours apart, but one side had already rolled forward for daylight saving and the other hadn't, so the real offset was only two hours for that window. The calculation itself is trivial. You subtract three hours from the Eastern time and you land on Pacific. One PM minus three hours gets you ten AM. That rule holds whenever both zones are sitting on standard time, which runs roughly from early November to mid-March. The problem is the six weeks in spring and the three weeks in fall when one side has switched to daylight time and the other hasn't yet. During those gaps the offset shrinks to two hours instead of three, and if you are booking something across that boundary you will absolutely mess it up if you just do mental math. I keep a little spreadsheet open with the exact DST transition dates for both zones because relying on memory has cost me more scheduling headaches than I care to admit. The US rules changed after 2007, so anything older than that on your calendar probably has the wrong window marked. If you are working with systems that predate that change, double check the dates before you commit to anything.
There is also the edge case of places in North America that do not observe DST at all, like most of Indiana now and portions of Kentucky and Michigan. If your EST contact happens to be in one of those areas, they might still be on what they call Eastern Time but which is actually UTC-5 year-round while the Pacific side flips to UTC-7. The offset becomes two hours for part of the year and four hours at other points, which makes a single conversion rule useless. In practice I just ask people where they are before I schedule anything across time zones, and I verify with a tool rather than trusting my assumptions. If you want a free way to handle this without opening a converter every time, most operating systems have built-in world clock support. Windows lets you add a second time zone in Settings, macOS has the clock menu showing multiple zones, and Linux users can set TZ environment variables. The Linux approach is probably the cleanest if you are scripting something. You set your working directory TZ to America/New_York, run the conversion, then switch it to America/Los_Angeles. It eliminates the manual subtraction entirely and handles DST transitions automatically. One thing people overlook is that the abbreviation matters. EST specifically means standard time, but a lot of software and websites use "EST" as a blanket label even when daylight saving is in effect, when the correct abbreviation would be EDT. If you see 1 PM EST listed on a calendar invite during July, that is almost certainly EDT in disguise, and the actual conversion to PST would be 10 AM Pacific daylight time, not standard. The three-hour rule still applies, but the label is wrong and that tends to cause confusion when people argue about it afterward.
For bulk conversions or repetitive scheduling tasks, Python with the pytz or zoneinfo libraries handles this cleanly. You parse the time string, localize it to America/New_York, convert to America/Los_Angeles, and let the library manage the offset. It takes about thirty seconds to write once and saves you from manual arithmetic going forward. JavaScript equivalents exist too, though Node's built-in Intl.DateTimeFormat is finicky with certain edge-case date pairs and will sometimes return unexpected results around the transition boundaries. The real takeaway here is that 1 PM EST to PST is almost always 10 AM Pacific, but assuming it is always ten o'clock will get you in trouble twice a year. Verify the DST status of both zones before locking in any appointment, and don't trust abbreviations you see on unsourced websites. The offset is consistent only when both sides are on the same type of time, and that is not the case every day of the year.
Get the Full Details
