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

Unix Timestamp Converter

Paste anything
✓ detected: unix timestamp (seconds)

Standard formats

unix timestamp (seconds)
1643673600
unix timestamp (milliseconds)
1643673600000
iso 8601 (utc)
2022-02-01T00:00:00.000Z
iso 8601 (local, no Z)
2022-02-01T00:00:00
rfc 2822 (email/http)
Tue, 01 Feb 2022 00:00:00 +0000
human readable
Tuesday, 1 February 2022, 00:00:00 UTC

Timezones

UTC
01 Feb 2022, 00:00:00
UTC
01 Feb 2022, 00:00:00
—

Platform-specific formats

windows filetime
132881472000000000
apple cocoa time
665366400
excel serial date
44593.00000
ntp timestamp
3852662400
gps timestamp
Week 2195, ToW 172800s
.net datetime ticks
637792704000000000
webkit timestamp
13288147200000000
tai timestamp
1643673637
(UTC +37s, as of 2017)
julian date
2459611.50000
modified julian date (mjd)
59611.00000
lilian date
160451
unix day
19024

ABOUT THIS TIMESTAMP

Unix timestamp 1643673600 represents Tuesday, 1 February 2022 at 00:00:00 UTC. In milliseconds it is 1643673600000. This moment falls on day 32 of 2022, in week 5. The ISO 8601 representation is 2022-02-01T00:00:00.000Z. The Windows FILETIME equivalent is 132881472000000000. The Apple Cocoa timestamp is 665366400. The Excel serial date is 44593.00000. The NTP timestamp is 3852662400. The Modified Julian Date is 59611.00000. The Unix Day number is 19024.

DAY OF WEEK
Tuesday
DAY OF YEAR
32 of 365
WEEK NUMBER
Week 5
UNIX DAY
19024
LEAP YEAR
No
DAYS FROM TODAY
1607 days ago
UTC OFFSET FROM NOW
-1607 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.