TimezoneCalculator

Batch date-time converter

One value per line. Each row gets a result or a specific reason it could not be converted.

Accepted: ISO 8601 local (2024-11-03 01:30), with offset (2024-11-03T05:30Z, …+05:30), with a zone (…[Europe/Paris]), 12-hour with AM/PM, or @epoch. Lines starting with # are ignored. Up to 20,000 lines; runs in a background worker.

0 converted, 0 with notes, 0 need attention

LineInputUTCAsia/KolkataResult

Nothing is guessed silently

Is 03/04/2026 the 3rd of April or the 4th of March? It depends on who wrote it, so slash dates are rejected until you declare the order. 12-hour times need AM or PM. A value like 2024-07-01T09:00-05:00[America/New_York] contradicts itself (New York is UTC−04:00 in July), so you choose whether the offset or the zone wins, or reject such rows.

Bare numbers are refused; prefix epoch values with @ so the unit setting applies explicitly. Date-only values are reported but not converted, because a date is not a moment in time.

Questions

Is there a row limit?

20,000 lines per run. Conversion runs in a background worker so the page stays responsive.

What does the CSV include?

Every row with its status, UTC instant, converted local time and offset, the message, the policies you chose and the rule source.