← Back to Tools

Timestamp Converter

Convert between Unix timestamps and dates.

How to use the Timestamp Converter

Unix timestamps are used by databases, APIs, and programming languages to represent dates as a single integer. This tool converts them to human-readable dates and back — in one click.

  1. 1

    Convert a timestamp to a date

    Type a Unix timestamp (e.g. 1700000000) into the top field and click "Convert to Date." The ISO date string and full local date appear in the result area.

  2. 2

    Convert a date to a timestamp

    Enter an ISO date string (e.g. 2024-11-14T22:13:20.000Z) into the second field and click "Convert to Timestamp" to get the Unix epoch value in seconds.

  3. 3

    Use Current Time

    Click "Use Current Time" to load the current Unix timestamp and convert it instantly — useful for quickly checking what the current epoch time is.

Frequently asked questions

What is a Unix timestamp?

A Unix timestamp is the number of seconds elapsed since January 1, 1970, 00:00:00 UTC — the "Unix epoch." It is timezone-independent, making it the universal standard for storing dates in databases, log files, and APIs.

Why does Unix time start at January 1, 1970?

That date was chosen as an arbitrary starting point when Unix was created in the late 1960s and early 1970s. It is close to when the system was developed, and the choice has simply persisted across all computing systems ever since.

Are timestamps in seconds or milliseconds?

It depends on the system. Unix timestamps are traditionally in seconds, but JavaScript's Date.now() returns milliseconds. A 10-digit number is almost certainly seconds; a 13-digit number is milliseconds. Divide by 1000 to convert milliseconds to seconds.

Can timestamps represent dates before 1970?

Yes — negative timestamps represent dates before the epoch. For example, -86400 is December 31, 1969, 00:00:00 UTC (one day before the epoch).

How are timestamps stored in databases?

Most SQL databases have TIMESTAMP or DATETIME column types. Some NoSQL stores or REST APIs return raw Unix integers. Always document whether your timestamps are in seconds or milliseconds to prevent off-by-1000 bugs.