Unix (s):1782526682
Unix (ms):1782526682807
ISO 8601:2026-06-27T02:18:02.807Z
live

Unix Timestamp Converter

Paste anything
✓ detected: unix timestamp (seconds)

Standard formats

unix timestamp (seconds)
2100000000
unix timestamp (milliseconds)
2100000000000
iso 8601 (utc)
2036-07-18T13:20:00.000Z
iso 8601 (local, no Z)
2036-07-18T13:20:00
rfc 2822 (email/http)
Fri, 18 Jul 2036 13:20:00 +0000
human readable
Friday, 18 July 2036, 13:20:00 UTC

Timezones

UTC
18 Jul 2036, 13:20:00
UTC
18 Jul 2036, 13:20:00

Platform-specific formats

windows filetime
137444736000000000
apple cocoa time
1121692800
excel serial date
49874.55556
ntp timestamp
4308988800
gps timestamp
Week 2949, ToW 480000s
.net datetime ticks
642355968000000000
webkit timestamp
13744473600000000
tai timestamp
2100000037
(UTC +37s, as of 2017)
julian date
2464893.05556
modified julian date (mjd)
64892.55556
lilian date
165732
unix day
24305

ABOUT THIS TIMESTAMP

Unix timestamp 2100000000 represents Friday, 18 July 2036 at 13:20:00 UTC. In milliseconds it is 2100000000000. This moment falls on day 200 of 2036, in week 29. The ISO 8601 representation is 2036-07-18T13:20:00.000Z. The Windows FILETIME equivalent is 137444736000000000. The Apple Cocoa timestamp is 1121692800. The Excel serial date is 49874.55556. The NTP timestamp is 4308988800. The Modified Julian Date is 64892.55556. The Unix Day number is 24305.

DAY OF WEEK
Friday
DAY OF YEAR
200 of 366
WEEK NUMBER
Week 29
UNIX DAY
24305
LEAP YEAR
Yes
DAYS FROM TODAY
in 3674 days
UTC OFFSET FROM NOW
+3674 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.