Skip to content
MarketCalendars.com
Sign up

Unix timestamp converter

Convert epoch time to a date and a date to epoch time, in seconds, milliseconds, microseconds or nanoseconds and any time zone

Current Unix time, seconds

1793997785

Current Unix time, milliseconds

1793997785000
Read as ISO 8601 date in UTC
Jump to

Result

  • Unix time (seconds)1000425600
  • Milliseconds1000425600000
  • Microseconds1000425600000000
  • Nanoseconds1000425600000000000
  • ISO 8601 in UTC2001-09-14T00:00:00Z
  • ISO 8601 in UTC2001-09-14T00:00:00+00:00
  • RFC 9557 with zone2001-09-14T00:00:00+00:00[UTC]
  • RFC 2822 (email)Fri, 14 Sep 2001 00:00:00 +0000
  • SQL timestamp in UTC2001-09-14 00:00:00
  • Readable in UTCFri 14 Sep 2001, 00:00:00 UTC
  • Relative to now25 years 1 month ago
  • CalendarFriday, week 2001-W37, day 257 of the year

Time zones

  • UTC

    Fri 14 Sep 2001, 00:00:00

    UTC

    UTC+00:00

  • New York, United States

    Thu 13 Sep 2001, 20:00:00

    EDT

    UTC-04:00 summer

  • London, United Kingdom

    Fri 14 Sep 2001, 01:00:00

    BST

    UTC+01:00 summer

  • Tokyo, Japan

    Fri 14 Sep 2001, 09:00:00

    UTC+09:00

Markets at this moment

All markets on 14 Sep 2001
  • NYSE

    Closed following Attacks on the World Trade Center

    Closed

    Open at 09:33 on Mon 17 Sep

  • Nasdaq

    Closed following Attacks on the World Trade Center

    Closed

    Open at 09:33 on Mon 17 Sep

  • LSE

    Outside trading hours

    Closed

    Open at 08:00

  • Xetra

    Outside trading hours

    Closed

    Open at 09:00

  • TSE Tokyo

    Regular session

    Open

    Lunch break at 11:30

  • HKEX

    Outside trading hours

    Closed

    Open at 10:00

This forex trading week as Unix timestamps: opens 1793570400, closes 1794002400 (17:00 New York)

Forex market hours

Unix time in code

Get the current time and convert both ways. The examples use the value above

// Current Unix time in seconds
Math.floor(Date.now() / 1000)

// Unix time to date
new Date(1000425600 * 1000).toISOString()

// Date to Unix time
Date.parse("2001-09-14T00:00:00Z") / 1000

Notable timestamps

01970-01-01 00:00:00 UTCThe Unix epoch
-11969-12-31 23:59:59 UTCOne second before the epoch
10000000002001-09-09 01:46:40 UTCOne billion seconds
12345678902009-02-13 23:31:30 UTCThe digits in order
20000000002033-05-18 03:33:20 UTCTwo billion seconds
21474836472038-01-19 03:14:07 UTCLast second of signed 32-bit time

Units by number of digits

For timestamps from 2001 to 2286

DigitsUnitExample
10Seconds1793967600
13Milliseconds1793967600000
16Microseconds1793967600000000
19Nanoseconds1793967600000000000

Time spans in seconds

1 minute60
1 hour3,600
1 day86,400
1 week604,800
30 days2,592,000
365 days31,536,000
Average Gregorian year31,556,952

What it reads

  • Timestamps in any unit, negative or with a fraction, with or without separators such as 1,793,967,600
  • ISO 8601 and RFC 3339 dates, with Z, an offset or a zone in brackets as RFC 9557 writes it
  • RFC 2822 and HTTP dates, and the output of JavaScript's Date.toString()
  • Dates in words, such as 6 Nov 2026 2:30 pm or Nov 6, 2026
  • Slash dates in your date format; when the order is unclear, a note lets you swap day and month
  • Relative times: now, today, tomorrow, in 3 days, 2 hours ago, +90 minutes
  • A zone name after the date, such as 2026-11-06 09:30 Europe/London

Dates without an offset are read in the zone you choose. Unix time does not count leap seconds, so 23:59:60 is read as the next second.

Frequently asked questions

What is a Unix timestamp?

The number of seconds since 00:00:00 UTC on 1 January 1970, the Unix epoch, not counting leap seconds. It is the same everywhere in the world at a given moment, so it has no time zone. Times before 1970 are negative.

How do I tell seconds from milliseconds?

By the number of digits. A current timestamp has 10 digits in seconds, 13 in milliseconds, 16 in microseconds and 19 in nanoseconds. The converter picks the unit from the length and you can override it.

What happens to times that clocks skip or repeat?

When clocks go forward, a range of local times never happens, such as 02:30 in New York on 8 March 2026. The converter reads it with the offset from before the change, so 02:30 becomes 03:30 EDT. When clocks go back, a range happens twice; it shows the earlier one and lets you pick the later.

Why does EST or BST not work as a time zone?

Abbreviations are ambiguous: IST is used in India, Ireland and Israel, and CST in the US, China and Cuba. Use an offset such as -05:00 or a zone name such as America/New_York. Zone names also follow clock changes.

What is the year 2038 problem?

Systems that store Unix time as a signed 32-bit number run out at 2147483647, which is 03:14:07 UTC on 19 January 2038. The next second wraps to December 1901. 64-bit time does not have this limit.

Is there an API for this?

Yes. GET /api/v2/time/convert and /api/v2/time/now return the same conversions as JSON, free and with no key. See marketcalendars.com/docs/api/convert-time. To check whether a market was open at a timestamp, add at= to the status endpoint.

Related: 24-hour market timeline, world market map and thetime conversion API