Unix (s):1782526189
Unix (ms):1782526189768
ISO 8601:2026-06-27T02:09:49.768Z
live

Unix Timestamp Converter

Paste anything
✓ detected: unix timestamp (seconds)

Standard formats

unix timestamp (seconds)
1707091200
unix timestamp (milliseconds)
1707091200000
iso 8601 (utc)
2024-02-05T00:00:00.000Z
iso 8601 (local, no Z)
2024-02-05T00:00:00
rfc 2822 (email/http)
Mon, 05 Feb 2024 00:00:00 +0000
human readable
Monday, 5 February 2024, 00:00:00 UTC

Timezones

UTC
05 Feb 2024, 00:00:00
UTC
05 Feb 2024, 00:00:00
—

Platform-specific formats

windows filetime
133515648000000000
apple cocoa time
728784000
excel serial date
45327.00000
ntp timestamp
3916080000
gps timestamp
Week 2300, ToW 86400s
.net datetime ticks
638426880000000000
webkit timestamp
13351564800000000
tai timestamp
1707091237
(UTC +37s, as of 2017)
julian date
2460345.50000
modified julian date (mjd)
60345.00000
lilian date
161185
unix day
19758

ABOUT THIS TIMESTAMP

Unix timestamp 1707091200 represents Monday, 5 February 2024 at 00:00:00 UTC. In milliseconds it is 1707091200000. This moment falls on day 36 of 2024, in week 6. The ISO 8601 representation is 2024-02-05T00:00:00.000Z. The Windows FILETIME equivalent is 133515648000000000. The Apple Cocoa timestamp is 728784000. The Excel serial date is 45327.00000. The NTP timestamp is 3916080000. The Modified Julian Date is 60345.00000. The Unix Day number is 19758.

DAY OF WEEK
Monday
DAY OF YEAR
36 of 366
WEEK NUMBER
Week 6
UNIX DAY
19758
LEAP YEAR
Yes
DAYS FROM TODAY
873 days ago
UTC OFFSET FROM NOW
-873 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.