How it works
Pick a date and time and the zone it is in, then read it off in every other zone you add. The date matters: a time converted for next month can differ by an hour from today because of daylight-saving changes, and this tool computes each result from the single absolute instant you chose, so it is correct for the actual date, including the two-to-three-week windows each spring and autumn when the US and Europe are briefly an hour closer than usual.
Search any city to change the source or add a target; your own zone is detected and shown first. A +1 or −1 next to a result means that zone is on the next or previous calendar day. Everything runs in your browser using its built-in time-zone database, it works offline and nothing you type is sent anywhere.
Frequently asked questions
How do I convert EST to PST (or any pair)?
Set the source city to one in the Eastern zone (e.g. New York) and add a city in the Pacific zone (e.g. Los Angeles). The Pacific result will read three hours earlier. Because it is date-aware, it stays correct across daylight-saving changes rather than assuming a fixed offset.
Is it correct for future dates?
Yes. Each result is formatted from one absolute instant using the IANA time-zone database, so a meeting booked weeks out is converted using the daylight-saving rules in effect on that date, not today's offset.
Does it handle half-hour zones like India?
Yes: India (+5:30), Nepal (+5:45) and the other fractional-offset zones render at their true offset, which fixed-offset converters get wrong.
Can I share a conversion?
Yes. “Copy link” puts the date, time, source and target zones into the URL, so anyone who opens it sees the same conversion. The state lives in the URL fragment and is never sent to our server.