Skip to content
Butter Tools Logo
Butter Tools

Unix Timestamp Converter

Convert epoch seconds / milliseconds to a human date and back, in UTC or your local time zone.

Current Unix time

Timestamp → Date

Date → Timestamp

Accepts ISO 8601, "YYYY-MM-DD HH:mm:ss", or anything Date can parse.

Unix Timestamp Converter Examples

Click any card to try
menu_book

How to Use Unix Timestamp Converter

To convert a Unix timestamp to a human-readable date, paste the timestamp into the top field, select whether it is in seconds or milliseconds, and the tool instantly displays the corresponding date and time in both UTC and your local timezone. The current Unix timestamp is shown live and updates every second.

To convert a date to a Unix timestamp, enter the date and time in the bottom section and the tool calculates the corresponding Unix timestamp in seconds and milliseconds. This converter is essential for developers debugging API responses, log files, and database records that store times as Unix timestamps.

help

Frequently Asked Questions

What is a Unix timestamp? expand_more

A Unix timestamp is the number of seconds (or milliseconds) elapsed since the Unix epoch: midnight on January 1, 1970, UTC. It is used universally in computing to represent moments in time as a single integer.

What is the current Unix timestamp? expand_more

The current Unix timestamp changes every second. In May 2026 it is approximately 1,747,700,000 seconds. Use the live counter on this page to see the exact current value.

What is the difference between seconds and milliseconds timestamps? expand_more

Standard Unix timestamps use seconds. JavaScript's Date.now() and many APIs return milliseconds (1000 times larger). A 10-digit number is typically seconds; a 13-digit number is typically milliseconds.

What date does Unix timestamp 0 represent? expand_more

Unix timestamp 0 represents January 1, 1970, at 00:00:00 UTC, known as the Unix epoch. All Unix timestamps are relative to this point in time.

What is the Unix timestamp for the year 2038 problem? expand_more

The Year 2038 problem affects 32-bit systems where Unix time overflows on January 19, 2038, at timestamp 2,147,483,647. 64-bit systems extend this limit billions of years into the future.