Unix (s):1782526104
Unix (ms):1782526104496
ISO 8601:2026-06-27T02:08:24.496Z
live

Unix Timestamp Converter

Paste anything
✓ detected: unix timestamp (seconds)

Standard formats

unix timestamp (seconds)
2000000000
unix timestamp (milliseconds)
2000000000000
iso 8601 (utc)
2033-05-18T03:33:20.000Z
iso 8601 (local, no Z)
2033-05-18T03:33:20
rfc 2822 (email/http)
Wed, 18 May 2033 03:33:20 +0000
human readable
Wednesday, 18 May 2033, 03:33:20 UTC

Timezones

UTC
18 May 2033, 03:33:20
UTC
18 May 2033, 03:33:20

Platform-specific formats

windows filetime
136444736000000000
apple cocoa time
1021692800
excel serial date
48717.14815
ntp timestamp
4208988800
gps timestamp
Week 2784, ToW 272000s
.net datetime ticks
641355968000000000
webkit timestamp
13644473600000000
tai timestamp
2000000037
(UTC +37s, as of 2017)
julian date
2463735.64815
modified julian date (mjd)
63735.14815
lilian date
164575
unix day
23148

ABOUT THIS TIMESTAMP

Unix timestamp 2000000000 represents Wednesday, 18 May 2033 at 03:33:20 UTC. In milliseconds it is 2000000000000. This moment falls on day 138 of 2033, in week 20. The ISO 8601 representation is 2033-05-18T03:33:20.000Z. The Windows FILETIME equivalent is 136444736000000000. The Apple Cocoa timestamp is 1021692800. The Excel serial date is 48717.14815. The NTP timestamp is 4208988800. The Modified Julian Date is 63735.14815. The Unix Day number is 23148.

DAY OF WEEK
Wednesday
DAY OF YEAR
138 of 365
WEEK NUMBER
Week 20
UNIX DAY
23148
LEAP YEAR
No
DAYS FROM TODAY
in 2517 days
UTC OFFSET FROM NOW
+2517 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.