Time Zone Converter: Wall Clock, ISO 8601 and Unix Epoch in One Tool

Most time zone converters assume that you already know which kind of time you are holding. In practice you usually do not. A calendar entry gives you a date and a clock reading, a log line gives you an ISO 8601 string with an offset glued to the end, and a database row gives you a bare integer that counts seconds since 1970. The Time Zone Converter treats those as three separate input modes and resolves each one to a single instant before it shows you anything, which is the only order of operations that keeps a daylight saving transition from silently moving your answer by an hour.

The tool carries its own catalog of 597 selectable zone entries, built from 317 IANA zone groups and 994 main city names in tzdb release 2026f, so the search works without a lookup request. What follows is a working walkthrough of the three modes, the two daylight saving policies that decide ambiguous cases, and the output fields you can copy into a ticket, a query, or a message to a colleague.

What the converter takes in and what it returns

Every conversion starts in the input card. The mode buttons switch between Date & time, ISO 8601, and Unix epoch, and the fields below them change with the mode. Date & time expects a date in YYYY-MM-DD form and a clock reading in HH:MM, with the source zone chosen from the searchable catalog; the first row of that list is the zone your own browser reports, so a local conversion needs no typing. ISO 8601 expects one string and can work with or without an offset. Unix epoch expects an integer and a unit switch for seconds or milliseconds.

The source zone does two different jobs depending on the mode. In Date & time it is the zone the wall clock belongs to. In ISO 8601 it is the fallback for strings that carry no offset, and the display zone for strings that do. In Unix epoch the number already fixes the instant, so the source zone only controls how the result is rendered in the source card.

Below the input card, a verdict line reports whether the local time exists, falls into the spring-forward gap, or occurs twice in the fall-back overlap. The target table repeats the resolved instant in every zone you have added; the defaults are Europe/London, America/New_York, and Asia/Kolkata, and the add list searches the same catalog. For each target you get the local clock, the date, the UTC offset, the abbreviation in force at that instant, the day shift, and the difference from the source zone. A 24-cell strip plots the hours of that day in the first target zone, and the About card prints the tzdb release along with the zone count, so the data version behind an offset is never a mystery.

Converting a wall-clock time across four zones

Take a concrete case. You are in Chișinău on 22 November 2026 and you need to tell a colleague in New York what 09:00 means for them. Choose Date & time, keep the browser zone if it is Europe/Chisinau, type 2026-11-22 and 09:00, and leave the target list at its defaults.

The source card shows 09:00, the weekday Sunday, the offset GMT+02:00, and the abbreviation EET. November is outside the European summer period, since the European Union switched back to standard time on 25 October 2026, so the offset is two hours ahead of UTC rather than three. The resolved instant is 07:00 UTC.

ZoneLocal clockOffsetAbbreviationDifference from source
Europe/Chisinau09:00GMT+02:00EETsame
Europe/London07:00GMT+00:00GMT-2h
America/New_York02:00GMT-05:00EST-7h
Asia/Kolkata12:30GMT+05:30IST+3h 30m

The arithmetic behind the table is simple once the instant is fixed. Each row takes 07:00 UTC and adds the offset that the zone uses at that moment, which is why Kolkata lands on a half hour: its offset is five and a half hours, so 07:00 plus 05:30 gives 12:30. The difference column subtracts the source offset from the target offset, and it is the number you actually quote when you say that a meeting at nine in Chișinău is seven hours earlier in New York.

Two buttons keep repeated work short. Now refills the active mode with the current moment in the selected zone, which is useful when you want to check what time it is somewhere before you propose a slot. Copy on a row puts that row on the clipboard as pipe-separated text, while Copy table produces a tab-separated block that pastes cleanly into a spreadsheet or a ticket comment. The search fields themselves are capped: the source list shows 12 rows before you type and at most 40 matches while typing, and the add list shows 6 and 10 respectively, so the catalog stays quick without pagination.

Reading a timestamp: ISO 8601 and Unix epoch

The ISO 8601 mode exists because APIs and logs rarely hand you a clean wall clock. Paste 2026-07-15T09:00:00+03:00, set the source zone to Europe/Chisinau, and the card resolves it to 06:00 UTC, which is 02:00 in New York on daylight time, 07:00 in London on British summer time, and 11:30 in Kolkata. The epoch value shown next to those fields is 1784095200, and switching the epoch unit to milliseconds gives 1784095200000, the same instant expressed at finer precision.

The offset is what makes the string unambiguous. An ISO timestamp that ends in Z, or in a signed offset such as +03:00 or -05:00, pins the instant by itself, and the source zone is then only a display choice. A string without an offset, such as 2026-07-15T09:00:00, is a local time that could belong to any zone, so the converter reads it as wall time in the source zone and applies that zone's rules. This is the same ambiguity that makes a bare timestamp dangerous in an API payload: the sender and the receiver can disagree about which offset was meant, and the disagreement only shows up twice a year, at the transitions.

The Unix epoch mode inverts the relationship. A number such as 1795330800 is an instant with no zone attached, and the converter renders it through the source zone and every target zone you have added; on 22 November 2026 that number is 09:00 in Chișinău and 02:00 in New York. Choose the unit deliberately, because a seconds value read as milliseconds lands in January 1970 and a milliseconds value read as seconds lands tens of thousands of years in the future. An empty field is reported as Invalid input rather than a zero, which matters because zero is a valid epoch value that means 1970-01-01T00:00:00Z.

Both non-wall modes share one limitation that is worth stating plainly: they resolve a single instant. There is no batch field for a list of dates, no recurrence rule, and no calendar integration. If you have twenty log lines to check, the honest workflow is to paste them one at a time or convert the numeric ones, and the absence of a bulk path is a design decision rather than a missing control that might appear later.

Missing hour and repeated hour: choosing the instant

Daylight saving creates two kinds of local time that a converter cannot resolve on its own, and the tool refuses to hide either of them. The first is the missing hour. In New York on 8 March 2026 the clocks jump from 02:00 to 03:00, so the wall time 02:30 never happens. If you enter that value with America/New_York as the source zone, the verdict line reports the gap and the gap policy decides the outcome. Shift forward adds the size of the gap and lands on 03:30 EDT, which is 07:30 UTC. Shift back subtracts it and lands on 01:30 EST, which is 06:30 UTC. Reject refuses the conversion and reports the gap instead of inventing an instant.

The second is the repeated hour. On 1 November 2026 the clocks in New York move from 02:00 back to 01:00, so every wall time between 01:00 and 02:00 happens twice. Enter 01:30 with the overlap policy set to First occurrence and you get 05:30 UTC on the summer offset, displayed as 01:30 EDT. Set it to Second occurrence and you get 06:30 UTC on the standard offset, displayed as 01:30 EST. Reject shows both candidates, which is the correct answer when the source is a human note that simply says half past one.

Wall time in New YorkPolicyResolved instantLocal clock shown
2026-03-08 02:30Shift forward07:30 UTC03:30 EDT
2026-03-08 02:30Shift back06:30 UTC01:30 EST
2026-11-01 01:30First occurrence05:30 UTC01:30 EDT
2026-11-01 01:30Second occurrence06:30 UTC01:30 EST

The two policies are independent, so a single session can shift forward on a gap and take the second occurrence on an overlap. That combination is not arbitrary: it matches what most scheduling systems do when they must pick something, and it makes the choice explicit instead of leaving it to a library default that changes between languages and versions. A timestamp in ISO 8601 form with an offset avoids both questions entirely, because the offset already identifies one of the two instants; the policies only matter when the input is wall time.

Offsets, abbreviations, day shift and the 24-hour strip

The output card gives you more than a clock reading, and each field answers a different question. The offset label, written as GMT+02:00 or GMT-05:00, is the mathematically useful value: it tells you exactly how far the zone is from UTC at that instant, and it is what you add or subtract when you do the conversion by hand. The abbreviation, such as EET, EST, or IST, is a display string, and it is ambiguous by nature: IST can mean India Standard Time, Irish Standard Time, or Israel Standard Time, and CST can mean Central Standard Time or China Standard Time. The zone identifier, not the abbreviation, is what carries the full rule set, which is why the converter always shows the identifier in the table and in the copied text.

The difference column compares the target zone with the source zone at the same instant, including the half-hour and three-quarter-hour offsets that some zones use. The day shift column tells you whether the target is on the next or previous calendar day: a call at 23:00 in Los Angeles is already 08:00 the next morning in Chișinău, and the +1d marker makes that visible without mental arithmetic. Together with the date row, those fields are what you need to write a meeting note that cannot be misread.

The 24-hour strip is the planning view. It plots every hour of the day in the first target zone, with the abbreviation in force at each hour, so you can see at a glance where the working day overlaps with the source zone and where the date changes. If the first target is New York and the source is Chișinău, the strip shows the New York morning hours that correspond to the Chișinău afternoon, which is the window a same-day call has to fit into. Changing the first target re-plots the strip immediately, and the 12-hour toggle changes every clock on the page without changing any of the underlying instants.

Limits, data version, and the formats you can copy

The catalog is the part of the tool that is easiest to overestimate, so here is the exact scope. The page ships 597 selectable zone entries derived from 317 IANA zone groups, plus 994 main city names from tzdb release 2026f, and the search matches zone names, city names, countries, and abbreviations such as UTC, IST, or +0545. The About card prints that release, which is the first thing to check when an offset disagrees with another converter: a rule change published in a later tzdb release will not appear here until the site is rebuilt.

The output formats cover the usual handoff points. The source card shows the local clock, date, weekday, offset label, abbreviation, ISO 8601 with offset, UTC ISO, HTTP date, SQL datetime, and the epoch value in seconds, with milliseconds on its copy button. Five of those fields carry their own copy button, and the table can be copied whole as tab-separated text or row by row as pipe-separated text, and the share button copies a URL that restores the mode, source zone, date, policies, and target list, so a colleague opens exactly the view you were reading.

The constraints are equally specific. Conversions are limited by the JavaScript Date range, roughly plus or minus 8.64e15 milliseconds around the epoch, and historical offsets come from the bundled tzdb data and the browser's Intl implementation, which can differ in precision for dates far in the past. Nothing is uploaded, stored, or logged: there is no account, no localStorage, and no history, so reloading the page returns to the defaults and the share link is the only way state leaves the tab. The tool does not schedule meetings, send reminders, import calendar files, or convert a list of dates in one pass.

Frequently Asked Questions

Which input mode should I use?

Use Date & time when you are reading a clock or a calendar entry and know its zone. Use ISO 8601 when you copy a timestamp from an API, a log, or a database. Use Unix epoch when a system gives you a number of seconds or milliseconds since 1970-01-01T00:00:00Z.

Why does an ISO timestamp need a source zone?

A string without an offset does not say which zone it was written in. The converter reads it as wall time in the source zone and applies that zone's rules. A string that ends in Z or in a signed offset fixes the instant by itself.

What happens in the missing hour?

Some local times never occur when clocks spring forward. The verdict line reports the gap, and the gap policy shifts the time forward, shifts it back, or rejects the conversion with the size of the gap.

What happens in the repeated hour?

When clocks fall back, a wall time in that hour happens twice. First occurrence takes the earlier instant, Second occurrence takes the later one, and Reject shows both candidates so you can choose deliberately.

How many zones does the search cover?

The catalog holds 597 selectable zone entries from 317 IANA zone groups, plus 994 main city names from tzdb 2026f. Search matches zone names, cities, countries, and abbreviations; the list shows 12 rows before typing and up to 40 matches while typing.

Can I convert several dates at once?

No. One conversion resolves one instant, which is then shown in every zone in your table. Convert a list of dates one at a time, or use epoch values, which are unambiguous by construction.

Is anything uploaded or stored?

No. The catalog ships with the page and the conversion runs in the browser with no network request, no account, no localStorage, and no history. A share link is the only way state leaves the tab.

Why does another converter show a different offset?

Offsets change when a government alters its DST rules, and each site rebuilds its data at a different time. This page uses tzdb 2026f and prints the release in the About card, so a difference can be traced to a data version.

Lazar Ljubenović
Lazar Ljubenović

Niš · SO reputation 19885 · Badges: 10🥇59🥈95🥉 · SO member since 2013