How to Convert Time Zones: EST to PST, Daylight Saving and the Business-Hours Overlap

“Let’s meet at 3” is a complete sentence only inside one time zone. Add a second city and it becomes a small research project: how many hours apart are we, is daylight saving in force, and whose date is it by then? Getting it wrong is not a rounding error — it is a missed flight connection, a webinar started to an empty room, or a client call placed at 4 AM their time. This guide explains how time zone conversion actually works, how to use our time zone converter — six zones, daylight saving applied from the date you pick, and a business-hours overlap shown with every result — and walks a real conversion through UTC step by step.

How to Convert a Time, Step by Step

1. Type the time. Enter it as it was given to you — for example, 3:00 PM — in its own zone, not pre-adjusted in your head. 2. Pick the date. This is the step every mental calculation skips and the converter insists on: the date decides whether daylight saving time applies in each zone, which can shift the result by a full hour. 3. Choose the from and to zones. Six options cover the four mainland US zones — Eastern, Central, Mountain, Pacific — plus GMT/UTC and Central European Time. 4. Press Convert Time and read all four result lines. You get the converted time with the correct abbreviation (EST vs EDT, PST vs PDT), the target weekday and date with a “next day” or “previous day” note when midnight is crossed, a daylight saving summary for both zones, and the overlap of normal business hours — for ET to PT, 12:00 PM – 5:00 PM ET, which is 9:00 AM – 2:00 PM PT.

How Conversion Works: Everything Routes Through UTC

Every time zone is an offset from Coordinated Universal Time. In standard time, Eastern is UTC−5, Central UTC−6, Mountain UTC−7, Pacific UTC−8, GMT is UTC+0 and Central European Time is UTC+1. The converter subtracts the from-zone’s offset to recover the UTC moment, then adds the to-zone’s offset — routing through UTC is what keeps the signs straight. Daylight saving moves the offsets: US zones spring forward on the second Sunday of March and fall back on the first Sunday of November, so Eastern becomes UTC−4 and Pacific UTC−7. Central Europe follows EU rules — forward on the last Sunday of March, back on the last Sunday of October, when CET becomes CEST at UTC+2. If you also need to know how long a meeting or a layover lasts once it is placed, our time duration calculator handles the interval maths.

Worked Example: 3:00 PM Eastern on July 15, 2026

Step 1, check daylight saving: a July date sits inside US daylight saving (March 8 to November 1 in 2026), so Eastern is EDT at UTC−4 and Pacific is PDT at UTC−7. Step 2, convert to UTC: 3:00 PM minus −4 hours is 7:00 PM UTC. Step 3, convert UTC to Pacific: 7:00 PM plus −7 hours is 12:00 PM PDT. Step 4, check the working-day fit: ET 9-to-5 is 1 PM – 9 PM UTC and PT 9-to-5 is 4 PM – 12 AM UTC, so the business-hours overlap is 12:00 PM – 5:00 PM ET (9:00 AM – 2:00 PM PT) — a noon Pacific call sits comfortably inside it. Notice what did not change: the 3-hour ET–PT gap is the same in January, because both zones shift on the same weekends. What does change is the transatlantic gap — New York to Berlin is 6 hours most of the year, but 5 hours for the few weeks each spring and fall between the US and EU switch weekends. Knowing what a badly-timed recurring meeting costs is its own calculation, and our meeting cost calculator prices exactly that.

Daylight Saving: The Weeks That Break Recurring Meetings

Most conversion errors are not offset errors; they are calendar errors. A weekly New York–Berlin call set up in February quietly moves an hour in late March, because the US springs forward on the second Sunday of March while Europe waits until the last Sunday — then moves again in autumn, when Europe falls back on the last Sunday of October and the US a week later. Twice a year the gap is 5 hours instead of 6, for two to three weeks at a time. Within the US this never happens between the four mainland zones, since they all switch together — but any recurring arrangement that crosses the Atlantic, or reaches a fixed-UTC commitment like a server cron job or a flight schedule, passes through both mismatch windows every year. The practical rule: convert with the actual date of the meeting, never with today’s offsets, and re-check any recurring transatlantic time in the last week of March and the last week of October.

Common Mistakes

Writing EST in July. In summer the zones are EDT and PDT; the letters are not decoration — a contract or calendar invite that says EST for a July meeting is off by an hour for anyone who reads it literally. Converting the time but not the date. Cross enough zones and the answer falls on the next or previous day; the converter flags this, mental maths usually doesn’t. Assuming New York to Berlin is always 6 hours. For a few weeks each spring and fall it is 5, and recurring meetings drift if nobody re-checks. Scheduling at the edge of the overlap. A 9 AM Pacific / noon Eastern start is the earliest both sides are at their desks; earlier is someone’s pre-work favour, and it should be labelled as one. Forgetting that “Central” is ambiguous. In this converter CET is Central European Time — a US colleague who hears “Central” and thinks Chicago is six hours adrift before the meeting even starts.

A meeting that spans zones produces a recording that spans hours. The Silence Chapters tool finds the natural breaks in that recording — the pauses — and exports each segment as its own clip, ready to share with the people who were asleep in the other hemisphere.

Frequently Asked Questions

More guides from ToolNest