Unix (s):1782526189
Unix (ms):1782526189878
ISO 8601:2026-06-27T02:09:49.878Z
live

Unix Timestamp Converter

Paste anything
✓ detected: unix timestamp (seconds)

Standard formats

unix timestamp (seconds)
1111111111
unix timestamp (milliseconds)
1111111111000
iso 8601 (utc)
2005-03-18T01:58:31.000Z
iso 8601 (local, no Z)
2005-03-18T01:58:31
rfc 2822 (email/http)
Fri, 18 Mar 2005 01:58:31 +0000
human readable
Friday, 18 March 2005, 01:58:31 UTC

Timezones

UTC
18 Mar 2005, 01:58:31
UTC
18 Mar 2005, 01:58:31
—

Platform-specific formats

windows filetime
127555847110000000
apple cocoa time
132803911
excel serial date
38429.08230
ntp timestamp
3320099911
gps timestamp
Week 1314, ToW 439111s
.net datetime ticks
632467079110000000
webkit timestamp
12755584711000000
tai timestamp
1111111148
(UTC +37s, as of 2017)
julian date
2453447.58230
modified julian date (mjd)
53447.08230
lilian date
154287
unix day
12860

ABOUT THIS TIMESTAMP

Unix timestamp 1111111111 represents Friday, 18 March 2005 at 01:58:31 UTC. In milliseconds it is 1111111111000. This moment falls on day 77 of 2005, in week 11. The ISO 8601 representation is 2005-03-18T01:58:31.000Z. The Windows FILETIME equivalent is 127555847110000000. The Apple Cocoa timestamp is 132803911. The Excel serial date is 38429.08230. The NTP timestamp is 3320099911. The Modified Julian Date is 53447.08230. The Unix Day number is 12860.

DAY OF WEEK
Friday
DAY OF YEAR
77 of 365
WEEK NUMBER
Week 11
UNIX DAY
12860
LEAP YEAR
No
DAYS FROM TODAY
7771 days ago
UTC OFFSET FROM NOW
-7771 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.