The model, stated exactly
The converter takes the New York wall time you enter, resolves it to a single UTC instant using real zone data (Intl, time zone America/New_York — never a hardcoded offset), then reads that same instant in UTC, London (Europe/London), Chicago (America/Chicago), Denver (America/Denver), Los Angeles (America/Los_Angeles), Tokyo (Asia/Tokyo), and your own local zone as reported by your browser. The abbreviation shown — EST or EDT for New York, BST or GMT for London — is the one in force on the date you entered. Your local zone is read from your device, so the same page shows different local results for visitors in different zones, which is the point.
The worked example, line by line
Setup: 12:00 in New York on 2026-10-24, a daylight-time date.
Line 1 — New York. 12:00 EDT (UTC-4), because October 24 falls between March 8 and November 1, 2026.
Line 2 — UTC. 12:00 + 4 hours = 16:00 UTC on 2026-10-24.
Line 3 — London. London is on BST (UTC+1) in late October, so 16:00 UTC = 17:00 BST on 2026-10-24.
Line 4 — US zones. 11:00 CDT Chicago, 10:00 MDT Denver, 09:00 PDT Los Angeles, all on 2026-10-24.
Line 5 — Tokyo. Tokyo is UTC+9 all year, so 16:00 UTC = 01:00 JST on 2026-10-25 — the date rolls forward.
Try these
Winter: 12:00 New York time on January 15, 2027. That is 12:00 EST (UTC-5), 17:00 UTC, 17:00 GMT in London, 11:00 CST in Chicago, 10:00 MST in Denver, 09:00 PST in Los Angeles, and 02:00 JST on January 16 in Tokyo. Note that London and New York are both on standard time, so noon in New York is 5:00 p.m. in London in both seasons — the gap that never changes is New York to London, five hours.
The changeover weekends in 2026. On March 8, 2026, New York springs forward: 2:00 a.m. EST becomes 3:00 a.m. EDT, and noon that day is already EDT (16:00 UTC). On November 1, 2026, New York falls back: 2:00 a.m. EDT becomes 1:00 a.m. EST, and noon that day is EST (17:00 UTC). Times between 2:00 and 3:00 a.m. on March 8 do not exist in New York, and times between 1:00 and 2:00 a.m. on November 1 happen twice — the converter resolves the wall time as entered and the date, not the hour, decides the abbreviation.
Noon in New York, everywhere
| Noon in New York | UTC | London | Chicago | Denver | Los Angeles | Tokyo |
| Summer (EDT, e.g. 2026-10-24) | 16:00 | 17:00 BST | 11:00 CDT | 10:00 MDT | 09:00 PDT | 01:00 JST next day |
| Winter (EST, e.g. 2027-01-15) | 17:00 | 17:00 GMT | 11:00 CST | 10:00 MST | 09:00 PST | 02:00 JST next day |
| Reverse: noon in London | 11:00 UTC (BST) / 12:00 UTC (GMT) | 12:00 | 06:00 CDT / CST | 05:00 MDT / MST | 04:00 PDT / PST | 20:00 / 21:00 JST |
The reverse row is worth memorizing: noon in London is 7:00 a.m. in New York in both seasons, because London and New York change their clocks in the same direction — London springs forward on March 29, 2026 and falls back on October 25, 2026, so for the few weeks when one side has changed and the other has not, the gap is four hours, not five.
Output · formula · meaning
| Output | Formula | What it means |
| New York | Wall time resolved via America/New_York | 12:00 EDT (2026-10-24) at the defaults — EDT, not EST, because October is daylight time. |
| UTC | Same instant in UTC | 16:00 UTC (2026-10-24) at the defaults — the single instant every zone shares. |
| London | Same instant in Europe/London | 17:00 BST (2026-10-24) at the defaults — five hours ahead of New York. |
| Chicago / Denver / Los Angeles | Same instant in America/Chicago, Denver, Los Angeles | 11:00 CDT / 10:00 MDT / 09:00 PDT (2026-10-24) at the defaults. |
| Tokyo | Same instant in Asia/Tokyo | 01:00 JST (2026-10-25) at the defaults — note the date shift forward. |
| Your local time | Same instant in your browser's zone | Shown in the calculator result — it follows your device, so it differs by visitor by design. |
Who uses this
- The manager scheduling a New York call: enters noon New York time and sees 5:00 p.m. in London and 9:00 a.m. in Los Angeles, so the meeting fits both coasts and London.
- The traveler landing at JFK: enters the arrival time in New York and reads what time it is back home before messaging family.
- The student joining a New York class remotely: enters the class time and gets the exact local time, including the March and November clock changes.
- The team publishing on a New York deadline: enters the deadline in New York time and confirms the London and Tokyo publish times before announcing anything.
Accuracy & limitations
The conversion is exact for the date and time you enter, because every zone is read from real zone data rather than a fixed offset. It cannot predict a government's future zone change: if the US or the UK changed its daylight-saving rules, times after that change would follow the new rules once zone data is updated. The converter covers UTC, London, the four mainland US zones, Tokyo, and your local zone; it does not cover Alaska, Hawaii, or US territories as named outputs, though your local zone covers them if that is where your device is set. All times are shown in 24-hour format; 17:00 is 5:00 p.m. and 01:00 is 1:00 a.m. Error policy: missing, malformed, or nonexistent dates and times are reported as errors rather than converted.
Cite this calculatorBright Side Kit. “New York Time Converter: EST & EDT.” brightoolbox.com, 2026.Bright Side Kit. "New York Time Converter: EST & EDT." https://brightoolbox.com/new-york-time-converter/ Accessed October 24, 2026.
Embed this calculatorPaste this into any web page to embed the live calculator. The “Powered by Bright Side Kit” link below it must stay intact.