Unix (s):1782526323
Unix (ms):1782526323927
ISO 8601:2026-06-27T02:12:03.927Z
live

Unix Timestamp Converter

Paste anything
✓ detected: unix timestamp (seconds)

Standard formats

unix timestamp (seconds)
1656633600
unix timestamp (milliseconds)
1656633600000
iso 8601 (utc)
2022-07-01T00:00:00.000Z
iso 8601 (local, no Z)
2022-07-01T00:00:00
rfc 2822 (email/http)
Fri, 01 Jul 2022 00:00:00 +0000
human readable
Friday, 1 July 2022, 00:00:00 UTC

Timezones

UTC
01 Jul 2022, 00:00:00
UTC
01 Jul 2022, 00:00:00
—

Platform-specific formats

windows filetime
133011072000000000
apple cocoa time
678326400
excel serial date
44743.00000
ntp timestamp
3865622400
gps timestamp
Week 2216, ToW 432000s
.net datetime ticks
637922304000000000
webkit timestamp
13301107200000000
tai timestamp
1656633637
(UTC +37s, as of 2017)
julian date
2459761.50000
modified julian date (mjd)
59761.00000
lilian date
160601
unix day
19174

ABOUT THIS TIMESTAMP

Unix timestamp 1656633600 represents Friday, 1 July 2022 at 00:00:00 UTC. In milliseconds it is 1656633600000. This moment falls on day 182 of 2022, in week 26. The ISO 8601 representation is 2022-07-01T00:00:00.000Z. The Windows FILETIME equivalent is 133011072000000000. The Apple Cocoa timestamp is 678326400. The Excel serial date is 44743.00000. The NTP timestamp is 3865622400. The Modified Julian Date is 59761.00000. The Unix Day number is 19174.

DAY OF WEEK
Friday
DAY OF YEAR
182 of 365
WEEK NUMBER
Week 26
UNIX DAY
19174
LEAP YEAR
No
DAYS FROM TODAY
1457 days ago
UTC OFFSET FROM NOW
-1457 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.