Unix (s):1782526557
Unix (ms):1782526557801
ISO 8601:2026-06-27T02:15:57.801Z
live

Unix Timestamp Converter

Paste anything
✓ detected: unix timestamp (seconds)

Standard formats

unix timestamp (seconds)
1790812800
unix timestamp (milliseconds)
1790812800000
iso 8601 (utc)
2026-10-01T00:00:00.000Z
iso 8601 (local, no Z)
2026-10-01T00:00:00
rfc 2822 (email/http)
Thu, 01 Oct 2026 00:00:00 +0000
human readable
Thursday, 1 October 2026, 00:00:00 UTC

Timezones

UTC
01 Oct 2026, 00:00:00
UTC
01 Oct 2026, 00:00:00
—

Platform-specific formats

windows filetime
134352864000000000
apple cocoa time
812505600
excel serial date
46296.00000
ntp timestamp
3999801600
gps timestamp
Week 2438, ToW 345600s
.net datetime ticks
639264096000000000
webkit timestamp
13435286400000000
tai timestamp
1790812837
(UTC +37s, as of 2017)
julian date
2461314.50000
modified julian date (mjd)
61314.00000
lilian date
162154
unix day
20727

ABOUT THIS TIMESTAMP

Unix timestamp 1790812800 represents Thursday, 1 October 2026 at 00:00:00 UTC. In milliseconds it is 1790812800000. This moment falls on day 274 of 2026, in week 40. The ISO 8601 representation is 2026-10-01T00:00:00.000Z. The Windows FILETIME equivalent is 134352864000000000. The Apple Cocoa timestamp is 812505600. The Excel serial date is 46296.00000. The NTP timestamp is 3999801600. The Modified Julian Date is 61314.00000. The Unix Day number is 20727.

DAY OF WEEK
Thursday
DAY OF YEAR
274 of 365
WEEK NUMBER
Week 40
UNIX DAY
20727
LEAP YEAR
No
DAYS FROM TODAY
in 96 days
UTC OFFSET FROM NOW
+96 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.