Unix (s):1782526264
Unix (ms):1782526264380
ISO 8601:2026-06-27T02:11:04.380Z
live

Unix Timestamp Converter

Paste anything
✓ detected: unix timestamp (seconds)

Standard formats

unix timestamp (seconds)
1736035200
unix timestamp (milliseconds)
1736035200000
iso 8601 (utc)
2025-01-05T00:00:00.000Z
iso 8601 (local, no Z)
2025-01-05T00:00:00
rfc 2822 (email/http)
Sun, 05 Jan 2025 00:00:00 +0000
human readable
Sunday, 5 January 2025, 00:00:00 UTC

Timezones

UTC
05 Jan 2025, 00:00:00
UTC
05 Jan 2025, 00:00:00
—

Platform-specific formats

windows filetime
133805088000000000
apple cocoa time
757728000
excel serial date
45662.00000
ntp timestamp
3945024000
gps timestamp
Week 2348, ToW 0s
.net datetime ticks
638716320000000000
webkit timestamp
13380508800000000
tai timestamp
1736035237
(UTC +37s, as of 2017)
julian date
2460680.50000
modified julian date (mjd)
60680.00000
lilian date
161520
unix day
20093

ABOUT THIS TIMESTAMP

Unix timestamp 1736035200 represents Sunday, 5 January 2025 at 00:00:00 UTC. In milliseconds it is 1736035200000. This moment falls on day 5 of 2025, in week 1. The ISO 8601 representation is 2025-01-05T00:00:00.000Z. The Windows FILETIME equivalent is 133805088000000000. The Apple Cocoa timestamp is 757728000. The Excel serial date is 45662.00000. The NTP timestamp is 3945024000. The Modified Julian Date is 60680.00000. The Unix Day number is 20093.

DAY OF WEEK
Sunday
DAY OF YEAR
5 of 365
WEEK NUMBER
Week 1
UNIX DAY
20093
LEAP YEAR
No
DAYS FROM TODAY
538 days ago
UTC OFFSET FROM NOW
-538 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.