DevToolsForYou
Private by defaultRuns in your browser

Timezone converter

Pick a date, time, and source timezone to instantly see the equivalent time in any other timezone — DST handled automatically.

UTC+00:00
UTCUTC+00:00
Mon, 24 Aug 2026, 16:30
America/New_YorkUTC-04:00 · DST
Mon, 24 Aug 2026, 08:30
Europe/LondonUTC+01:00 · DST
Mon, 24 Aug 2026, 18:30
Asia/TokyoUTC+09:00
Tue, 25 Aug 2026, 10:30
Popular time zone conversionsQuick access
New York time conversionsAll Eastern Time pairs
London time conversionsAll Greenwich Mean Time pairs
Mumbai / Kolkata time conversionsAll India Standard Time pairs
Los Angeles time conversionsAll Pacific Time pairs
Tokyo time conversionsAll Japan Standard Time pairs
Dubai time conversionsAll Gulf Standard Time pairs
Singapore time conversionsAll Singapore Time pairs
Sydney time conversionsAll Australian Eastern Time pairs
Timezone Converter

About this tool

Time zones are a political construct, not a geographic one, and that is what makes them hard. Offsets change when governments decide they change, sometimes with weeks of notice — Egypt reinstated daylight saving in 2023, Mexico abolished most of it in 2022, and Lebanon moved its clocks with two days' warning. This is why correct conversion depends on the IANA time zone database rather than on a fixed offset. An offset like UTC+5:30 describes a moment; a zone like Asia/Kolkata describes a rule that produces the right offset for any moment, past or future. The distinction matters most around daylight saving transitions, where the same wall-clock time can occur twice or not at all: in the spring, 2:30am simply does not exist in New York, and in the autumn it happens twice, an hour apart. This converter uses the browser's built-in Intl API with full IANA support, so historical dates and DST transitions resolve correctly for the date you pick rather than for today. Conversion runs locally.

No signup requiredRuns in your browserInstant results
How to use
  1. 1

    Select the source time zone from the first dropdown.

  2. 2

    Select the target time zone from the second dropdown.

  3. 3

    Enter the time you want to convert — the result updates instantly.

  4. 4

    Use the current time button to convert right now.

Why use this tool?
  • →

    Schedule meetings across timezones without manually accounting for daylight saving offsets.

  • →

    Convert UTC timestamps from logs or APIs into local readable time for your region.

  • →

    Check what time it is in another country right now or at a specific date.

ExamplesInput → output

New York to London

Input9:00 AM EST (New York)
Output2:00 PM GMT (London)

Mumbai to San Francisco

Input6:30 PM IST (Mumbai)
Output5:00 AM PST (San Francisco)

UTC to Tokyo

Input12:00 PM UTC
Output9:00 PM JST (Tokyo)
Common errorsAnd how to fix them

The converted time is an hour off

Cause: Daylight saving. Either the date you converted falls on the other side of a transition from the one you had in mind, or the two zones change clocks on different dates — the US and the EU shift on different weekends, so the gap between New York and London is four hours for two weeks each year rather than five.

Fix: Check the specific date, not just the time. When scheduling recurring meetings across regions, expect the local time to drift by an hour twice a year unless you anchor the series to one zone.

A time that should exist gives an unexpected result

Cause: The wall-clock time falls in a daylight saving gap. When clocks spring forward, an hour of local time is skipped entirely, and there is no correct conversion for a time inside it.

Fix: Pick a time outside the transition hour. If you are storing user-entered times in code, store the UTC instant alongside the zone so the ambiguity is resolved once, at entry, rather than on every read.

Abbreviations like IST or CST give the wrong zone

Cause: Abbreviations are ambiguous. IST is Indian, Irish, and Israel Standard Time; CST is North American Central, Cuba, and China Standard Time — six hours apart or more.

Fix: Always use the IANA identifier — Asia/Kolkata, America/Chicago — in configuration, APIs, and calendar invites. Reserve abbreviations for display to humans who share your context.

Frequently asked questionsCommon questions answered

These answers explain common timezone converter tasks, expected input formats, and edge cases so both visitors and search engines can understand what this tool does.

How does daylight saving time work in this tool?

This tool uses the browser's built-in Intl API with full IANA timezone support. DST offsets are applied automatically based on the selected date, so you always get the correct local time regardless of the time of year.

What timezone format is used?

Timezones are identified using IANA timezone names such as America/New_York, Europe/London, and Asia/Kolkata. These are the standard identifiers used across operating systems and programming languages.

Can I convert the current time?

Yes. The tool defaults to the current date and time in your local timezone. You can adjust the date and time fields to convert any specific moment.

How do I convert UTC to IST or any other timezone?

Select UTC (Etc/UTC) as the source timezone and Asia/Kolkata as the target to convert to IST. The same approach works for any pair — pick the source timezone on the left and the destination on the right, then set the date and time.

Does the tool account for daylight saving time automatically?

Yes. Timezone offsets that observe daylight saving time (such as America/New_York or Europe/London) automatically reflect the correct offset for the selected date, since DST rules differ by country and change on different dates each year.