Unix (s):1782526168
Unix (ms):1782526168060
ISO 8601:2026-06-27T02:09:28.060Z
live

Unix Timestamp Converter

Paste anything
✓ detected: unix timestamp (seconds)

Standard formats

unix timestamp (seconds)
1593561600
unix timestamp (milliseconds)
1593561600000
iso 8601 (utc)
2020-07-01T00:00:00.000Z
iso 8601 (local, no Z)
2020-07-01T00:00:00
rfc 2822 (email/http)
Wed, 01 Jul 2020 00:00:00 +0000
human readable
Wednesday, 1 July 2020, 00:00:00 UTC

Timezones

UTC
01 Jul 2020, 00:00:00
UTC
01 Jul 2020, 00:00:00

Platform-specific formats

windows filetime
132380352000000000
apple cocoa time
615254400
excel serial date
44013.00000
ntp timestamp
3802550400
gps timestamp
Week 2112, ToW 259200s
.net datetime ticks
637291584000000000
webkit timestamp
13238035200000000
tai timestamp
1593561637
(UTC +37s, as of 2017)
julian date
2459031.50000
modified julian date (mjd)
59031.00000
lilian date
159871
unix day
18444

ABOUT THIS TIMESTAMP

Unix timestamp 1593561600 represents Wednesday, 1 July 2020 at 00:00:00 UTC. In milliseconds it is 1593561600000. This moment falls on day 183 of 2020, in week 27. The ISO 8601 representation is 2020-07-01T00:00:00.000Z. The Windows FILETIME equivalent is 132380352000000000. The Apple Cocoa timestamp is 615254400. The Excel serial date is 44013.00000. The NTP timestamp is 3802550400. The Modified Julian Date is 59031.00000. The Unix Day number is 18444.

DAY OF WEEK
Wednesday
DAY OF YEAR
183 of 366
WEEK NUMBER
Week 27
UNIX DAY
18444
LEAP YEAR
Yes
DAYS FROM TODAY
2187 days ago
UTC OFFSET FROM NOW
-2187 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.