Unix (s):1782526335
Unix (ms):1782526335315
ISO 8601:2026-06-27T02:12:15.315Z
live

Unix Timestamp Converter

Paste anything
✓ detected: unix timestamp (seconds)

Standard formats

unix timestamp (seconds)
681436800
unix timestamp (milliseconds)
681436800000
iso 8601 (utc)
1991-08-06T00:00:00.000Z
iso 8601 (local, no Z)
1991-08-06T00:00:00
rfc 2822 (email/http)
Tue, 06 Aug 1991 00:00:00 +0000
human readable
Tuesday, 6 August 1991, 00:00:00 UTC

Timezones

UTC
06 Aug 1991, 00:00:00
UTC
06 Aug 1991, 00:00:00
—

Platform-specific formats

windows filetime
123259104000000000
apple cocoa time
-296870400
excel serial date
33456.00000
ntp timestamp
2890425600
gps timestamp
Week 604, ToW 172800s
.net datetime ticks
628170336000000000
webkit timestamp
12325910400000000
tai timestamp
681436837
(UTC +37s, as of 2017)
julian date
2448474.50000
modified julian date (mjd)
48474.00000
lilian date
149314
unix day
7887

ABOUT THIS TIMESTAMP

Unix timestamp 681436800 represents Tuesday, 6 August 1991 at 00:00:00 UTC. In milliseconds it is 681436800000. This moment falls on day 218 of 1991, in week 32. The ISO 8601 representation is 1991-08-06T00:00:00.000Z. The Windows FILETIME equivalent is 123259104000000000. The Apple Cocoa timestamp is -296870400. The Excel serial date is 33456.00000. The NTP timestamp is 2890425600. The Modified Julian Date is 48474.00000. The Unix Day number is 7887.

DAY OF WEEK
Tuesday
DAY OF YEAR
218 of 365
WEEK NUMBER
Week 32
UNIX DAY
7887
LEAP YEAR
No
DAYS FROM TODAY
12744 days ago
UTC OFFSET FROM NOW
-12744 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.