Unix (s):1782526290
Unix (ms):1782526290204
ISO 8601:2026-06-27T02:11:30.204Z
live

Unix Timestamp Converter

Paste anything
✓ detected: unix timestamp (seconds)

Standard formats

unix timestamp (seconds)
1108339200
unix timestamp (milliseconds)
1108339200000
iso 8601 (utc)
2005-02-14T00:00:00.000Z
iso 8601 (local, no Z)
2005-02-14T00:00:00
rfc 2822 (email/http)
Mon, 14 Feb 2005 00:00:00 +0000
human readable
Monday, 14 February 2005, 00:00:00 UTC

Timezones

UTC
14 Feb 2005, 00:00:00
UTC
14 Feb 2005, 00:00:00
—

Platform-specific formats

windows filetime
127528128000000000
apple cocoa time
130032000
excel serial date
38397.00000
ntp timestamp
3317328000
gps timestamp
Week 1310, ToW 86400s
.net datetime ticks
632439360000000000
webkit timestamp
12752812800000000
tai timestamp
1108339237
(UTC +37s, as of 2017)
julian date
2453415.50000
modified julian date (mjd)
53415.00000
lilian date
154255
unix day
12828

ABOUT THIS TIMESTAMP

Unix timestamp 1108339200 represents Monday, 14 February 2005 at 00:00:00 UTC. In milliseconds it is 1108339200000. This moment falls on day 45 of 2005, in week 7. The ISO 8601 representation is 2005-02-14T00:00:00.000Z. The Windows FILETIME equivalent is 127528128000000000. The Apple Cocoa timestamp is 130032000. The Excel serial date is 38397.00000. The NTP timestamp is 3317328000. The Modified Julian Date is 53415.00000. The Unix Day number is 12828.

DAY OF WEEK
Monday
DAY OF YEAR
45 of 365
WEEK NUMBER
Week 7
UNIX DAY
12828
LEAP YEAR
No
DAYS FROM TODAY
7803 days ago
UTC OFFSET FROM NOW
-7803 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.