Timezone Converter
Convert local times with explicit handling of repeated clock times
Set the date-time plus source and target timezones first to convert it; advanced timezone troubleshooting is available in Advanced mode.
The full guide also includes pitfalls, worked examples, snippets, FAQs, and related tools for checking results or troubleshooting.
About this tool
Enter a real Gregorian local date-time and source/target timezone names supported by your browser, such as America/New_York and Asia/Shanghai. The converter checks which instants map back to the requested source clock time. A missing time during a forward clock change is rejected. A repeated time during a rollback is rejected by default; select the earlier or later instant to resolve it. Results show source and target clock times, UTC/ISO, exact UTC offsets, offset difference and optional Unix fields. Quarter-hour offsets are preserved as hours and minutes. Timezone rules come from the browser’s Intl database, whose version can differ between devices; this is a practical preview, not a guarantee for every historical timezone change or legal deadline. Input years are 0001–9999. Date-times and settings are saved in local browser storage; Clear removes that draft.
Suggested Workflow
Scenario Recipes
Resolve a New York rollback
Goal: Keep the two 01:30 instants distinct.
- Enter 2026-11-01T01:30 with source America/New_York and target UTC.
- Convert with Reject selected to see the ambiguity.
- Select Earlier, then Later, and compare ISO results.
Result: Earlier is 2026-11-01T05:30:00.000Z; later is 2026-11-01T06:30:00.000Z.
Check a quarter-hour offset
Goal: Avoid a rounded decimal-hour handoff.
- Enter 2026-01-01T12:00, source UTC, target Asia/Kathmandu.
- Convert and inspect the target time and offset difference.
Result: The target is 17:45 and the difference is +05:45.
Failure Clinic (Common Pitfalls)
An invalid date is not a DST adjustment
Cause: February 30 never exists in the Gregorian calendar.
Fix: Correct the calendar date; the tool will not roll it into March.
Timezone abbreviations are not unique identifiers
Cause: Abbreviations such as CST can refer to different regions.
Fix: Use region names supported by the browser and check the displayed UTC offset.
Production Snippets
Worked example
text
New York 2026-03-08 02:30 → no candidate
New York 2026-11-01 01:30 → 05:30Z / 06:30ZFrequently Asked Questions
What happens to a nonexistent local time?
It is rejected with no conversion result. For example, New York 2026-03-08 02:30 does not occur because clocks jump from 01:59 to 03:00.
How do I resolve a repeated local time?
Choose earlier or later. New York 2026-11-01 01:30 maps to 05:30Z or 06:30Z. The default rejects the ambiguity rather than choosing silently.
Are quarter-hour offsets rounded?
No. UTC to Asia/Kathmandu shows +05:45. Source/target UTC offsets and their difference are displayed in hours, minutes and seconds when needed.
Where do timezone rules come from?
The current browser’s Intl timezone database. Supported names and historical or future rules can vary by browser version; verify important schedules against the system that will execute them.
Are dates and settings stored?
They are processed locally and saved as a browser-local draft. Clear removes the saved draft and visible results.
Keep browsing