Unix (s):1782526682
Unix (ms):1782526682462
ISO 8601:2026-06-27T02:18:02.462Z
live

Unix Timestamp Converter

Paste anything
✓ detected: unix timestamp (seconds)

Standard formats

unix timestamp (seconds)
1500000000
unix timestamp (milliseconds)
1500000000000
iso 8601 (utc)
2017-07-14T02:40:00.000Z
iso 8601 (local, no Z)
2017-07-14T02:40:00
rfc 2822 (email/http)
Fri, 14 Jul 2017 02:40:00 +0000
human readable
Friday, 14 July 2017, 02:40:00 UTC

Timezones

UTC
14 Jul 2017, 02:40:00
UTC
14 Jul 2017, 02:40:00
—

Platform-specific formats

windows filetime
131444736000000000
apple cocoa time
521692800
excel serial date
42930.11111
ntp timestamp
3708988800
gps timestamp
Week 1957, ToW 441600s
.net datetime ticks
636355968000000000
webkit timestamp
13144473600000000
tai timestamp
1500000037
(UTC +37s, as of 2017)
julian date
2457948.61111
modified julian date (mjd)
57948.11111
lilian date
158788
unix day
17361

ABOUT THIS TIMESTAMP

Unix timestamp 1500000000 represents Friday, 14 July 2017 at 02:40:00 UTC. In milliseconds it is 1500000000000. This moment falls on day 195 of 2017, in week 28. The ISO 8601 representation is 2017-07-14T02:40:00.000Z. The Windows FILETIME equivalent is 131444736000000000. The Apple Cocoa timestamp is 521692800. The Excel serial date is 42930.11111. The NTP timestamp is 3708988800. The Modified Julian Date is 57948.11111. The Unix Day number is 17361.

DAY OF WEEK
Friday
DAY OF YEAR
195 of 365
WEEK NUMBER
Week 28
UNIX DAY
17361
LEAP YEAR
No
DAYS FROM TODAY
3270 days ago
UTC OFFSET FROM NOW
-3270 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.