PlayTools

タイムゾーンとUTCオフセット

18の世界タイムゾーン間で日時を変換します。サマータイムに自動対応。

Runs in your browser — nothing you enter is uploaded

UTC

2026/11/22 12:43

America/New York

2026/11/22 7:43

このタイムゾーン変換ツールの使い方

  1. 日時ピッカーで変換したい日時を選びます。
  2. 「変換元」でその時刻が属するタイムゾーンを選びます。
  3. 「変換先」で目的のゾーンを選びます。
  4. 結果はすぐに表示されます。夏時間は自動反映されます。
  5. 上下を入れ替えれば逆変換できます。

When to convert timezone

Use this timezone converter whenever a clock time in one city has to be understood in another. Remote teams convert timezone before sending a calendar invite so every attendee sees a local start time. Travellers do the same for flight arrivals, hotel check-in, and pharmacy opening hours. Support and engineering teams convert timezone when a log line is stored in UTC but the incident report needs a local wall-clock.

A world clock only shows “now”. A timezone converter also answers “what time is 3:00 PM next Tuesday over there?”, which is the question that actually books a meeting. Enter the date, pick two zones, and read both results — including the date change when the conversion crosses midnight.

If you convert timezone around a daylight-saving transition, do not add a fixed number of hours from memory. Offsets move, and two regions may not change on the same weekend. This page follows IANA rules for the date you typed, which is why the same pair of cities can be four hours apart in winter and five hours apart in summer.

Abbreviations like EST, BST, or IST are easy to mix up — IST is India Standard Time in one context and Irish Standard Time in another. The timezone converter on this page uses IANA identifiers (America/New_York, Europe/London, Asia/Kolkata), so each city maps to one set of rules instead of a three-letter code that several places share. If you only know a UTC offset, pick UTC on one side and the city on the other to convert timezone without guessing the abbreviation.

Open a dedicated timezone converter page for a city pair. Each page shows the current offset, sample meeting times, and daylight-saving notes.

タイムゾーンとUTCオフセット

世界はUTCからのオフセットで区分されます。会議やログの解釈に不可欠です。

夏時間でオフセットが変わる地域があります。Intl APIでIANAデータに基づき補正します。

国際共有では必ずタイムゾーンを明記しましょう。

DST transitions create “missing” or “duplicate” hours once a year. Confirm whether a meeting uses local wall-clock time or a UTC timestamp. Aviation and trading systems often standardize on UTC internally; this timezone converter can show both the local result and the UTC equivalent by setting one side to UTC.

Typical uses: scheduling a call across continents, checking a flight arrival in local time, reading a log timestamp against a colleague’s zone, or converting a webinar start time before you add it to your calendar. Pair this timezone converter with the date-difference calculator when a multi-day span also crosses a DST shift.

The dropdowns cover major business cities plus UTC. For a route you use every week, open one of the city-pair pages linked below — each is a focused timezone converter for that corridor, with the live offset, sample meeting hours, and a reverse link. The hub on this page is the general timezone converter: any date, any pair among the listed zones, DST included.

A common mistake is converting the time but forgetting the calendar date. Crossing the International Date Line, or converting evening hours in the Americas into the next morning in East Asia, changes the day as well as the clock. Read both result cards before you send the invite. If you also need how many days sit between two dates, use the date-difference calculator after you convert timezone.

How to read the result

Type the date and time as it reads on the clock in the “from” zone — the label shows which zone that is — and the converter shows the same moment in the “to” zone, with the date, because converting evening times across the Atlantic or Pacific often lands on a different day. The input always means wall-clock time in the source zone, whatever time zone your own computer is set to.

Times that do not exist or happen twice because of daylight saving are handled predictably: 02:30 on the night New York springs forward is treated as 03:30 on the new offset, and 01:30 on the night it falls back is the first of the two 01:30s.

Worked examples

  • 09:00 in New York on 15 January is 14:00 in London and 23:00 in Tokyo.
  • 09:00 in New York on 15 July is still 14:00 in London — both observe summer time — but 22:00 in Tokyo, which does not.
  • In the weeks between the US and European clock changes (mid-March and late October to early November), New York and London are only 4 hours apart instead of 5.
  • India is UTC+5:30 all year, so its offset to other zones includes half an hour; Nepal is UTC+5:45.

Scheduling across time zones

  • Put the time in every participant’s zone in the invitation, or anchor it to UTC, and name the zones (“10:00 New York / 15:00 London”) rather than writing EST or BST, which are often used incorrectly.
  • Calendar apps store events in UTC and convert for each attendee; a time zone set wrongly on one person’s device is the usual cause of “I joined an hour late”.
  • For recurring meetings, check the weeks around daylight-saving changes, when the gap between regions moves by an hour.

In-depth guides

These free tools pair well with this page — open them in a new tab to finish your workflow.

よくある質問

タイムゾーン変換はどう機能しますか?

時刻を入力し、変換元と変換先のタイムゾーンを選択します。UTCオフセットとサマータイムを考慮して、目的地の時刻を即座に計算します。

サマータイムに対応していますか?

はい。IANAタイムゾーンデータベースを使用して各地域のサマータイムルールを正確に適用するため、年間を通じて正確です。

複数のタイムゾーンを同時に変換できますか?

現在、1つの変換元と1つの変換先タイムゾーン間での変換に対応しています。複数のゾーンを比較するには変換を繰り返してください。

同じUTCオフセットを持つ都市があるのはなぜですか?

経度が近い都市は同じオフセットを持つことが多いですが、サマータイムのルールが異なる場合があります。正確さのために都市名や地域名を使用してください。

過去や将来の日付でも正確ですか?

はい、IANAデータベースにタイムゾーンルールがある限り正確です。1900年以前の歴史的な日付はデータが不完全な場合があります。

オフラインでも使えますか?

はい。変換にはブラウザと OS に組み込まれたタイムゾーンデータベース(IANA tz データベース)を使うため、ページ読み込み後は通信不要です。最新のサマータイム規則を反映するため、ブラウザを最新に保ってください。