UTC to EST Converter · Free UTC to Eastern Time Calculator

Live UTC and EST Clocks

These clocks update in real-time using your device's system clock. The EST/EDT display automatically adjusts based on whether daylight saving time is currently in effect.

UTC to EST Converter Tool

Enter any UTC date and time below to convert it to Eastern Time. The converter automatically accounts for daylight saving time, so you always get the correct EST or EDT result.

How to Convert UTC to EST

Converting UTC to Eastern Time is a simple subtraction. The exact number of hours to subtract depends on whether daylight saving time (DST) is in effect.

During Standard Time (EST)

Eastern Standard Time is UTC minus 5 hours. To convert, subtract 5 from the UTC hour.

• UTC 14:00 (2:00 PM) = EST 09:00 (9:00 AM)
• UTC 20:00 (8:00 PM) = EST 15:00 (3:00 PM)
• UTC 03:00 (3:00 AM) = EST 22:00 (10:00 PM) the previous day

During Daylight Saving Time (EDT)

Eastern Daylight Time is UTC minus 4 hours. To convert, subtract 4 from the UTC hour.

• UTC 14:00 (2:00 PM) = EDT 10:00 (10:00 AM)
• UTC 20:00 (8:00 PM) = EDT 16:00 (4:00 PM)
• UTC 03:00 (3:00 AM) = EDT 23:00 (11:00 PM) the previous day

Handling Day Boundaries

When the subtraction results in a negative number, add 24 and go back one calendar day. For example, UTC 02:00 on March 15 converted to EST becomes 21:00 (9:00 PM) on March 14. This day-boundary issue is one of the most common sources of confusion when scheduling across time zones.

UTC to EST 24-Hour Conversion Table

This table shows every hour of the day converted from UTC to both EST (UTC-5) and EDT (UTC-4). Use the EST column during standard time (November through March) and the EDT column during daylight saving time (March through November).

Tip: Bookmark this table if you frequently convert between UTC and Eastern Time. The business hours overlap (13:00-21:00 UTC = 9 AM-5 PM EST) is especially useful for scheduling meetings with colleagues or clients in the Eastern time zone.

Daylight Saving Time Rules (EST vs EDT)

The distinction between EST and EDT is one of the most important factors in precise time conversion. Getting it wrong means your conversion is off by a full hour.

When DST Begins (Spring Forward)

Daylight saving time in the United States begins on the second Sunday of March at 2:00 AM local time. At that moment, clocks jump forward to 3:00 AM. This means the Eastern time zone switches from EST (UTC-5) to EDT (UTC-4). The 2:00 AM hour does not exist on that day.

When DST Ends (Fall Back)

Daylight saving time ends on the first Sunday of November at 2:00 AM local time. Clocks move back to 1:00 AM, and the Eastern time zone switches from EDT (UTC-4) back to EST (UTC-5). The 1:00 AM hour occurs twice on that day, which can cause confusion for time-sensitive applications.

DST Dates for Upcoming Years

The Permanent DST Debate

The U.S. Senate passed the Sunshine Protection Act in 2022, which would have made daylight saving time permanent year-round. However, the bill did not pass the House of Representatives. As of 2024, the biannual clock change remains in effect. Several states have passed laws to adopt permanent DST, but they cannot take effect until federal law changes.

Countries That Use Eastern Time

The Eastern Time zone is not limited to the United States. Parts of Canada (Ontario, Quebec), the Bahamas, Haiti, Cuba, Panama, and the Turks and Caicos Islands also observe Eastern Time. However, not all of these jurisdictions follow the same DST rules. Cuba and Haiti have their own DST schedules, which may differ from the U.S. by a few weeks.

World City Clocks

See the current time in major cities around the world. All clocks update live based on your system time.

Meeting Time Scheduler

Planning a meeting across time zones? Select a UTC time and see what it looks like in multiple time zones simultaneously. Green-highlighted slots indicate business hours (9 AM to 5 PM) in that time zone.

What Is UTC (Coordinated Universal Time)

UTC is the primary time standard by which the world regulates clocks and time. It is the successor to Greenwich Mean Time (GMT) and serves as the reference point for all other time zones.

How UTC Is Maintained

UTC is determined by a network of over 400 atomic clocks located in more than 80 national laboratories around the world. The International Bureau of Weights and Measures (BIPM) in Paris, France, coordinates these clocks to produce the most precise time possible. Atomic clocks measure time using the vibrations of cesium-133 atoms, which oscillate at exactly 9,192,631,770 times per second.

UTC vs GMT

While UTC and GMT are functionally the same time (both representing the time at the Prime Meridian, 0 degrees longitude), they differ in how they are measured. GMT is based on astronomical observations of the sun's position, while UTC is based on atomic clocks. UTC is occasionally adjusted by adding leap seconds to keep it within 0.9 seconds of astronomical time. The last leap second was added on December 31, 2016.

Why UTC Matters

UTC provides a single, unambiguous time reference that is not affected by time zones or daylight saving time. This makes it important for international coordination. Airlines, military operations, weather reporting, financial markets, and computer networks all rely on UTC as their baseline time standard.

What Is EST (Eastern Standard Time)

Eastern Standard Time (EST) is the time zone used by the eastern portion of North America during the non-DST months (typically November through March). It is defined as UTC minus 5 hours (UTC-5).

Geographic Coverage

The Eastern Time zone covers 23 U.S. states (fully or partially), including the District of Columbia. Major population centers include New York City (8.3 million), Philadelphia (1.6 million), Miami (6.2 million metro), Atlanta (6.1 million metro), Boston (4.9 million metro), Washington D.C. (6.3 million metro), Detroit (4.3 million metro), and Charlotte (2.7 million metro).

In Canada, the Eastern Time zone includes Ontario (including Toronto and Ottawa) and Quebec (including Montreal and Quebec City). The Eastern Time zone covers approximately 47% of the U.S. population, more than any other time zone.

EST in Financial Markets

The New York Stock Exchange (NYSE) and NASDAQ operate on Eastern Time, with regular trading hours from 9:30 AM to 4:00 PM ET. This makes Eastern Time the de facto time zone for U.S. financial markets. Global traders convert from their local time zones to ET to track market hours. Pre-market trading begins at 4:00 AM ET, and after-hours trading extends until 8:00 PM ET.

UTC in Aviation (Zulu Time)

The aviation industry uses UTC exclusively, referring to it as "Zulu time" (designated by the letter Z). This practice eliminates confusion when flights cross multiple time zones.

Why Aviation Uses Zulu Time

A flight from New York to London crosses five time zones. If pilots and air traffic controllers used local time, every handoff between control centers would require a time conversion, increasing the risk of errors. By using a single time reference (UTC/Zulu), everyone in the aviation system is on the same clock.

Zulu Time Notation

In aviation, Zulu time is written with a "Z" suffix. For example, 1430Z means 2:30 PM UTC. METAR weather reports, NOTAM notices, and flight plans all use this format. If you see "ATIS information updated at 1800Z," that means 1:00 PM EST or 2:00 PM EDT.

Practical Examples

• A flight departing JFK at 6:00 PM EST departs at 2300Z (23:00 UTC)
• A flight landing at Heathrow at 7:00 AM GMT (UTC+0) lands at 0700Z
• A METAR issued at 1645Z translates to 11:45 AM EST or 12:45 PM EDT

UTC in Military Operations

Military forces worldwide use UTC for coordination, but they often reference time zones using the NATO phonetic alphabet. Each time zone is assigned a letter designation.

Military Time Zone Letters

When a military briefing states a time of "1400R," it means 2:00 PM in the Romeo time zone (UTC-5, equivalent to EST). The letter J (Juliet) is used for local time, regardless of which zone the observer is in.

Military Time Format

The military uses a 24-hour clock exclusively. There is no AM or PM. Hours run from 0000 (midnight) to 2359 (11:59 PM). This system eliminates the ambiguity of 12-hour time. "0800" is always 8:00 in the morning. "2000" is always 8:00 in the evening. Combined with the time zone letter, military time provides an unambiguous global time reference.

UTC in Programming and Databases

Software developers and database administrators work with UTC constantly. Storing and manipulating time data correctly is one of the most common challenges in software engineering.

Store in UTC, Display in Local Time

The standard best practice for handling time in software is to store all timestamps in UTC and convert to the user's local time zone only at the point of display. This approach avoids problems caused by daylight saving time transitions, users in different time zones, and server relocations.

JavaScript UTC Methods

JavaScript provides several built-in methods for working with UTC time:

• new Date().toISOString() returns the current time in UTC as an ISO 8601 string
• Date.UTC(year, month, day, hour, minute) creates a timestamp from UTC components
• date.getUTCHours() returns the hour in UTC (0-23)
• date.toLocaleString('en-US', {timeZone: 'America/New_York'}) converts to Eastern Time display

Database Timestamps

PostgreSQL offers the TIMESTAMP WITH TIME ZONE type, which stores values in UTC and converts them on output based on the session time zone. MySQL's TIMESTAMP type also stores in UTC internally. When designing schemas, always use timezone-aware timestamp types. Storing local times in a database without timezone information leads to bugs that are extremely difficult to track down, especially around DST transitions.

Unix Timestamps

Unix timestamps count the number of seconds since January 1, 1970, 00:00:00 UTC (the "Unix epoch"). This is a single integer that is inherently UTC-based and timezone-neutral. Converting between Unix timestamps and human-readable dates requires knowing the target time zone. The current Unix timestamp increases by exactly 1 every second, regardless of time zones or DST.

Python Time Zone Handling

Python developers should use the datetime module with timezone-aware objects. The pytz library (or the built-in zoneinfo module in Python 3.9+) provides proper timezone support. A common pattern is: from datetime import datetime, timezone; utc_now = datetime.now(timezone.utc). For converting to Eastern Time, use the zoneinfo.ZoneInfo('America/New_York') timezone. Never use naive datetime objects for cross-timezone work, as they have no timezone information and lead to subtle bugs.

ISO 8601 Time Format

ISO 8601 is the international standard for date and time representation. It is widely used in data exchange, APIs, and technical documentation. Understanding this format is important for anyone working with time data across systems.

Format Structure

The full ISO 8601 date-time format is: YYYY-MM-DDThh:mm:ss+hh:mm

• 2024-06-15T14:30:00Z means June 15, 2024 at 2:30 PM UTC (the "Z" suffix means Zulu/UTC)
• 2024-06-15T10:30:00-04:00 means the same moment expressed in EDT (UTC-4)
• 2024-06-15T09:30:00-05:00 means the same moment expressed in EST (UTC-5)

Why ISO 8601 Matters

ISO 8601 eliminates the ambiguity of date formats. Is "01/02/2024" January 2nd or February 1st? It depends on whether you are in the U.S. (MM/DD/YYYY) or Europe (DD/MM/YYYY). ISO 8601 always uses YYYY-MM-DD, which sorts chronologically and is universally unambiguous. Major APIs (including those from Google, Amazon, Microsoft, and GitHub) use ISO 8601 as their standard time format.

Duration Format

ISO 8601 also defines a format for time durations: P[n]Y[n]M[n]DT[n]H[n]M[n]S. For example, P1Y2M3DT4H5M6S means 1 year, 2 months, 3 days, 4 hours, 5 minutes, and 6 seconds. PT5H means a duration of 5 hours. This format is used in APIs, scheduling systems, and calendar applications.

History of Time Zones

Time zones as we know them are a relatively recent invention, driven by the practical needs of railroads and telecommunications.

Before Time Zones

Before the late 19th century, each city set its own local time based on the position of the sun. Noon was when the sun was at its highest point in the sky, and clocks were set accordingly. This meant that a city just 100 miles to the west might be 10-15 minutes behind. For local affairs, this worked fine. But railroads created a problem.

The Railroad Problem

By the 1870s, U.S. railroads maintained over 300 local time zones for scheduling purposes. A traveler going from Washington D.C. to San Francisco would pass through dozens of different local times. Scheduling was a nightmare, and the confusion contributed to rail accidents. In 1883, U.S. and Canadian railroads adopted a standardized system of four time zones (Eastern, Central, Mountain, Pacific), and on November 18, 1883, clocks across the country were reset.

International Standardization

In 1884, the International Meridian Conference in Washington D.C. established the Prime Meridian at Greenwich, England, and created the foundation for the global time zone system. Twenty-four time zones were defined, each spanning 15 degrees of longitude (360 degrees divided by 24 hours). The conference was attended by delegates from 25 nations.

The Birth of UTC

UTC was formally adopted in 1960 by the International Radio Consultative Committee. It replaced GMT as the world's time standard in 1972, when the current system of leap seconds was introduced. The name "UTC" was chosen as a language-neutral compromise. Neither the English abbreviation "CUT" nor the French "TUC" was selected, so UTC was agreed upon as a neutral option.

Leap Seconds Explained

Leap seconds are one of the most misunderstood aspects of timekeeping. They affect UTC directly and have real implications for computing, navigation, and scientific research.

Why Leap Seconds Exist

Earth's rotation is not perfectly constant. Tidal friction, movements of material within the Earth's core, and other factors cause the planet to speed up and slow down unpredictably. Atomic clocks, which define the length of a second, are far more precise than Earth's rotation. Over time, atomic time and Earth rotation time drift apart. Leap seconds are added to UTC to keep atomic time within 0.9 seconds of Earth rotation time (UT1).

How Leap Seconds Work

When a leap second is added, the last minute of the day contains 61 seconds instead of 60. The sequence goes: 23:59:58, 23:59:59, 23:59:60, 00:00:00. This extra second is always added at the end of June 30 or December 31 UTC. The International Earth Rotation and Reference Systems Service (IERS) decides when to add a leap second, typically with about six months notice.

Leap Seconds in Computing

Leap seconds have caused notable problems in computing. In 2012, a leap second caused widespread outages at Reddit, Mozilla, Yelp, and other sites because the Linux kernel had a bug in its leap second handling. In 2015, another leap second caused issues with Java-based systems. Google developed a technique called "leap smear" where they spread the extra second across a longer period, adding a tiny fraction of a second to each second over a 24-hour window. This avoids the sudden jump that causes software crashes.

The Future of Leap Seconds

In November 2022, the General Conference on Weights and Measures voted to abolish leap seconds by 2035. After that date, UTC will be allowed to drift further from Earth rotation time, with corrections potentially applied on a century timescale instead. This decision was driven by the increasing problems leap seconds cause in computing and telecommunications. Until 2035, leap seconds will continue to be added as needed.

Common Time Zone Mistakes

Converting between time zones is straightforward in theory but error-prone in practice. Here are the most frequent mistakes and how to avoid them.

• Confusing EST and EDT. EST (UTC-5) is used during standard time (November to March), and EDT (UTC-4) is used during daylight saving time (March to November). Using EST when you should use EDT (or vice versa) makes your conversion off by one hour. When in doubt, use "ET" (Eastern Time) without specifying standard or daylight.
• Forgetting day boundary crossings. When converting UTC times in the early morning hours (00:00-04:00 UTC), the Eastern Time result is on the previous calendar day. UTC midnight is 7:00 PM EST on the previous evening. Always check if your conversion crosses a day boundary.
• Assuming all countries change DST on the same date. The U.S. changes DST in March and November, but the EU changes in the last weekends of March and October. For a few weeks each year, the time difference between New York and London is 4 hours instead of the usual 5.
• Using deprecated timezone abbreviations. Timezone abbreviations like "EST" are ambiguous. EST could mean Eastern Standard Time in the U.S. or Eastern Standard Time in Australia (UTC+10). In software, always use IANA timezone identifiers like "America/New_York" instead of abbreviations.
• Hardcoding timezone offsets. Writing code that assumes EST is always -5 will break during EDT. Use timezone-aware libraries that handle DST transitions automatically.
• Not accounting for half-hour and 45-minute offsets. Not all time zones are whole-hour offsets from UTC. India (UTC+5:30), Nepal (UTC+5:45), and parts of Australia (UTC+9:30) use non-standard offsets.

UTC for Remote Teams and Global Collaboration

Remote work has made time zone management a daily challenge for millions of workers. Using UTC as a shared reference point simplifies coordination across global teams.

Setting Team Hours in UTC

Many distributed teams define their "overlap hours" in UTC rather than any local time zone. For example, a team might agree that everyone is available from 14:00 to 18:00 UTC. This translates to 9:00 AM - 1:00 PM EST, 2:00 PM - 6:00 PM GMT, and 11:30 PM - 3:30 AM IST (next day). While not all time zones can overlap during business hours, defining the window in UTC removes the ambiguity of "whose 2 PM are we talking about?"

Calendar Best Practices

When scheduling meetings across time zones, always include the UTC time in the invitation. A meeting scheduled for "2 PM" is meaningless without a time zone qualifier. Calendar applications like Google Calendar and Outlook handle this automatically by storing events in UTC and displaying them in each user's local time. However, when communicating via email or chat, explicitly stating "Tuesday at 18:00 UTC (1:00 PM EST / 6:00 PM GMT)" prevents confusion.

Asynchronous Communication

Many remote teams are shifting toward asynchronous workflows that reduce the need for simultaneous availability. Tools like Slack, Notion, and Linear allow team members to communicate across time zones without requiring real-time interaction. When async communication includes timestamps, using UTC or ISO 8601 format ensures that everyone interprets the time correctly regardless of their local time zone.

UTC in Project Management

Deadlines for distributed teams should always specify a time zone, preferably UTC. "Due by Friday" is ambiguous when your team spans from UTC-8 (Pacific) to UTC+5:30 (India). "Due by Friday 23:59 UTC" is clear and unambiguous. Most project management tools allow you to set deadlines with specific time zones, and using UTC as the standard simplifies this process.

Frequently Asked Questions

What time is it in EST right now?

The live clock at the top of this page shows the current Eastern Time. During daylight saving time (March to November), Eastern Time is EDT (UTC-4). During standard time (November to March), it is EST (UTC-5). The clock automatically reflects the correct one.

Is New York on EST or EDT right now?

New York follows the U.S. daylight saving time schedule. From the second Sunday of March to the first Sunday of November, New York is on EDT (UTC-4). The rest of the year, it is on EST (UTC-5). The DST badge on the live clock above shows which is currently in effect.

What is the difference between ET and EST?

ET (Eastern Time) is a general term that covers both EST and EDT. When someone says "the meeting is at 3 PM ET," they mean 3 PM in whatever Eastern Time variant is currently in effect. EST specifically means UTC-5 (standard time), while EDT means UTC-4 (daylight time). Using "ET" is safer because it adapts to the current season.

How many hours ahead is UTC compared to EST?

UTC is 5 hours ahead of EST. If it is 2:00 PM EST, it is 7:00 PM UTC. During EDT, UTC is 4 hours ahead. If it is 2:00 PM EDT, it is 6:00 PM UTC.

Does UTC ever change for daylight saving time?

No. UTC never changes. It remains constant throughout the year. Only local time zones shift during daylight saving time transitions. This is one of the main reasons UTC is used as the global reference standard.

External References and Resources

For official time standards and technical references, consult these authoritative sources:

• NIST Time and Frequency Division -- the U.S. National Institute of Standards and Technology maintains the official U.S. time standard and provides time services including the atomic clock network.
• BIPM (International Bureau of Weights and Measures) -- the international organization responsible for coordinating UTC from atomic clock data submitted by national laboratories worldwide.
• ISO 8601 Standard -- the international standard for date and time representation used in computing, aviation, and international communication.
• Time and Date -- World Time Zones -- a widely-used reference for current time zone information, DST transition dates, and city-level time data.

Other Free Tools

Check out these related tools from our free tools library: