Unix Timestamp Converter

Turn epoch numbers from logs, databases and APIs into dates you can read, and dates into timestamps. Seconds, milliseconds and microseconds are detected automatically.

  • Files stay on your device
  • Free, no sign-up
  • Instant
Current Unix time—
Quick guide · 4 steps

How to use the Unix Timestamp Converter

When to use the Unix Timestamp Converter

Reading logs

Turn epoch times in server logs into dates you can understand.

Debugging APIs

Check created_at and expires values in API responses.

Database work

Convert stored timestamps to dates, or dates to values for queries.

Scheduling

Create a timestamp for a future moment, such as a token expiry.

Features and benefits

  • Auto-detects seconds, milliseconds and microseconds
  • ISO 8601, UTC, RFC 2822 and local time
  • Relative time (“3 days ago”)
  • Live current Unix time with one-click copy

Example

Input
1735689600
Output
2025-01-01T00:00:00.000Z · Wed, 01 Jan 2025 00:00:00 GMT

How the Unix Timestamp Converter works

If you enter a number, ConvertNest decides its unit by size: up to 11 digits is treated as seconds, up to 14 as milliseconds, and longer as microseconds. Anything else is read by the browser’s date parser, which understands ISO 8601 and most common date formats. The resulting moment is then formatted in UTC, ISO 8601, RFC 2822 and your device’s time zone, with a relative description such as “in 3 days”.

A real-life example

A support engineer sees “expires_at: 1767225600” in a customer’s API response and the customer insists the subscription should still be active. Converting it shows 1 January 2026, 00:00 UTC – which was 5:00 in the morning in Karachi, the customer’s city. The subscription expired at midnight UTC, not local midnight, which explains the confusion.

Good to know

Unix time counts the seconds since 00:00:00 UTC on 1 January 1970 (the “epoch”). It is how most computers store moments in time, because a single number is easy to compare and does not depend on time zones.

JavaScript and many APIs use milliseconds (13 digits today), databases and Unix tools usually use seconds (10 digits), and some systems use microseconds (16 digits). The converter decides which one you mean from the size of the number.

Timestamps are always UTC. The “your time” row converts to your device’s time zone and daylight-saving rules, which is why two people in different countries see different local times for the same timestamp.

Tips for the best results

  1. Remember timestamps are always UTC.
  2. Use ISO 8601 (2026-01-01T12:00:00Z) when typing dates to avoid ambiguity.
  3. Count the digits: 10 = seconds, 13 = milliseconds.
  4. Use “Use current time” to grab a timestamp for testing.

Common mistakes to avoid

Mixing seconds and milliseconds

A seconds value read as milliseconds lands in January 1970.

Forgetting time zones

A date typed without a zone is read in your local time.

Using day/month order ambiguously

Write dates as YYYY-MM-DD to avoid 03/04 confusion.

Unix Timestamp Converter – frequently asked questions

What is the current Unix timestamp?

It is shown live at the top of the tool.

What happens in 2038?

Systems that store Unix time in a signed 32-bit number overflow on 19 January 2038. Modern systems use 64-bit numbers and are not affected.

Can I convert a date to a timestamp?

Yes. Type a date like 2026-03-15 14:30 and read the Unix seconds and milliseconds.

Which time zone is used for typed dates?

Dates without a zone are read in your local time zone. Add Z (UTC) or +05:00 to be explicit.

What is the epoch?

00:00:00 UTC on 1 January 1970, the starting point of Unix time.

Are leap seconds counted?

No. Unix time ignores leap seconds, as JavaScript does.

Why do I see a date in 1970?

The number was probably in seconds but read as milliseconds, or it was zero. Check the number of digits.