Timestamp Converter

Convert Unix timestamps to human dates and vice versa. Multi-timezone.

Timestamp → Date

seconds or milliseconds
ISO 8601 2026-07-28T13:02:40.000Z
UTC Tue, 28 Jul 2026 13:02:40 GMT
Local 7/28/2026, 1:02:40 PM
Relative 0s ago
Unix (s) 1785243760
Unix (ms) 1785243760000
2026Year
7Month
28Day
13Hour
2Min
40Sec

Date → Timestamp

About the Timestamp Converter

Convert between Unix timestamps and human-readable dates in both directions. A Unix timestamp counts seconds since 1 January 1970 UTC, which is compact for storage but unreadable at a glance. This tool shows any timestamp as UTC, ISO 8601, your local time and a relative description, and converts a chosen date back into epoch form.

How to use the Timestamp Converter

  1. Enter a timestamp or a date

    Paste a Unix timestamp in seconds or milliseconds, or pick a date and time to convert in the opposite direction.

  2. Read every representation

    The result is shown simultaneously as UTC, ISO 8601, your browser local time, and a relative description such as "3 hours ago".

  3. Copy the format you need

    Copy whichever representation your database, log query or API call expects.

When to use it

Reading log timestamps

Turn an epoch value in a log line into a readable date to correlate it with an incident.

Debugging token expiry

Convert a JWT exp claim to a real date to confirm whether a token has actually expired.

Writing database queries

Get the epoch value for a specific date boundary to use in a range filter.

Frequently asked questions

Is my timestamp in seconds or milliseconds?

A 10-digit value is seconds; a 13-digit value is milliseconds. Unix time is defined in seconds, but JavaScript Date.now() returns milliseconds, which is where most conversion mistakes come from.

What is ISO 8601?

An international standard date format, such as 2026-07-24T18:30:00Z. It sorts correctly as a string and is unambiguous about time zone, which is why most APIs prefer it.

Why does the local time differ from UTC?

Local time applies your browser time zone offset and daylight saving rules. The underlying instant is identical — only the presentation differs.

What is the year 2038 problem?

Systems storing Unix time in a signed 32-bit integer overflow on 19 January 2038. Modern platforms use 64-bit values, but legacy systems and embedded devices can still be affected.