Timestamp Converter

What a Unix Timestamp Is

A Unix timestamp is the number of seconds since 1 January 1970 00:00:00 UTC - the count itself, not a formatted date. Paste one into the converter and you get the date and time back; paste a date and you get the number to put in an API, a database column or a log line. The tool handles seconds and milliseconds, so a 10-digit value like 1747488000 and a 13-digit value like 1747488000000 both resolve to the same moment, and it shows the result in your own local time as well as UTC.

To work out what a timestamp means in a different time zone, use the time zone converter, and to turn a timestamp into a date offset you can count in days, the date calculator handles date arithmetic.

Unix Timestamp Basics

A Unix timestamp represents the number of seconds that have elapsed since January 1, 1970 00:00:00 UTC, commonly known as the Unix epoch. This epoch was chosen as a convenient round number to mark the start of the Unix era. Before this date, timestamps are represented as negative numbers, while dates after the epoch use positive values.

The Unix timestamp system was developed in the early 1970s as part of the Unix operating system design. Its simplicity—storing time as a single integer—made it efficient for computing and comparing dates. Unlike date strings that require parsing, timestamps can be compared mathematically with ease. This universal format became the standard for APIs, databases, and programming languages worldwide.

Timestamp Formats Explained

Timestamps come in two primary formats: seconds and milliseconds. JavaScript's Date.now() returns milliseconds (13 digits like 1747488000000), while Python's time.time() and Go's time.Now().Unix() return seconds (10 digits like 1747488000). Most Unix systems and APIs use seconds by default, while languages designed for web development typically use milliseconds.

When converting between formats, multiply or divide by 1000 accordingly. Most modern APIs accept both formats, but always verify the documentation for your specific use case.

Frequently Asked Questions

What is the Unix epoch?

The Unix epoch is January 1, 1970 00:00:00 UTC. All Unix timestamps are measured as seconds elapsed from this point.

Why do some timestamps have 13 digits?

Timestamps with 13 digits are in milliseconds (like JavaScript uses). Those with 10 digits are in seconds (like Python uses). Multiply milliseconds by 1000 to convert to seconds.

Can timestamps represent dates before 1970?

Yes, negative timestamps represent dates before the Unix epoch. For example, -86400 represents December 31, 1969.

What happens in 2038?

Older 32-bit systems cannot represent timestamps beyond January 19, 2038 03:14:07 UTC. Modern systems use 64-bit integers, avoiding this limitation.

How do I handle timezones?

Unix timestamps are always in UTC. When displaying to users, convert to their local timezone using JavaScript's toLocaleString() or similar methods.

Are Unix timestamps the same worldwide?

Yes, timestamps are universal and timezone-independent. 1747488000 always represents the same moment: May 17, 2025 12:00:00 UTC.