Unix (s):1782526626
Unix (ms):1782526626417
ISO 8601:2026-06-27T02:17:06.417Z
live

Unix Timestamp Converter

Paste anything
✓ detected: unix timestamp (seconds)

Standard formats

unix timestamp (seconds)
1388534400
unix timestamp (milliseconds)
1388534400000
iso 8601 (utc)
2014-01-01T00:00:00.000Z
iso 8601 (local, no Z)
2014-01-01T00:00:00
rfc 2822 (email/http)
Wed, 01 Jan 2014 00:00:00 +0000
human readable
Wednesday, 1 January 2014, 00:00:00 UTC

Timezones

UTC
01 Jan 2014, 00:00:00
UTC
01 Jan 2014, 00:00:00
—

Platform-specific formats

windows filetime
130330080000000000
apple cocoa time
410227200
excel serial date
41640.00000
ntp timestamp
3597523200
gps timestamp
Week 1773, ToW 259200s
.net datetime ticks
635241312000000000
webkit timestamp
13033008000000000
tai timestamp
1388534437
(UTC +37s, as of 2017)
julian date
2456658.50000
modified julian date (mjd)
56658.00000
lilian date
157498
unix day
16071

ABOUT THIS TIMESTAMP

Unix timestamp 1388534400 represents Wednesday, 1 January 2014 at 00:00:00 UTC. In milliseconds it is 1388534400000. This moment falls on day 1 of 2014, in week 1. The ISO 8601 representation is 2014-01-01T00:00:00.000Z. The Windows FILETIME equivalent is 130330080000000000. The Apple Cocoa timestamp is 410227200. The Excel serial date is 41640.00000. The NTP timestamp is 3597523200. The Modified Julian Date is 56658.00000. The Unix Day number is 16071.

DAY OF WEEK
Wednesday
DAY OF YEAR
1 of 365
WEEK NUMBER
Week 1
UNIX DAY
16071
LEAP YEAR
No
DAYS FROM TODAY
4560 days ago
UTC OFFSET FROM NOW
-4560 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.