Unix (s):1782526301
Unix (ms):1782526301186
ISO 8601:2026-06-27T02:11:41.186Z
live

Unix Timestamp Converter

Paste anything
✓ detected: unix timestamp (seconds)

Standard formats

unix timestamp (seconds)
197164800
unix timestamp (milliseconds)
197164800000
iso 8601 (utc)
1976-04-01T00:00:00.000Z
iso 8601 (local, no Z)
1976-04-01T00:00:00
rfc 2822 (email/http)
Thu, 01 Apr 1976 00:00:00 +0000
human readable
Thursday, 1 April 1976, 00:00:00 UTC

Timezones

UTC
01 Apr 1976, 00:00:00
UTC
01 Apr 1976, 00:00:00

Platform-specific formats

windows filetime
118416384000000000
apple cocoa time
-781142400
excel serial date
27851.00000
ntp timestamp
2406153600
gps timestamp
Week -197, ToW 345600s
.net datetime ticks
623327616000000000
webkit timestamp
11841638400000000
tai timestamp
197164837
(UTC +37s, as of 2017)
julian date
2442869.50000
modified julian date (mjd)
42869.00000
lilian date
143709
unix day
2282

ABOUT THIS TIMESTAMP

Unix timestamp 197164800 represents Thursday, 1 April 1976 at 00:00:00 UTC. In milliseconds it is 197164800000. This moment falls on day 92 of 1976, in week 14. The ISO 8601 representation is 1976-04-01T00:00:00.000Z. The Windows FILETIME equivalent is 118416384000000000. The Apple Cocoa timestamp is -781142400. The Excel serial date is 27851.00000. The NTP timestamp is 2406153600. The Modified Julian Date is 42869.00000. The Unix Day number is 2282.

DAY OF WEEK
Thursday
DAY OF YEAR
92 of 366
WEEK NUMBER
Week 14
UNIX DAY
2282
LEAP YEAR
Yes
DAYS FROM TODAY
18349 days ago
UTC OFFSET FROM NOW
-18349 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.