Explore · time zones
EST to Mexico City converter
Eastern Time (New York) → Central Standard Time (Mexico) (Mexico City)
Quick answer
The difference changes with daylight saving time. Mexico City is 1 hour behind New York from Jan 1, 2026 to Mar 8, 2026 07:00 UTC (New York on EST · UTC−5); 2 hours behind New York from Mar 8, 2026 07:00 UTC to Nov 1, 2026 06:00 UTC (New York on EDT · UTC−4); 1 hour behind New York from Nov 1, 2026 06:00 UTC to Dec 31, 2026 (New York on EST · UTC−5).
- Jan 1, 2026 to Mar 8, 2026 07:00 UTCNew York (EST, UTC−5) → Mexico City (CST, UTC−6)Mexico City is 1 hour behind New York
- Mar 8, 2026 07:00 UTC to Nov 1, 2026 06:00 UTCNew York (EDT, UTC−4) → Mexico City (CST, UTC−6)Mexico City is 2 hours behind New York
- Nov 1, 2026 06:00 UTC to Dec 31, 2026New York (EST, UTC−5) → Mexico City (CST, UTC−6)Mexico City is 1 hour behind New York
9:00 AM EST (UTC−5) in New York is 8:00 AM CST (UTC−6) in Mexico City, the same day. Mexico City is 1 h behind New York.
| Format | Result | Copy |
|---|---|---|
| Mexico CityCST · UTC−6 · Wednesday, January 14, 2026 · the same day | 8: | |
| ISO 8601UTC | 2026- | |
| Unix seconds | 1768399200 | |
| RFC 2822UTC | Wed, |
Conversions use New York (America/New_York) and Mexico City (America/Mexico_City). Other cities reached through search aliases may have different historical rules.
Current time in New York and Mexico City
Hour by hour: New York (EST, UTC−5) → Mexico City (CST, UTC−6)
Both sides are inside 9:00–17:00 from 10:00 AM to 5:00 PM EST (UTC−5) in New York (7 hours).
| New York | Mexico City | Day |
|---|---|---|
| 12:00 AM | 11:00 PM | previous day |
| 1:00 AM | 12:00 AM | same day |
| 2:00 AM | 1:00 AM | same day |
| 3:00 AM | 2:00 AM | same day |
| 4:00 AM | 3:00 AM | same day |
| 5:00 AM | 4:00 AM | same day |
| 6:00 AM | 5:00 AM | same day |
| 7:00 AM | 6:00 AM | same day |
| 8:00 AM | 7:00 AM | same day |
| 9:00 AM | 8:00 AM | same day |
| 10:00 AM | 9:00 AM | same day |
| 11:00 AM | 10:00 AM | same day |
| 12:00 PM | 11:00 AM | same day |
| 1:00 PM | 12:00 PM | same day |
| 2:00 PM | 1:00 PM | same day |
| 3:00 PM | 2:00 PM | same day |
| 4:00 PM | 3:00 PM | same day |
| 5:00 PM | 4:00 PM | same day |
| 6:00 PM | 5:00 PM | same day |
| 7:00 PM | 6:00 PM | same day |
| 8:00 PM | 7:00 PM | same day |
| 9:00 PM | 8:00 PM | same day |
| 10:00 PM | 9:00 PM | same day |
| 11:00 PM | 10:00 PM | same day |
Hour by hour: New York (EDT, UTC−4) → Mexico City (CST, UTC−6)
Both sides are inside 9:00–17:00 from 11:00 AM to 5:00 PM EDT (UTC−4) in New York (6 hours).
| New York | Mexico City | Day |
|---|---|---|
| 12:00 AM | 10:00 PM | previous day |
| 1:00 AM | 11:00 PM | previous day |
| 2:00 AM | 12:00 AM | same day |
| 3:00 AM | 1:00 AM | same day |
| 4:00 AM | 2:00 AM | same day |
| 5:00 AM | 3:00 AM | same day |
| 6:00 AM | 4:00 AM | same day |
| 7:00 AM | 5:00 AM | same day |
| 8:00 AM | 6:00 AM | same day |
| 9:00 AM | 7:00 AM | same day |
| 10:00 AM | 8:00 AM | same day |
| 11:00 AM | 9:00 AM | same day |
| 12:00 PM | 10:00 AM | same day |
| 1:00 PM | 11:00 AM | same day |
| 2:00 PM | 12:00 PM | same day |
| 3:00 PM | 1:00 PM | same day |
| 4:00 PM | 2:00 PM | same day |
| 5:00 PM | 3:00 PM | same day |
| 6:00 PM | 4:00 PM | same day |
| 7:00 PM | 5:00 PM | same day |
| 8:00 PM | 6:00 PM | same day |
| 9:00 PM | 7:00 PM | same day |
| 10:00 PM | 8:00 PM | same day |
| 11:00 PM | 9:00 PM | same day |
Worked examples
| When | New York | Mexico City | ISO 8601 (UTC) | Unix |
|---|---|---|---|---|
| a winter weekday | 9:00 AM EST (UTC−5), January 14, 2026 | 8:00 AM CST (UTC−6), January 14, 2026 | 2026-01-14T14:00:00.000Z | 1768399200 |
| a summer weekday | 10:00 AM EDT (UTC−4), July 15, 2026 | 8:00 AM CST (UTC−6), July 15, 2026 | 2026-07-15T14:00:00.000Z | 1784124000 |
| New Year | 7:00 PM EST (UTC−5), December 31, 2026 | 6:00 PM CST (UTC−6), December 31, 2026 | 2027-01-01T00:00:00.000Z | 1798761600 |
The ISO 8601 and Unix columns are the same instant written without a zone — how APIs and databases should store it. Need this for a whole column? Convert a CSV file.
EST — Eastern Time
- IANA identifier
- America/New_York
- Standard time
- EST · UTC−5
- Daylight time
- EDT · UTC−4
- On this clock today
- New York, Washington DC, Toronto, Miami, Boston, Atlanta, Detroit
Places that share this clock as of 2026-11-13 (tzdata 2026f). Conversions for any date use America/New_York; a listed place's past or future rules may differ.
Offset changes 2026–2027
- Mar 8, 2026, 3:00 AM local (2026-03-08 07:00 UTC): clocks go forward to UTC−4 (EDT)
- Nov 1, 2026, 1:00 AM local (2026-11-01 06:00 UTC): clocks go back to UTC−5 (EST)
- Mar 14, 2027, 3:00 AM local (2027-03-14 07:00 UTC): clocks go forward to UTC−4 (EDT)
- Nov 7, 2027, 1:00 AM local (2027-11-07 06:00 UTC): clocks go back to UTC−5 (EST)
EST here is North American Eastern Standard Time (UTC−5), with EDT (UTC−4) in summer. Australian Eastern Standard Time is on the AEST page.
Mexico City — Central Standard Time (Mexico)
- IANA identifier
- America/Mexico_City
- UTC offset
- CST · UTC−6
- Daylight saving
- Not observed
- On this clock today
- Mexico City, Guadalajara, Monterrey, most of Mexico, Calgary, Edmonton
Places that share this clock as of 2026-11-13 (tzdata 2026f). Conversions for any date use America/Mexico_City; a listed place's past or future rules may differ.
Most of Mexico abolished daylight saving time in October 2022; Mexico City stays on UTC−6 all year. Border municipalities that follow US daylight saving, Baja California and the states on UTC−7 are not on this clock. Alberta (Calgary, Edmonton) has used this UTC−6 clock all year since 1 November 2026; for earlier dates in Alberta use the Mountain Time page.
Related conversions
File workspace
Converting a whole column of timestamps?
The free converter handles one value at a time across 82 formats and 92 zones. The file workspace converts an entire CSV column between any two formats and zones, previews the first rows, and leaves unreadable cells exactly as they were.
Offsets and change dates on this page are computed from IANA time zone database 2026f for 2026–2027; the live tool uses the same data.