Unix Timestamp Converter
Convert between Unix timestamps and human-readable dates
Current Unix Timestamp
The current time expressed as a Unix timestamp (seconds since January 1, 1970)
Updated in real-time. Unix time counts seconds since Jan 1, 1970 UTC.
Convert Unix Timestamp to Date
Enter a Unix timestamp to convert it to a human-readable date
Category Hub
Category Essentials
Date and time queries often connect across age, differences, time zones, and countdowns. These featured pages act as strong starting points for the most common time-based calculations.
Related Tools
Daily Inspiration
The pen is mightier than the sword. - Edward Bulwer-Lytton
Unix Timestamp Converter (Epoch Time) - Convert Timestamp Date
We provide a fast and precise tool for developers to convert Unix timestamps to human-readable dates and back. Whether you're debugging an API response, validating a JWT token, or working with database time entries, our converter simplifies the process.
Convert Unix Timestamp to Date
Paste any Unix timestamp (in seconds or milliseconds) into the field below. We instantly translate that number into a clear, readable date format. We display the time in both UTC and your local timezone so you can see the difference at a glance.
Convert Date to Unix Timestamp
Need to generate a timestamp for a specific event? Use our date picker to select a precise moment. We will generate the corresponding Unix timestamp in both seconds and milliseconds for you to use in your applications.
Current Unix Timestamp (Live)
Here is the current time, continuously updated, represented as the number of seconds that have passed since the Unix Epoch (January 1st, 1970).
Current Timestamp (seconds): Live updating number
Seconds vs Milliseconds (The Most Common Mistake)
A frequent source of errors is confusing timestamps in seconds with those in milliseconds. We help you spot this issue quickly.
- 10-Digit Timestamps are typically in seconds. This is common in PHP, Python, and many database systems like PostgreSQL.
- 13-Digit Timestamps are almost always in milliseconds. This is the standard for JavaScript (
Date.now()) and Java.
If you paste a 13-digit timestamp and the resulting date is thousands of years in the future, you're treating milliseconds as seconds. To fix this, simply divide the timestamp by 1000.
UTC, Time Zones, and "Why is my result off?"
It is crucial to remember that a Unix timestamp is fundamentally based on UTC (Coordinated Universal Time). It has no inherent timezone information. If a converted date appears to be off by several hours, it's likely because you are comparing the pure UTC output to your local time. Our tool displays both UTC and your local time to help you avoid this confusion.
Common Developer Use Cases
We designed this tool with developers in mind. Here are some common scenarios where it proves invaluable:
- JavaScript
Date.now(): Converting the 13-digit millisecond output fromDate.now()into a standard 10-digit timestamp for API calls. - JWT Expiration (
exp): Verifying the expiration time of a JSON Web Token. Theexpandiat(issued at) claims are defined as NumericDate, which is a standard Unix timestamp in seconds. - PostgreSQL Timestamps: Quickly converting a human-readable date into an epoch integer for
WHEREclauses or converting a retrieved epoch value back into a date for reports, similar to usingextract(epoch from your_timestamp_column).
Troubleshooting
- My converted date is off by a few hours. This is almost always a UTC vs. local time issue. A Unix timestamp is a fixed point in time, but its representation on a clock depends on the timezone.
- My timestamp is converting to a date in the distant future. You are likely using a 13-digit millisecond timestamp. Divide it by 1000 to get the correct value in seconds before converting.
- Why do dates after 2038 look wrong? You're seeing the Year 2038 problem. Legacy systems using a 32-bit signed integer to store the timestamp will run out of space on January 19, 2038, causing the value to wrap around to the year 1901. Modern 64-bit systems do not have this limitation.
Frequently Asked Questions
What is a Unix timestamp (epoch time)?
It's the total number of seconds that have passed since January 1, 1970, at 00:00:00 UTC.
Is Unix time in UTC or my local timezone?
Unix time itself is always in UTC. The human-readable date it represents can be displayed in any timezone, but the underlying integer value is constant.
Are Unix timestamps in seconds or milliseconds?
The original standard is seconds (a 10-digit number). However, milliseconds (a 13-digit number) are widely used, especially in JavaScript.
How do I convert a 13-digit timestamp to seconds?
Simply divide the 13-digit millisecond timestamp by 1000.
Does Unix time include leap seconds?
No, the POSIX standard explicitly omits leap seconds from the count.
What format does JavaScript Date.now() return?
It returns a 13-digit timestamp representing the number of milliseconds since the Unix Epoch.
What format are JWT exp/iat claims?
They are defined as a NumericDate, which is a standard 10-digit Unix timestamp in seconds.
What is the Year 2038 problem?
It is a bug that affects systems using 32-bit signed integers to store Unix time. On January 19, 2038, the integer will overflow, causing the time to wrap around to December 1901, which can cause system failures.
Can I convert timestamps before 1970?
Yes. Our tool supports negative timestamps, which represent dates and times before the epoch on January 1, 1970.
Why do different converters show different results?
This is typically due to one of two reasons: one tool is displaying UTC time while another is showing local time, or one is incorrectly interpreting a millisecond timestamp as seconds.
