Unix Timestamp Converter

Convert Unix epoch timestamps in seconds and milliseconds to human-readable ISO 8601, UTC, and local date/time.

Current Unix Epoch Time: 1788292800 .000

Enter Unix Timestamp

Auto-detected: 10 digits (Seconds)

💻 Developer Quick Snippets

JavaScript Math.floor(Date.now() / 1000)
Python import time; int(time.time())
Bash / CLI date +%s
Go time.Now().Unix()

Standard Date & Time Formats

ISO 8601 (Standard)
2026-09-01T20:00:00.000Z
UTC / GMT Date
Tue, 01 Sep 2026 20:00:00 GMT
Your Local Time
01/09/2026, 21:00:00 (BST)
Relative Time
Just now
Epoch Milliseconds
1788292800000

⚖️ Decision Verdict: Valid Unix Timestamp

Timestamp 1788292800 represents Tuesday, September 1, 2026 at 20:00:00 UTC.

Calendar & Epoch Telemetry

Seconds Since Epoch (1970)
1,788,292,800
Standard POSIX / Unix time integer
Days Until Year 2038 Bug
4,157 Days
Before 32-bit signed int overflow (2,147,483,647)
Day of Year
Day 244
Non-leap year (365 days)
ISO Week Number Week 36 Calendar work week
Leap Year No (2026) 28 days in February
Detected Timezone UTC Browser IANA timezone
Days in Month 30 Days September length

About this tool

How to use it

  1. Select your conversion direction: Timestamp to Human Date, or Human Date to Timestamp.
  2. Enter any 10-digit epoch timestamp in seconds (or 13-digit timestamp in milliseconds).
  3. View instant conversions across ISO 8601, UTC/GMT, your local browser timezone, and relative time ago.
  4. Copy formatted values with 1-click clipboard buttons.
  5. Inspect telemetry metrics including day of year, calendar week number, leap year status, and Year 2038 bug countdown.

Why it matters

Unix time (POSIX time) is the foundational temporal standard in operating systems, databases, distributed logs, and API protocols. Because machines track time as the number of seconds elapsed since January 1, 1970 00:00:00 UTC, software engineers frequently need rapid, accurate conversions between raw epoch integers and readable calendar dates across timezones.

When to use it

Use this tool when debugging server logs, querying SQL databases (UNIX_TIMESTAMP), verifying JWT expiration tokens (exp claim), or configuring cron schedules.

Good to know

Year 2038 Problem (Y2K38): On January 19, 2038 at 03:14:07 UTC, 32-bit signed integers will overflow from 2,147,483,647 to -2,147,483,648, resetting clocks to December 13, 1901. Modern systems mitigate this by transitioning to 64-bit timestamps.

Common questions

What is the Unix epoch?

The Unix epoch is the reference point from which time is measured in Unix-like operating systems: 00:00:00 Coordinated Universal Time (UTC) on Thursday, January 1, 1970. Every Unix timestamp is simply the number of non-leap seconds elapsed since that moment.

How do I tell seconds from milliseconds?

Timestamps measured in seconds are currently 10 digits long (e.g., 1,788,000,000 in 2026). Timestamps in milliseconds (standard in JavaScript `Date.now()`) are 13 digits long. This converter automatically detects and handles both.

What is the Year 2038 Problem?

The Year 2038 problem occurs when systems storing Unix time in a signed 32-bit integer exceed their maximum positive value of 2,147,483,647 seconds on January 19, 2038 at 03:14:07 UTC. Upgrading software and embedded kernels to 64-bit time integers solves the issue for the next 292 billion years.

Does Unix time account for leap seconds?

Strict POSIX Unix time ignores leap seconds. When an official leap second is inserted by the International Earth Rotation Service (IERS), Unix timestamps either repeat a second or utilize network time protocol (NTP) leap smearing to stretch seconds smoothly.

How do I get the current Unix timestamp in SQL?

In MySQL/MariaDB, run `SELECT UNIX_TIMESTAMP();`. In PostgreSQL, run `SELECT EXTRACT(EPOCH FROM NOW());`. In SQLite, run `SELECT strftime('%s', 'now');`.