Unix (s):1782526102
Unix (ms):1782526102763
ISO 8601:2026-06-27T02:08:22.763Z
live

Unix Timestamp Converter

Paste anything
✓ detected: unix timestamp (seconds)

Standard formats

unix timestamp (seconds)
345600
unix timestamp (milliseconds)
345600000
iso 8601 (utc)
1970-01-05T00:00:00.000Z
iso 8601 (local, no Z)
1970-01-05T00:00:00
rfc 2822 (email/http)
Mon, 05 Jan 1970 00:00:00 +0000
human readable
Monday, 5 January 1970, 00:00:00 UTC

Timezones

UTC
05 Jan 1970, 00:00:00
UTC
05 Jan 1970, 00:00:00
—

Platform-specific formats

windows filetime
116448192000000000
apple cocoa time
-977961600
excel serial date
25573.00000
ntp timestamp
2209334400
gps timestamp
Week -522, ToW 86400s
.net datetime ticks
621359424000000000
webkit timestamp
11644819200000000
tai timestamp
345637
(UTC +37s, as of 2017)
julian date
2440591.50000
modified julian date (mjd)
40591.00000
lilian date
141431
unix day
4

ABOUT THIS TIMESTAMP

Unix timestamp 345600 represents Monday, 5 January 1970 at 00:00:00 UTC. In milliseconds it is 345600000. This moment falls on day 5 of 1970, in week 1. The ISO 8601 representation is 1970-01-05T00:00:00.000Z. The Windows FILETIME equivalent is 116448192000000000. The Apple Cocoa timestamp is -977961600. The Excel serial date is 25573.00000. The NTP timestamp is 2209334400. The Modified Julian Date is 40591.00000. The Unix Day number is 4.

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