Timestamp Converter

What is the Timestamp Converter?

A Unix timestamp (or epoch time) counts the seconds that have elapsed since 00:00:00 UTC on 1 January 1970, ignoring leap seconds. Databases, log files, JWT claims and APIs use it because a single integer is unambiguous, timezone-independent and easy to compare and sort.

Humans prefer calendar dates, so converting is a daily task for developers. The main trap is units: many systems use seconds (10 digits today, such as 1790000000), while JavaScript and Java use milliseconds (13 digits). This converter detects the unit from the magnitude and shows the result in UTC, your local timezone and ISO 8601 format.

When to use the Timestamp Converter

Use it to make sense of log entries, database columns and API fields stored as epoch values, to compute when a token or cache entry will expire, to schedule jobs at an exact moment, and to double-check timezone handling between servers in different regions. It is also useful when comparing events recorded by different systems: converting everything to UTC removes confusion about offsets and daylight saving changes, so you can see which event really happened first.

How to use the Timestamp Converter

1. Paste a Unix timestamp to convert it to a date, or use the date picker to produce a timestamp.
2. Let the unit auto-detect, or force seconds or milliseconds.
3. Pick the timezone you want to display: UTC, your local time, or another zone.
4. Read the formatted date, ISO 8601 string and relative time (for example "3 days ago").
5. Press Now to load the current timestamp for quick comparisons.

Examples

1790000000        (seconds)
UTC:             2026-09-21T14:13:20Z
ISO 8601:        2026-09-21T14:13:20.000Z

1790000000000    (milliseconds)
Same instant:    2026-09-21T14:13:20.000Z

2026-10-02T00:00:00Z  ->  1790899200

In JavaScript: Math.floor(Date.now() / 1000) returns the current timestamp in seconds, and new Date(ts * 1000) converts it back.

Common errors and tips

• If a converted date lands in 1970, you passed seconds where milliseconds were expected, or the reverse put it in the far future.
• Store and transmit timestamps in UTC; convert to local time only when displaying.
• Daylight saving time makes local days 23 or 25 hours long, so never add 86400 seconds to move to "tomorrow" in local time.
• 32-bit signed timestamps overflow on 19 January 2038; use 64-bit integers.
• ISO 8601 strings with a trailing Z are UTC; an offset such as +02:00 is not.

Privacy: runs entirely in your browser

Conversions use your browser's own date functions and timezone data, so nothing you enter is sent anywhere. This tool runs entirely in your browser: nothing you enter is uploaded, stored or logged on our servers, and it keeps working even if you go offline after the page has loaded.