Unix (s):1782526127
Unix (ms):1782526127738
ISO 8601:2026-06-27T02:08:47.738Z
live

Unix Timestamp Converter

Paste anything
✓ detected: unix timestamp (seconds)

Standard formats

unix timestamp (seconds)
496800
unix timestamp (milliseconds)
496800000
iso 8601 (utc)
1970-01-06T18:00:00.000Z
iso 8601 (local, no Z)
1970-01-06T18:00:00
rfc 2822 (email/http)
Tue, 06 Jan 1970 18:00:00 +0000
human readable
Tuesday, 6 January 1970, 18:00:00 UTC

Timezones

UTC
06 Jan 1970, 18:00:00
UTC
06 Jan 1970, 18:00:00
—

Platform-specific formats

windows filetime
116449704000000000
apple cocoa time
-977810400
excel serial date
25574.75000
ntp timestamp
2209485600
gps timestamp
Week -522, ToW 237600s
.net datetime ticks
621360936000000000
webkit timestamp
11644970400000000
tai timestamp
496837
(UTC +37s, as of 2017)
julian date
2440593.25000
modified julian date (mjd)
40592.75000
lilian date
141432
unix day
5

ABOUT THIS TIMESTAMP

Unix timestamp 496800 represents Tuesday, 6 January 1970 at 18:00:00 UTC. In milliseconds it is 496800000. This moment falls on day 6 of 1970, in week 1. The ISO 8601 representation is 1970-01-06T18:00:00.000Z. The Windows FILETIME equivalent is 116449704000000000. The Apple Cocoa timestamp is -977810400. The Excel serial date is 25574.75000. The NTP timestamp is 2209485600. The Modified Julian Date is 40592.75000. The Unix Day number is 5.

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