What this UTC converter does
UTC — Coordinated Universal Time — is the single reference clock the whole world is measured against, and it never changes. This tool converts between UTC and any time zone: enter a date and time, pick a zone, and it returns the converted time along with the developer-friendly forms you often need next — the ISO 8601 timestamp (like 2026-08-28T14:00:00Z) and the Unix time. A live clock shows the current UTC time as you work.
It asks for a date, not just a time, because a zone's distance from UTC can change with the season — daylight saving moves local clocks while UTC stays put. The converter reads the exact offset for the date you choose from your browser's time-zone data, so a conversion around a daylight-saving change is still right.
How to use it
Four steps — your own zone is picked for you, so often you only set the time.
- Pick the date and time.Choose the day and enter the time to convert. The date decides which offset applies.
- Choose the time zone.Select the zone on the other side. It defaults to your device's own zone.
- Set the direction.Use Swap to switch between "UTC to your zone" and "your zone to UTC".
- Read and reuse the result.Take the converted time, the ISO 8601 timestamp, or the Unix value. Copy, print, or download as a CSV.
How UTC conversion works
Every time zone is defined by its offset from UTC. A place five hours ahead is UTC+05:00; five hours behind is UTC−05:00. To convert, you subtract the offset going to UTC and add it coming back:
- Local → UTC: subtract the offset. 18:00 at UTC+05:00 is 13:00 UTC.
- UTC → local: add the offset. 09:00 UTC in a UTC−04:00 zone is 05:00.
UTC itself never observes daylight saving — it is the fixed anchor. What shifts is a place's offset: when a region springs forward, it moves an hour further from UTC for the summer. This converter takes a date and applies the offset that truly holds then, rather than a single fixed number.
18:00 − 5:30 = 12:30 UTC
As a timestamp:
...T12:30:00ZA zone behind UTC works the other way: 09:00 at UTC−04:00 = 13:00 UTC
UTC and GMT give the same clock time in practice; if you prefer that framing, the GMT converter is the sibling tool. To turn the ISO or Unix output back into a readable time, the ISO 8601 converter and Unix timestamp converter handle those directly.
Quick examples
Local times converted to UTC. Offsets shown are the ones applying in each example.
| Local time | Zone (offset) | In UTC |
|---|---|---|
| 18:00 | Karachi (UTC+5) | 13:00 |
| 12:00 | New Delhi (UTC+5:30) | 06:30 |
| 09:00 | New York, winter (UTC−5) | 14:00 |
| 10:00 | Berlin, summer (UTC+2) | 08:00 |
| 02:00 | Tokyo (UTC+9) | 17:00 previous day |
Meeting several zones at once? The meeting planner lines them all up against a shared time, and the time zone abbreviations chart decodes any code you were sent.
Who uses it, and when
- Developers & sysadmins normalising log times, API timestamps, and cron schedules to UTC — and grabbing the ISO 8601 or Unix form on the spot.
- Remote teams agreeing on a shared UTC time so no one has to trust an abbreviation.
- Aviation, shipping & science, where UTC (as Zulu time) is the working standard.
- Gamers & event-goers decoding a launch, raid, or stream time posted in UTC.
If a colleague quotes the result in 24-hour form, the 24-hour clock chart maps it to 12-hour, and the time zone tools hub holds the rest of the set.
Frequently asked questions
What is the difference between UTC and GMT?
For everyday conversions they are the same — both sit at an offset of zero and give the same clock time. The difference is technical: UTC (Coordinated Universal Time) is the modern standard kept by atomic clocks, while GMT (Greenwich Mean Time) is the older astronomical time at the Greenwich meridian. Computing, aviation, and science use UTC as the reference.
What does the Z mean in a UTC timestamp?
The Z, spoken "Zulu", marks a time as UTC — zero offset. So 2026-08-28T14:00:00Z means 14:00 UTC. It is part of the ISO 8601 format and tells any system reading the timestamp that no time-zone offset needs to be applied.
Does UTC change for daylight saving time?
No. UTC never shifts — it is the fixed reference the world's zones are measured against. Daylight saving moves local clocks, which changes a place's offset from UTC for part of the year, but UTC itself stays constant. That is exactly why systems store times in UTC.
What is the ISO 8601 timestamp the tool shows?
ISO 8601 is the international standard for writing dates and times. The tool shows the moment in the form YYYY-MM-DDThh:mm:ssZ — for example 2026-08-28T14:00:00Z — which is unambiguous and sorts correctly as text, so it is the format most databases and APIs use.
What is the Unix time shown here?
Unix time is the number of seconds that have elapsed since 1 January 1970 at 00:00:00 UTC, not counting leap seconds. It is a single integer that represents an exact instant, widely used in programming and logs. The tool shows the Unix time for the moment you enter.
How do I convert my local time to UTC?
Subtract your offset. If you are at UTC+05:00 and your clock reads 18:00, then UTC is 18:00 − 5 hours = 13:00. For a zone behind UTC you add: 09:00 at UTC−04:00 is 13:00 UTC. Set the direction to your-zone-to-UTC and the converter does it for you, including daylight saving.
Is my data private?
Yes. The conversion runs entirely in your browser using its built-in time-zone data. Nothing you enter is uploaded or stored on a server.
Accuracy & sources
The converter builds a real point in time from your inputs and reads it as UTC and in the chosen zone — so it adds or subtracts the offset for you and rolls the date correctly across midnight. The ISO 8601 timestamp and Unix time are derived from that same instant. Every worked example on this page was checked by hand, and the conversion logic was tested against known winter and summer offsets, half-hour zones, and day-boundary cases.
Zone offsets and daylight-saving rules come from your browser's copy of the IANA Time Zone Database, the authoritative source operating systems use worldwide, and the timestamp follows ISO 8601. Written and reviewed by Fletcher Langley, and re-checked whenever the tool changes — last reviewed August 2026.
