search⌘KtranslateENexpand_moreupload_fileConvert

Free Unix Timestamp Converter Online

Timestamp converter

Turn Unix timestamps into readable dates and back: seconds or milliseconds, in your time zone and UTC, plus every format developers need.

current unix time1792277477

Timestamp → dateDate → timestamp

Unix timestampcheck_circleDetected seconds (10 digits)

DateTime

Jump to

Now1 hour agoTomorrowStart of today1 Jan 20002038 limit

in the pastMonday, 21 September 2026 at 17:13:2026 days ago

Seconds1790000000content_copyMilliseconds1790000000000content_copyISO 8601 (UTC)2026-09-21T14:13:20.000Zcontent_copyLocal (Europe/Istanbul)Monday, 21 September 2026 at 17:13:20 GMT+3content_copyUTCMon, 21 Sep 2026 14:13:20 GMTcontent_copyRFC 2822Mon, 21 Sep 2026 14:13:20 +0000content_copySQL datetime2026-09-21 14:13:20content_copyDay of yearday 264 · week 39content_copy

~/counting-since-1970

One number for every moment.

A Unix timestamp is simply the number of seconds since midnight UTC on 1 January 1970. No time zones, no months, no leap-year rules, which is why computers love it.

now · 1792277477

19701980199020002010202020302038

1 Jan 1970the epoch: timestamp 001 Jan 2000Y2K946,684,8009 Sep 2001first 10-digit timestamp1,000,000,00013 Feb 2009the 1234567890 party1,234,567,890Todaywhere we are now1,792,277,47718 May 2033timestamp 2,000,000,0002,000,000,00019 Jan 2038the 32-bit limit2,147,483,647

86,400Seconds in a dayAdd or subtract this to move a timestamp by one day: ignoring daylight-saving shifts.

10 vs 13Digits tell the unitTen digits is seconds (most APIs, databases). Thirteen is milliseconds (JavaScript, Java).

2038The 32-bit deadlineOld systems store seconds in a signed 32-bit number, which overflows on 19 January 2038.

~/one-string-six-readings

Paste a date string and see who agrees on what it means.

“2026-09-21” is midnight UTC to JavaScript, but “2026-09-21T14:13” is in your local time zone. “09/10/2026” is September in the US and October in the UK. Below, one string goes through your browser's own parser and five format rules, each checked by this page: the ECMAScript date format, ISO 8601 (including week and ordinal dates), RFC 3339, the HTTP and email date formats, and slash dates.

northUse in converter

2026-09-212026-09-21T14:13:202026-09-21T14:13:20Z2026-09-21T14:13:20+03:002026-09-21 14:13:2020260921T141320Z2026-W39-12026-264Mon, 21 Sep 2026 14:13:20 GMT09/10/20262016-12-31T23:59:60Z

readerverdictthe instant, in UTCwhy

JavaScript Date.parsethis browserparsed2026-09-21T11:13:20.000ZNo offset and a time, so read as local time in Europe/Istanbul.

ECMAScript date formatECMA-262 §21.4.1.32yes2026-09-21T11:13:20.000ZEvery browser must parse this exactly the same way.

ISO 8601ISO 8601-1:2019valid2026-09-21T14:13:20.000Z if UTCA calendar date with a time but no offset: ISO calls this local time, zone unknown.

RFC 3339internet timestampsno-Needs all of YYYY-MM-DD, T, HH:MM:SS and Z or ±HH:MM. Dates without a time or offset aren’t allowed.

HTTP and email datesRFC 9110 · RFC 5322no-Needs the form Mon, 21 Sep 2026 14:13:20 GMT.

Slash dateregional, no standardn/a-Not a dd/mm/yyyy or mm/dd/yyyy string.

lightbulbThe readers that accept it agree here, but not every system will accept this form. RFC 3339 with an offset is the safe choice.

~/when-clocks-change

Some local times happen twice. Some never happen at all.

Unix time never jumps, but local time does. Pick a zone and a year. Your browser's copy of the IANA time zone database is scanned hour by hour and narrowed to the exact minute each offset changes. It then shows the hour that is skipped, the hour that repeats, and why adding 86,400 seconds is not the same as adding a day.

Your zoneLondonNew YorkSydneyLord HoweKolkataIstanbulSão PauloChatham

chevron_left2026chevron_right

Europe/London · offset from UTC on the 15th of each month418 zones in this browser’s database

Jan+0Feb+0Mar+0Apr+1May+1Jun+1Jul+1Aug+1Sep+1Oct+1Nov+0Dec+0

fast_forwardClocks go forward 1 hour on 2026-03-29At 01:00 local time the clock jumps to 02:00. Local times from 01:00 to 01:59 never happen, so an alarm or meeting set then has no real moment.at 2026-03-29T01:00Z · unix 1774746000 · UTC+00:00 → UTC+01:00

replayClocks go back 1 hour on 2026-10-25At 02:00 local time the clock goes back to 01:00. Every time from 01:00 to 01:59 happens twice, so a local timestamp in that hour is ambiguous without its offset.at 2026-10-25T01:00Z · unix 1792890000 · UTC+01:00 → UTC+00:00

No clock changes in 2026: Europe/London stays at UTC+00:00 all year.

add one day across the change

start, 12 hours before the change2026-03-28 13:00 UTC+00:00

+ 86,400 seconds2026-03-29 14:00 UTC+01:00

+ 1 calendar day, same wall time2026-03-29 13:00 UTC+01:00

That calendar day lasted 23 hours, not 24. Code that adds 86,400 to move “one day” drifts by 60 minutes; use your language’s calendar arithmetic in the user’s zone instead.

~/common-bugs

Four timestamp bugs, and how to spot them.

bug_reportDates in 1970A timestamp in seconds was treated as milliseconds, or it was 0 / null.new Date(1790000000) → Wed 21 Jan 1970buildMultiply seconds by 1000 in JavaScript, and check for empty values.

bug_reportDates 50,000 years awayThe reverse: milliseconds were treated as seconds.fromtimestamp(1790000000000) → year 58,691buildDivide by 1000, or check for 13 digits before converting.

bug_reportOff by a few hoursThe date was shown in UTC when the user expected local time, or the other way round.14:13 UTC shown to a user in Istanbul (+03:00)buildStore in UTC, convert to the viewer’s time zone only when displaying.

bug_reportOff by one dayMidnight in one zone is still the previous day in another.2026-09-21T00:30+03:00 = 2026-09-20 21:30 UTCbuildCompare full timestamps, not just the date part, across zones.

~/in-your-language

Get the current timestamp in code.

JavaScriptPythonPHPGoSQLBash

secondsMath.floor(Date.now() / 1000)

millisecondsDate.now()

to datenew Date(ts * 1000).toISOString()

~/reference

Twelve clocks, twelve starting points, one instant.

Unix time is only one of many epoch-based clocks. Each row converts the instant in the converter at the top of the page, 2026-09-21T14:13:20.000Z, using exact whole-number arithmetic for the 64-bit tick counts.

clockepochunitthis instantused by

Unix time1970-01-01 UTCseconds1790000000content_copyPOSIX, Linux, most APIs and databases

JavaScript, Java1970-01-01 UTCmilliseconds1790000000000content_copyDate.now(), System.currentTimeMillis()

NTP1900-01-01 UTCseconds, 32-bit eras3998988800content_copyNetwork Time Protocol; era 0 wraps on 7 Feb 2036

GPS time1980-01-06 UTCseconds, no leap seconds1474035218content_copySatellite navigation; ahead of UTC by the leap seconds since 1980

Windows FILETIME1601-01-01 UTC100 ns ticks134344736000000000content_copyNTFS timestamps, Win32 APIs, Active Directory

.NET DateTime.Ticks0001-01-01100 ns ticks639255968000000000content_copyC#, PowerShell, SQL Server datetime2

Chrome / WebKit1601-01-01 UTCmicroseconds13434473600000000content_copyBrowser history and cookie databases

Apple Cocoa2001-01-01 UTCseconds811692800content_copyCFAbsoluteTime, NSDate, iOS and macOS

Classic Mac, HFS+1904-01-01seconds3872844800content_copyHFS+ volumes, QuickTime atoms, Excel for Mac 1904 mode

Excel 1900 system1899-12-30, in effectdays, fractional46286.592593content_copySpreadsheet serial dates; includes the fictional 29 Feb 1900

Julian Day24 Nov 4714 BC, noondays2461305.092593content_copyAstronomy; days since a single ancient starting point

UUID v1 / v61582-10-15 UTC100 ns ticks140092928000000000content_copyThe timestamp inside time-based UUIDs

37 sTAI is ahead of UTCInternational Atomic Time never pauses. Since 1 January 2017 it has been 37 seconds ahead of UTC.

18 sGPS is ahead of UTCGPS time started equal to UTC in 1980 and has never added a leap second, so it’s now 18 seconds ahead.

27leap seconds since 1972The last was 23:59:60 UTC on 31 December 2016. Unix time pretends it never happened, repeating or smearing a second.

How we agreed on what time it is

1847Railway timeBritish railways adopt Greenwich time, ending a patchwork of local solar times.

1884Prime MeridianThe International Meridian Conference fixes longitude 0° at Greenwich.

1970The Unix epochEarly Unix counts in sixtieths of a second; by 1973 it settles on seconds since 1970.

1972UTC and leap secondsUTC adopts atomic seconds, adding leap seconds to stay within 0.9 s of Earth’s rotation.

1988ISO 8601The first edition of the international standard for writing dates and times.

2002RFC 3339A strict internet profile of ISO 8601 for timestamps in protocols.

2022Leap seconds to endThe CGPM votes to stop inserting leap seconds by 2035.

2024RFC 9557Extends RFC 3339 with a time zone suffix such as [Europe/London].

Sources

[1]RFC 3339Date and Time on the Internet: the strict profile checked in the parser lab.IETF ↗[2]RFC 9557Adds time zone names and extensions to RFC 3339 timestamps.IETF ↗[3]ECMAScript Date Time String FormatWhich strings every browser must parse, and the date-only UTC rule.TC39 ↗[4]Seconds Since the EpochPOSIX’s exact formula for Unix time, which ignores leap seconds.The Open Group ↗[5]IANA Time Zone DatabaseThe tz data your browser used to find the clock changes above.IANA ↗[6]IERS Bulletin CAnnounces each leap second, or that none is due.IERS ↗

More date & time tools

For the questions a timestamp doesn't answer directly.

All tools →

date_rangeDate Difference

Exact days, weeks and months between two dates.

1 Jan → 21 Separrow_forward263 days

scheduleTime Duration

Add or subtract hours and minutes.

09:15 + 8h 25marrow_forward17:40

eventWeekday Finder

Which day of the week any date falls on.

19 Jan 2038arrow_forwardTuesday

more_timeCron Generator

Build a schedule expression visually.

every weekday 9amarrow_forward0 9 * * 1-5

straightenUnit Converter

Convert seconds, hours, days and years, and 8 other unit types.

1,000,000 sarrow_forward11.6 days

cakeAge Calculator

Exact age in years, months and days.

1990-05-14arrow_forward36 y 4 m