Unix Timestamp Converter – Epoch Time & Date

Free Unix Timestamp (Epoch) Converter Tool

Current Unix Timestamp

0

Unix Timestamp to Date

Date to Unix Timestamp

Format: YYYY-MM-DD HH:mm:ss

In-depth guide

Unix timestamps: seconds, milliseconds, time zones and the converter's rules

What a Unix timestamp counts, how this page decides between seconds and milliseconds, how fixed UTC offsets differ from Local time, what date strings it accepts (and silently rolls over), with every example run on the real page.

Last verified: Sources: The Open Group — POSIX, Seconds Since the Epoch Plain-text version of this guide

Key figures at a glance

Epoch
1970-01-01 00:00:00 UTC = 0
Every POSIX day is counted as exactly 86,400 seconds, so leap seconds have no timestamp of their own.
Source: The Open Group — POSIX, Seconds Since the Epoch
Seconds or milliseconds
Below 10,000,000,000 = seconds; at or above = milliseconds
With the Include milliseconds box ticked every value is read as milliseconds.
Date input format
YYYY-MM-DD HH:mm:ss only
Out-of-range parts are not rejected: 2025-02-30 becomes 2025-03-02.
32-bit limit
2,147,483,647 = 2038-01-19 03:14:07 UTC
The page itself uses JavaScript numbers and handles years from -271821 to 275760.

What a timestamp is

A Unix (POSIX) timestamp is the number of seconds since the Epoch, 1970-01-01 00:00:00 UTC. It names one instant, independent of time zones. POSIX defines each day as exactly 86,400 seconds, so a leap second such as 23:59:60 does not get its own number. Values before 1970 are negative: -1 is 1969-12-31 23:59:59 UTC.

The same instant has a different wall-clock reading in each zone. 1737546000 is 11:40:00 UTC on 22 January 2025, which is 19:40 in Singapore (UTC+8).

Timestamp to date: what the page does

The top banner shows the current time as whole seconds from your device clock (it ticks every second). In the converter you enter a number, pick a time zone and press the button. It shows four lines: the UTC time, your local time (in your browser's format and language), the time at the selected fixed offset, and an ISO 8601 string in UTC with milliseconds.

Seconds or milliseconds. The rule is a size test, not a digit count. Without the box ticked, a value below 10,000,000,000 is multiplied by 1000 (seconds); a value at or above that is used as milliseconds. With the box ticked the value is always milliseconds. Verified results:

Input Box UTC result
0 off 1970-01-01T00:00:00.000Z
1737546000 off 2025-01-22T11:40:00.000Z
1737546000000 off 2025-01-22T11:40:00.000Z
1737546000 on 1970-01-21T02:39:06.000Z (read as ms)
2147483647 off 2038-01-19T03:14:07.000Z
-1 off 1969-12-31T23:59:59.000Z
9999999999 off 2286-11-20T17:46:39.000Z
10000000000 off 1970-04-26T17:46:40.000Z (now read as ms)
1737546000.5 off 2025-01-22T11:40:00.500Z

So the box is only needed to force small numbers to milliseconds, and seconds from the year 2286 onwards cannot be entered as seconds. Numbers too large for a date (about 1e20) show an "Invalid timestamp" alert; errors appear as browser alerts, not inline.

Time zones. "Local" uses your browser's zone database, including daylight saving time and historical offsets: with the browser set to Singapore, timestamp 0 shows 7:30:00 AM, because Singapore's offset in 1970 was UTC+7:30. The fixed choices (UTC-12 … UTC+14, including +5:30 and +9:30) always apply the same offset and never change with the season. Offsets such as +5:45, +3:30 and +8:45 are not offered.

Date to timestamp: strict format, loose values

The text must match YYYY-MM-DD HH:mm:ss exactly: four-digit year, two-digit parts, a space. These are rejected with an alert: 2025-01-22T09:00:00, 2025-01-22 09:00, 2025-01-22 09:00:00.500, 2025-01-22 09:00:00Z, 2025-1-22 09:00:00. The result shows seconds (rounded down) and milliseconds.

Matching the pattern does not make the date real. The numbers roll over like a calendar would:

Input (UTC) Result Reading
2025-02-30 10:00:00 1740909600 2025-03-02 10:00:00 UTC
2025-13-01 00:00:00 1767225600 2026-01-01 00:00:00 UTC
2025-01-22 24:00:00 1737590400 2025-01-23 00:00:00 UTC
2025-01-22 25:61:61 1737597721 2025-01-23 02:02:01 UTC

The same wall time gives different timestamps by zone. For 2025-01-22 09:00:00: UTC+8 gives 1737507600, UTC gives 1737536400, UTC-5 gives 1737554400 and UTC+5:30 gives 1737516600. The difference between UTC and UTC+8 is 28,800 seconds, eight hours. Other checks: 1969-12-31 23:59:59 UTC is -1, 9999-12-31 23:59:59 UTC is 253402300799, and 0099-01-01 00:00:00 UTC is -59042995200.

Tip: Always read the zone selector before trusting the number. A timestamp that is "off by eight hours" is nearly always a UTC versus UTC+8 mix-up, and 28,800 is the giveaway.

Edge cases and limits

  • Year 2038: 2147483647 is the largest signed 32-bit value. Systems storing seconds in 32 bits overflow after 2038-01-19 03:14:07 UTC; this page does not, because it uses JavaScript's 64-bit floating point.
  • Range: JavaScript dates span ±8,640,000,000,000,000 ms, about years -271821 to 275760. Near the extremes a fixed-offset line can show NaN because the offset pushes the date out of range.
  • Precision: milliseconds at most. Microsecond or nanosecond timestamps (16 or 19 digits) are read as milliseconds and give absurd dates or an error.
  • Fractional input is accepted for conversion; the Date to timestamp result is always rounded down to a whole second.

Common mistakes

  • Treating a 13-digit value as seconds in your own code; it is milliseconds.
  • Ticking the milliseconds box for a 10-digit value and getting 1970.
  • Typing 2025-02-30 and not noticing it became March.
  • Reading Local when you meant UTC, or the reverse.
  • Assuming fixed offsets follow daylight saving time; they do not.

Read a token's iat and exp with the JWT expiration checker, compare cities with the world clock, or find overlapping hours with the meeting time optimizer.

Frequently Asked Questions (FAQ)

What is a Unix timestamp?

A Unix timestamp is the number of seconds that have elapsed since January 1, 1970, 00:00:00 UTC (the Unix epoch). It's a simple way to represent a specific point in time as a single number, widely used in programming and databases.

How do I convert a Unix timestamp to a readable date?

Enter the timestamp in the "Unix Timestamp to Date" section, check whether it's in seconds (10 digits) or milliseconds (13 digits), and click "Convert to Date". The tool will display the date in your local timezone, UTC, and ISO 8601 format.

What's the difference between a 10-digit and 13-digit timestamp?

A 10-digit timestamp represents seconds since January 1, 1970, while a 13-digit timestamp represents milliseconds. Check "Include milliseconds" when working with 13-digit timestamps (commonly used in JavaScript).

Can I convert dates before 1970?

Yes! Dates before January 1, 1970 have negative Unix timestamps. For example, -86400 represents December 31, 1969. Our converter handles both positive and negative timestamps.

What is the Year 2038 problem?

On 32-bit systems, Unix timestamps overflow after January 19, 2038, 03:14:07 UTC (timestamp 2147483647). Modern 64-bit systems don't have this limitation and can handle dates far into the future.

Is my timezone automatically detected?

Yes, your browser's timezone is automatically detected and used for displaying local times and when converting dates to timestamps. You'll see both UTC and local time in the results.

How accurate are the Unix timestamp conversions?

Conversions are mathematically precise. Standard timestamps (seconds) are accurate to the nearest second, and millisecond timestamps are accurate to 1/1000th of a second (1 millisecond).

Can I use this tool for programming and development?

Absolutely! This tool is perfect for developers working with timestamps in any programming language including JavaScript, Python, PHP, Java, Ruby, Go, and more. It helps debug timestamp issues and test date/time functionality.

What is ISO 8601 format?

ISO 8601 is an international standard for date/time representation (format: 2025-01-22T09:00:00.000Z). The "Z" suffix indicates UTC/Zulu time. This format is widely used in REST APIs, JSON, and data interchange.

Does this Unix timestamp converter work offline?

After the initial page load, all conversions happen entirely in your browser using JavaScript. No data is sent to servers. However, you need internet connection to first access the page.

Why are there different times shown for UTC and local time?

Unix timestamps always represent a single moment in UTC time. The local time display shows how that same moment appears in your timezone, accounting for your UTC offset (e.g., UTC+8 for Singapore) and daylight saving time.

How do I get the current Unix timestamp?

The current Unix timestamp is displayed at the top of the page and updates in real-time every second. Click the "Copy" button to quickly copy it to your clipboard for use in your code or applications.

Sources

  1. The Open Group — POSIX.1-2017, Seconds Since the Epoch — Definition and the 86,400-seconds-per-day rule.
  2. ECMAScript language specification — Time values and time range — Date time values are milliseconds from the epoch within ±8,640,000,000,000,000.
  3. IETF — RFC 3339, Date and Time on the Internet: Timestamps — The ISO 8601 profile behind the 2025-01-22T11:40:00.000Z output.

This guide explains published rules in plain language. It is not financial, legal or official advice — rules change, so confirm with the agency linked above before you commit.

Embed this tool on your website

Free to use. Paste this code into your page and keep the link back to ToolSG.