Inputs
1. Timestamp to Date
Local Time: -
GMT/UTC: -
2. Date to Timestamp
Epoch Timestamp: -
Results

How It Works

Unix Time (Epoch) represents seconds elapsed since January 1, 1970 (00:00:00 UTC). The converter shifts scales by translating timestamps to milliseconds ($Time_{ms} = Epoch_{sec} \times 1000$) and loading them into Javascript Date models to output local and UTC string values.

Formula Used

Epoch Seconds = Milliseconds / 1000
Unix Epoch time measures the seconds elapsed since 00:00:00 UTC on January 1, 1970. To convert a JavaScript timestamp (which is in milliseconds) to epoch seconds, we divide by 1000.
Date Time = Epoch Milliseconds after 1970-01-01T00:00:00Z
To translate epoch seconds to calendar date-time, the value is scaled to milliseconds and mapped to the standard UTC timeline to extract calendar years, months, and hours.

Worked Example

Here is a step-by-step example of how these values are calculated:

Timestamp 1773000000
Result: Converted Output Date: `Sat Mar 07 2026` in UTC timezone.

Frequently Asked Questions

What is the difference between seconds and milliseconds timestamps?
Standard Unix epoch timestamps are measured in **seconds** (typically a 10-digit number like `1773000000`). JavaScript APIs and web logs often use **milliseconds** (a 13-digit number like `1773000000000`). Divide milliseconds by 1000 to convert to seconds.
What happens in the year 2038?
The Year 2038 problem (Y2K38) affects 32-bit signed integer storage systems, which cap out at timestamp `2147483647` (January 19, 2038). Modern browsers use 64-bit float numbers, avoiding this limitation.