Unix (s):1782526294
Unix (ms):1782526294656
ISO 8601:2026-06-27T02:11:34.656Z
live

Unix Timestamp Converter

Paste anything
✓ detected: unix timestamp (seconds)

Standard formats

unix timestamp (seconds)
1741046400
unix timestamp (milliseconds)
1741046400000
iso 8601 (utc)
2025-03-04T00:00:00.000Z
iso 8601 (local, no Z)
2025-03-04T00:00:00
rfc 2822 (email/http)
Tue, 04 Mar 2025 00:00:00 +0000
human readable
Tuesday, 4 March 2025, 00:00:00 UTC

Timezones

UTC
04 Mar 2025, 00:00:00
UTC
04 Mar 2025, 00:00:00
—

Platform-specific formats

windows filetime
133855200000000000
apple cocoa time
762739200
excel serial date
45720.00000
ntp timestamp
3950035200
gps timestamp
Week 2356, ToW 172800s
.net datetime ticks
638766432000000000
webkit timestamp
13385520000000000
tai timestamp
1741046437
(UTC +37s, as of 2017)
julian date
2460738.50000
modified julian date (mjd)
60738.00000
lilian date
161578
unix day
20151

ABOUT THIS TIMESTAMP

Unix timestamp 1741046400 represents Tuesday, 4 March 2025 at 00:00:00 UTC. In milliseconds it is 1741046400000. This moment falls on day 63 of 2025, in week 9. The ISO 8601 representation is 2025-03-04T00:00:00.000Z. The Windows FILETIME equivalent is 133855200000000000. The Apple Cocoa timestamp is 762739200. The Excel serial date is 45720.00000. The NTP timestamp is 3950035200. The Modified Julian Date is 60738.00000. The Unix Day number is 20151.

DAY OF WEEK
Tuesday
DAY OF YEAR
63 of 365
WEEK NUMBER
Week 9
UNIX DAY
20151
LEAP YEAR
No
DAYS FROM TODAY
480 days ago
UTC OFFSET FROM NOW
-480 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.