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

Unix Timestamp Converter

Paste anything
✓ detected: unix timestamp (seconds)

Standard formats

unix timestamp (seconds)
1900000000
unix timestamp (milliseconds)
1900000000000
iso 8601 (utc)
2030-03-17T17:46:40.000Z
iso 8601 (local, no Z)
2030-03-17T17:46:40
rfc 2822 (email/http)
Sun, 17 Mar 2030 17:46:40 +0000
human readable
Sunday, 17 March 2030, 17:46:40 UTC

Timezones

UTC
17 Mar 2030, 17:46:40
UTC
17 Mar 2030, 17:46:40
—

Platform-specific formats

windows filetime
135444736000000000
apple cocoa time
921692800
excel serial date
47559.74074
ntp timestamp
4108988800
gps timestamp
Week 2619, ToW 64000s
.net datetime ticks
640355968000000000
webkit timestamp
13544473600000000
tai timestamp
1900000037
(UTC +37s, as of 2017)
julian date
2462578.24074
modified julian date (mjd)
62577.74074
lilian date
163417
unix day
21990

ABOUT THIS TIMESTAMP

Unix timestamp 1900000000 represents Sunday, 17 March 2030 at 17:46:40 UTC. In milliseconds it is 1900000000000. This moment falls on day 76 of 2030, in week 11. The ISO 8601 representation is 2030-03-17T17:46:40.000Z. The Windows FILETIME equivalent is 135444736000000000. The Apple Cocoa timestamp is 921692800. The Excel serial date is 47559.74074. The NTP timestamp is 4108988800. The Modified Julian Date is 62577.74074. The Unix Day number is 21990.

DAY OF WEEK
Sunday
DAY OF YEAR
76 of 365
WEEK NUMBER
Week 11
UNIX DAY
21990
LEAP YEAR
No
DAYS FROM TODAY
in 1359 days
UTC OFFSET FROM NOW
+1359 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.