Unix (s):1782526547
Unix (ms):1782526547057
ISO 8601:2026-06-27T02:15:47.057Z
live

Unix Timestamp Converter

Paste anything
✓ detected: unix timestamp (seconds)

Standard formats

unix timestamp (seconds)
1796083200
unix timestamp (milliseconds)
1796083200000
iso 8601 (utc)
2026-12-01T00:00:00.000Z
iso 8601 (local, no Z)
2026-12-01T00:00:00
rfc 2822 (email/http)
Tue, 01 Dec 2026 00:00:00 +0000
human readable
Tuesday, 1 December 2026, 00:00:00 UTC

Timezones

UTC
01 Dec 2026, 00:00:00
UTC
01 Dec 2026, 00:00:00
—

Platform-specific formats

windows filetime
134405568000000000
apple cocoa time
817776000
excel serial date
46357.00000
ntp timestamp
4005072000
gps timestamp
Week 2447, ToW 172800s
.net datetime ticks
639316800000000000
webkit timestamp
13440556800000000
tai timestamp
1796083237
(UTC +37s, as of 2017)
julian date
2461375.50000
modified julian date (mjd)
61375.00000
lilian date
162215
unix day
20788

ABOUT THIS TIMESTAMP

Unix timestamp 1796083200 represents Tuesday, 1 December 2026 at 00:00:00 UTC. In milliseconds it is 1796083200000. This moment falls on day 335 of 2026, in week 48. The ISO 8601 representation is 2026-12-01T00:00:00.000Z. The Windows FILETIME equivalent is 134405568000000000. The Apple Cocoa timestamp is 817776000. The Excel serial date is 46357.00000. The NTP timestamp is 4005072000. The Modified Julian Date is 61375.00000. The Unix Day number is 20788.

DAY OF WEEK
Tuesday
DAY OF YEAR
335 of 365
WEEK NUMBER
Week 48
UNIX DAY
20788
LEAP YEAR
No
DAYS FROM TODAY
in 157 days
UTC OFFSET FROM NOW
+157 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.