Unix (s):1782526302
Unix (ms):1782526302012
ISO 8601:2026-06-27T02:11:42.012Z
live

Unix Timestamp Converter

Paste anything
✓ detected: unix timestamp (seconds)

Standard formats

unix timestamp (seconds)
946684800
unix timestamp (milliseconds)
946684800000
iso 8601 (utc)
2000-01-01T00:00:00.000Z
iso 8601 (local, no Z)
2000-01-01T00:00:00
rfc 2822 (email/http)
Sat, 01 Jan 2000 00:00:00 +0000
human readable
Saturday, 1 January 2000, 00:00:00 UTC

Timezones

UTC
01 Jan 2000, 00:00:00
UTC
01 Jan 2000, 00:00:00
—

Platform-specific formats

windows filetime
125911584000000000
apple cocoa time
-31622400
excel serial date
36526.00000
ntp timestamp
3155673600
gps timestamp
Week 1042, ToW 518400s
.net datetime ticks
630822816000000000
webkit timestamp
12591158400000000
tai timestamp
946684837
(UTC +37s, as of 2017)
julian date
2451544.50000
modified julian date (mjd)
51544.00000
lilian date
152384
unix day
10957

ABOUT THIS TIMESTAMP

Unix timestamp 946684800 represents Saturday, 1 January 2000 at 00:00:00 UTC. In milliseconds it is 946684800000. This moment falls on day 1 of 2000, in week 1. The ISO 8601 representation is 2000-01-01T00:00:00.000Z. The Windows FILETIME equivalent is 125911584000000000. The Apple Cocoa timestamp is -31622400. The Excel serial date is 36526.00000. The NTP timestamp is 3155673600. The Modified Julian Date is 51544.00000. The Unix Day number is 10957.

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