Unix Timestamp Converter

Instantly convert Epoch timestamps to dates across 400+ global timezones.

Current Unix Time

Timestamp to Date

UTC Time (Universal)
Target Time ()

Human Date to Timestamp

Generated Timestamp

What is Unix Time?

Computers need a simple, unambiguous way to record moments in time. Writing “16/10/2026 5:30 PM” is confusing — is that day-month or month-day? Which time zone? Unix time solves this by counting the seconds elapsed since the “Unix epoch”: 00:00:00 UTC on 1 January 1970. The timestamp 1800000000, for example, is one specific instant, no matter where you are.

Databases, server logs, APIs, JWT tokens and analytics tools all use Unix timestamps. This converter turns those numbers into readable dates in any of 400+ time zones, and turns dates back into timestamps.

How to Use the Timestamp Converter

Timestamp to date

  1. Paste the timestamp into Enter Timestamp.
  2. Select Seconds or Milliseconds.
  3. Choose a target time zone. You will see the date in your local time, in UTC and in the selected zone.

Date to timestamp

  1. Pick a date and time.
  2. Select the time zone that date belongs to.
  3. Copy the generated timestamp.

The live clock at the top shows the current Unix time, ticking every second.

Example Timestamps

TimestampUTCIndia (IST)
01 Jan 1970, 00:00:001 Jan 1970, 05:30:00
17356896001 Jan 2025, 00:00:001 Jan 2025, 05:30:00
180000000015 Jan 2027, 08:00:0015 Jan 2027, 13:30:00
214748364719 Jan 2038, 03:14:0719 Jan 2038, 08:44:07

Seconds vs Milliseconds

The most common timestamp bug is mixing up seconds and milliseconds. If a converted date shows a year like 57,000 or 1970, you probably used the wrong unit.

  • 10 digits → seconds (Unix, PHP, MySQL, most APIs)
  • 13 digits → milliseconds (JavaScript, Java, many analytics tools)

To convert, multiply seconds by 1,000 or divide milliseconds by 1,000.

Getting Timestamps in Code

// JavaScript (seconds)
Math.floor(Date.now() / 1000)

// PHP
time();

# Python
import time; int(time.time())

-- MySQL
SELECT UNIX_TIMESTAMP();

# Linux / macOS shell
date +%s

Why Developers Prefer Timestamps

  • Time zone independent: store once in UTC, display in the user’s local time.
  • Easy maths: the difference between two timestamps is simply the number of seconds between them.
  • Compact and sortable: a single integer sorts correctly and indexes efficiently in databases.

The Year 2038 Problem

Older systems store Unix time as a signed 32-bit integer, whose maximum value is 2,147,483,647 — reached on 19 January 2038 at 03:14:07 UTC. One second later, such systems would wrap around to a negative number representing December 1901. Modern 64-bit systems are not affected, but embedded devices and legacy software still need checking.

Related Tools

Frequently Asked Questions

A Unix timestamp (also called epoch time or POSIX time) is the number of seconds that have passed since 00:00:00 UTC on 1 January 1970, not counting leap seconds. It is a single number that represents the same instant everywhere in the world.
Current timestamps in seconds have 10 digits (for example 1800000000), while millisecond timestamps have 13 digits (1800000000000). JavaScript's Date.now() returns milliseconds; most Unix tools, PHP and databases use seconds.
Systems that store Unix time as a signed 32-bit integer can only count up to 2,147,483,647, which is reached at 03:14:07 UTC on 19 January 2038. After that the number overflows. Modern systems use 64-bit integers, which avoids the problem for billions of years.
No. The timestamp itself is always based on UTC. Time zones only matter when you display it as a human-readable date, which is why the converter lets you choose a target time zone.
Choose the date and time, set the time zone to Asia/Kolkata and generate the timestamp. IST is UTC+5:30, so midnight on 1 January 2025 in India is 1735669800, five and a half hours before UTC midnight (1735689600).
JavaScript: Math.floor(Date.now() / 1000). PHP: time(). Python: int(time.time()). MySQL: UNIX_TIMESTAMP(). Linux shell: date +%s.