Timestamp guide

Convert a Unix timestamp to a date

A Unix timestamp is compact and useful for machines, but a readable date is faster when you are debugging logs, API responses, and database rows.

Open Timestamp Converter View all tools

What the number means

Unix timestamps count time from January 1, 1970 UTC. The number may be stored in seconds or milliseconds depending on the system that produced it.

Example

Input

1715200000

Output

A readable local date, UTC date, ISO string, Unix seconds, and Unix milliseconds.

How to convert it

Paste the timestamp into the timestamp converter.
Select seconds or milliseconds based on the value length.
Compare the local time with the UTC or ISO output before using it in a report.

Local time and UTC

A timestamp represents one moment. The local date is convenient for reading, but UTC is usually better when you are comparing logs across servers, teams, or timezones.

If you paste a date into a bug report, include the ISO UTC value. It removes the guesswork around daylight saving time and local machine settings.

Common mistakes

Ignoring timezone when comparing dates from logs
Copying a duration value and treating it as an absolute timestamp
Using milliseconds in a seconds-only API field
Rounding a timestamp before checking whether precision matters

FAQ

What timezone is a Unix timestamp in?

The timestamp itself is based on UTC. The displayed local date depends on your browser's timezone.

Can the same timestamp show different local times?

Yes. People in different timezones can see different local dates for the same UTC instant.

Should I use ISO time in bug reports?

Yes. ISO UTC output is usually clearer than a local-only date when sharing logs with other people.