Unix Timestamp Converter

Convert timestamps to human-readable dates and dates to Unix epochs instantly in your browser.

Detected: Seconds
Presets:
Enterto convert instantly

Parsed Date & Representations

last year
Local Time
Wed, Sep 17, 2025, 15:37:36
UTC Time
Wed, Sep 17, 2025, 15:37:36 UTC
ISO 8601
2025-09-17T15:37:36.000Z
Unix Seconds
1758123456
Unix Milliseconds
1758123456000
  • Local Processing
    All conversions happen directly in your browser. No date or timestamp data is sent to a server.
  • Seconds & Milliseconds
    Automatically detect or manually select common Unix timestamp units.
  • UTC & Local Time
    View the same instant using UTC or your local timezone.

Knowledge Base

Understanding Unix Timestamps

A Unix timestamp represents the total number of seconds (or milliseconds) elapsed since the Unix Epoch: January 1, 1970 at 00:00:00 UTC, excluding leap seconds.

The Unix Epoch

January 1, 1970, 00:00:00 UTC marks timestamp 0. Negative numbers represent dates prior to the epoch, while positive numbers represent future dates.

Unix Epoch (0):1970-01-01 00:00:00 UTC
Current Epoch (~1.7B):Contemporary 2020s

The Year 2038 Problem

On January 19, 2038 at 03:14:07 UTC, signed 32-bit Unix timestamps reach 2,147,483,647 seconds and roll over to negative numbers. Modern 64-bit systems and JavaScript's double-precision floating-point numbers are not restricted by this 32-bit limit and safely represent timestamps for over 285,000 years.

Max 32-bit timestamp:2,147,483,647
Overflow boundary:2038-01-19 03:14:07 UTC

Seconds vs. Milliseconds Comparison

AttributeUnix SecondsUnix Milliseconds
Typical size~10 digits (e.g. 1704067200)~13 digits (e.g. 1704067200000)
JavaScript usageMath.floor(Date.now() / 1000)Date.now() or date.getTime()
Common ecosystemsPOSIX, Linux, MySQL, REST APIsBrowsers, JavaScript, MongoDB, Java

Troubleshooting 10-digit vs 13-digit timestamp bugs or unexpected 1970 dates?

Read Seconds vs Milliseconds Guide
Developer Quickstart

Current Timestamp & Conversion Cheat Sheet

How to retrieve the current epoch and convert timestamps across major programming languages.

// Get current Unix timestamps
const seconds = Math.floor(Date.now() / );
const milliseconds = Date.now();

// Convert timestamp (seconds) to Date
const dateFromSeconds = new Date(seconds * );
console.log(dateFromSeconds.toISOString());

// Convert timestamp (milliseconds) to Date
const dateFromMs = new Date(milliseconds);
console.log(dateFromMs.toUTCString());

Knowledge Base

Frequently Asked Questions

A Unix timestamp is an integer counting the number of elapsed seconds (or milliseconds) since midnight UTC on January 1, 1970 (the Unix Epoch), excluding leap seconds.
Yes. Unix time is fundamentally independent of timezones and daylight saving time. It measures an absolute instant in UTC. Timezones are only applied during human-readable formatting.
Traditional Unix/POSIX systems and many backend databases use seconds (~10 digits). Web browsers, JavaScript, and Java use milliseconds (~13 digits), providing 1,000 times higher precision.
UTC represents Coordinated Universal Time at the Greenwich meridian (longitude 0°). Your local time reflects your operating system's geographic timezone offset and any active Daylight Saving Time (DST).
Yes. Timestamps before January 1, 1970 are represented by negative numbers. For example, -86400 corresponds to December 31, 1969, 00:00:00 UTC.
Legacy systems storing Unix time in 32-bit signed integers will overflow at 2,147,483,647 seconds on January 19, 2038. ToolPorta and modern 64-bit platforms handle timestamps far beyond this boundary without issue.
Never. All timestamp transformations and date parsing execute entirely in your local browser using client-side JavaScript.
View all tools (15)