Unix (s):1782526190
Unix (ms):1782526190974
ISO 8601:2026-06-27T02:09:50.974Z
live

Unix Timestamp Converter

Paste anything
✓ detected: unix timestamp (seconds)

Standard formats

unix timestamp (seconds)
315964800
unix timestamp (milliseconds)
315964800000
iso 8601 (utc)
1980-01-06T00:00:00.000Z
iso 8601 (local, no Z)
1980-01-06T00:00:00
rfc 2822 (email/http)
Sun, 06 Jan 1980 00:00:00 +0000
human readable
Sunday, 6 January 1980, 00:00:00 UTC

Timezones

UTC
06 Jan 1980, 00:00:00
UTC
06 Jan 1980, 00:00:00
—

Platform-specific formats

windows filetime
119604384000000000
apple cocoa time
-662342400
excel serial date
29226.00000
ntp timestamp
2524953600
gps timestamp
Week 0, ToW 0s
.net datetime ticks
624515616000000000
webkit timestamp
11960438400000000
tai timestamp
315964837
(UTC +37s, as of 2017)
julian date
2444244.50000
modified julian date (mjd)
44244.00000
lilian date
145084
unix day
3657

ABOUT THIS TIMESTAMP

Unix timestamp 315964800 represents Sunday, 6 January 1980 at 00:00:00 UTC. In milliseconds it is 315964800000. This moment falls on day 6 of 1980, in week 1. The ISO 8601 representation is 1980-01-06T00:00:00.000Z. The Windows FILETIME equivalent is 119604384000000000. The Apple Cocoa timestamp is -662342400. The Excel serial date is 29226.00000. The NTP timestamp is 2524953600. The Modified Julian Date is 44244.00000. The Unix Day number is 3657.

DAY OF WEEK
Sunday
DAY OF YEAR
6 of 366
WEEK NUMBER
Week 1
UNIX DAY
3657
LEAP YEAR
Yes
DAYS FROM TODAY
16974 days ago
UTC OFFSET FROM NOW
-16974 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.