Unix (s):1782526290
Unix (ms):1782526290386
ISO 8601:2026-06-27T02:11:30.386Z
live

Unix Timestamp Converter

Paste anything
✓ detected: unix timestamp (seconds)

Standard formats

unix timestamp (seconds)
1765065600
unix timestamp (milliseconds)
1765065600000
iso 8601 (utc)
2025-12-07T00:00:00.000Z
iso 8601 (local, no Z)
2025-12-07T00:00:00
rfc 2822 (email/http)
Sun, 07 Dec 2025 00:00:00 +0000
human readable
Sunday, 7 December 2025, 00:00:00 UTC

Timezones

UTC
07 Dec 2025, 00:00:00
UTC
07 Dec 2025, 00:00:00
—

Platform-specific formats

windows filetime
134095392000000000
apple cocoa time
786758400
excel serial date
45998.00000
ntp timestamp
3974054400
gps timestamp
Week 2396, ToW 0s
.net datetime ticks
639006624000000000
webkit timestamp
13409539200000000
tai timestamp
1765065637
(UTC +37s, as of 2017)
julian date
2461016.50000
modified julian date (mjd)
61016.00000
lilian date
161856
unix day
20429

ABOUT THIS TIMESTAMP

Unix timestamp 1765065600 represents Sunday, 7 December 2025 at 00:00:00 UTC. In milliseconds it is 1765065600000. This moment falls on day 341 of 2025, in week 49. The ISO 8601 representation is 2025-12-07T00:00:00.000Z. The Windows FILETIME equivalent is 134095392000000000. The Apple Cocoa timestamp is 786758400. The Excel serial date is 45998.00000. The NTP timestamp is 3974054400. The Modified Julian Date is 61016.00000. The Unix Day number is 20429.

DAY OF WEEK
Sunday
DAY OF YEAR
341 of 365
WEEK NUMBER
Week 49
UNIX DAY
20429
LEAP YEAR
No
DAYS FROM TODAY
202 days ago
UTC OFFSET FROM NOW
-202 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.