Unix (s):1782526462
Unix (ms):1782526462805
ISO 8601:2026-06-27T02:14:22.805Z
live

Unix Timestamp Converter

Paste anything
✓ detected: unix timestamp (seconds)

Standard formats

unix timestamp (seconds)
1737417600
unix timestamp (milliseconds)
1737417600000
iso 8601 (utc)
2025-01-21T00:00:00.000Z
iso 8601 (local, no Z)
2025-01-21T00:00:00
rfc 2822 (email/http)
Tue, 21 Jan 2025 00:00:00 +0000
human readable
Tuesday, 21 January 2025, 00:00:00 UTC

Timezones

UTC
21 Jan 2025, 00:00:00
UTC
21 Jan 2025, 00:00:00
—

Platform-specific formats

windows filetime
133818912000000000
apple cocoa time
759110400
excel serial date
45678.00000
ntp timestamp
3946406400
gps timestamp
Week 2350, ToW 172800s
.net datetime ticks
638730144000000000
webkit timestamp
13381891200000000
tai timestamp
1737417637
(UTC +37s, as of 2017)
julian date
2460696.50000
modified julian date (mjd)
60696.00000
lilian date
161536
unix day
20109

ABOUT THIS TIMESTAMP

Unix timestamp 1737417600 represents Tuesday, 21 January 2025 at 00:00:00 UTC. In milliseconds it is 1737417600000. This moment falls on day 21 of 2025, in week 3. The ISO 8601 representation is 2025-01-21T00:00:00.000Z. The Windows FILETIME equivalent is 133818912000000000. The Apple Cocoa timestamp is 759110400. The Excel serial date is 45678.00000. The NTP timestamp is 3946406400. The Modified Julian Date is 60696.00000. The Unix Day number is 20109.

DAY OF WEEK
Tuesday
DAY OF YEAR
21 of 365
WEEK NUMBER
Week 3
UNIX DAY
20109
LEAP YEAR
No
DAYS FROM TODAY
522 days ago
UTC OFFSET FROM NOW
-522 days

Specialist tools

ABOUT TIMESTAMP CONVERSION

What is a Unix timestamp?

A Unix timestamp is the number of seconds elapsed since 1 January 1970 00:00:00 UTC -- a moment known as the Unix epoch. It is the most universal way computers store and transmit time because it is a timezone-agnostic integer that requires no calendar logic to compare or sort. Most programming languages, databases, and APIs use Unix timestamps as their internal time representation.

Why are there so many timestamp formats?

Different systems chose different starting points and different units. Windows measures time in 100-nanosecond intervals since 1 January 1601. Apple's frameworks count seconds since 1 January 2001. GPS counts weeks and seconds since 6 January 1980. Excel counts days since 30 December 1899, with an intentional bug that treats 1900 as a leap year for Lotus 1-2-3 compatibility. Converting between these formats requires knowing the offset between each epoch and the Unix epoch, then accounting for differences in unit scale.

What can unixtime.wtf convert?

Paste any timestamp and get instant conversion to 17 formats: Unix seconds, Unix milliseconds, ISO 8601, RFC 2822, human readable, Windows FILETIME, Apple Cocoa time, Excel serial date, NTP timestamp, GPS timestamp, .NET DateTime ticks, WebKit timestamp, TAI, Julian Day Number, Modified Julian Date, Lilian Date, and Unix Day. The specialist tools handle JWT token decoding, cron expression parsing, relative time expressions, and batch log normalisation. All conversions happen client-side -- nothing is sent to a server.