One tool for every time conversion: convert across time zones (DST-aware), turn Unix timestamps into dates, switch between time units, and measure durations. Free, no signup, and everything runs in your browser.
What makes it different
Other sites do one thing. This does time zones, timestamps, units, and durations — all in one place.
Uses your browser's official IANA time zone data, so summer-time shifts are always correct — even for future dates.
no off-by-one-hour bugsConvert epoch to date and back, in seconds or milliseconds — the developer feature most time sites skip.
epoch ⇄ dateYour local time, UTC, and the current Unix timestamp update every second at the top of the page.
always currentAdd as many cities as you like and see one moment in all of them at once — ideal for scheduling.
unlimited zonesConvert seconds to hours to days, or measure the exact gap between two dates and times.
4 tools in 1No signup, no ads, nothing sent to a server. Every calculation happens locally in your browser.
100% client-sideQuick guide
It's instant — no button to press.
Pick a date, time, and the zone it's in — or hit "Set to now."
Add any cities you want. Each shows the converted local time instantly.
Every zone updates live and is adjusted for Daylight Saving automatically.
Copy any time with one click for your message, invite, or calendar.
A Unix timestamp — also called epoch time or POSIX time — is the number of seconds that have elapsed since 1 January 1970, 00:00:00 UTC, a moment known as the Unix epoch. Because it's a single number with no time zone attached, it's the cleanest way for computers, databases, and APIs to store an exact moment in time.
For example, the timestamp 1750000000 represents a specific second in June 2025. Convert it in the Unix Timestamp tab above and you'll see it rendered in UTC, your local time, and ISO 8601 format.
Traditional Unix timestamps are measured in seconds and are 10 digits long today. However, JavaScript's Date.now() and many web APIs use milliseconds (13 digits). Mixing the two is a common bug — a millisecond value read as seconds lands you thousands of years in the future. This tool lets you switch between both so you never misread one for the other.
Time zone abbreviations are everywhere — in emails, calendar invites, and meeting requests — but they're easy to mix up, especially because many shift by an hour during Daylight Saving Time. Here's a quick reference for the most common ones:
| Abbr. | Zone | UTC offset | Region |
|---|---|---|---|
| UTC | Coordinated Universal Time | +00:00 | Global standard |
| GMT | Greenwich Mean Time | +00:00 | UK (winter) |
| EST / EDT | Eastern Time | −05:00 / −04:00 | US East Coast |
| PST / PDT | Pacific Time | −08:00 / −07:00 | US West Coast |
| CET / CEST | Central European Time | +01:00 / +02:00 | Europe |
| IST | India Standard Time | +05:30 | India |
| JST | Japan Standard Time | +09:00 | Japan |
| AEST / AEDT | Australian Eastern Time | +10:00 / +11:00 | Australia |
Notice how zones with a "/" have two values — the first is standard (winter) time, the second is Daylight Saving (summer) time. This is exactly why converting by hand is error-prone, and why this tool calculates the correct offset for the specific date you choose.
FAQ
Everything about time zones, Unix timestamps, DST, and units — in plain language.
Ask a question1 Jan 1970 00:00:00 UTC (the Unix epoch) — a simple, time-zone-free way for computers to store a moment in time.