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

Unix Timestamp Converter

Paste anything
✓ detected: unix timestamp (seconds)

Standard formats

unix timestamp (seconds)
1800000000
unix timestamp (milliseconds)
1800000000000
iso 8601 (utc)
2027-01-15T08:00:00.000Z
iso 8601 (local, no Z)
2027-01-15T08:00:00
rfc 2822 (email/http)
Fri, 15 Jan 2027 08:00:00 +0000
human readable
Friday, 15 January 2027, 08:00:00 UTC

Timezones

UTC
15 Jan 2027, 08:00:00
UTC
15 Jan 2027, 08:00:00
—

Platform-specific formats

windows filetime
134444736000000000
apple cocoa time
821692800
excel serial date
46402.33333
ntp timestamp
4008988800
gps timestamp
Week 2453, ToW 460800s
.net datetime ticks
639355968000000000
webkit timestamp
13444473600000000
tai timestamp
1800000037
(UTC +37s, as of 2017)
julian date
2461420.83333
modified julian date (mjd)
61420.33333
lilian date
162260
unix day
20833

ABOUT THIS TIMESTAMP

Unix timestamp 1800000000 represents Friday, 15 January 2027 at 08:00:00 UTC. In milliseconds it is 1800000000000. This moment falls on day 15 of 2027, in week 3. The ISO 8601 representation is 2027-01-15T08:00:00.000Z. The Windows FILETIME equivalent is 134444736000000000. The Apple Cocoa timestamp is 821692800. The Excel serial date is 46402.33333. The NTP timestamp is 4008988800. The Modified Julian Date is 61420.33333. The Unix Day number is 20833.

DAY OF WEEK
Friday
DAY OF YEAR
15 of 365
WEEK NUMBER
Week 3
UNIX DAY
20833
LEAP YEAR
No
DAYS FROM TODAY
in 202 days
UTC OFFSET FROM NOW
+202 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.