DEV · Date & Time

Unix Timestamp Converter

Convert Unix timestamps like 1732769832 into readable date & time, or pick a date & time and get the Unix timestamp back. See the result in ISO 8601, local time, and UTC.

  • Convert Unix timestamp → date & time (local & UTC).
  • Convert date & time → Unix timestamp in seconds.
  • See ISO 8601 representation of the same moment.
  • All calculations happen locally in your browser. No data is sent anywhere.

Paste a Unix timestamp or pick a date & time below, then click one of the convert buttons to see all formats at once.

Unix timestamp (seconds)
This should be seconds, not milliseconds. For example, 1732769832 represents a moment in late 2024.
Date & time (local)
Your browser's timezone is used for this field. Click Use current time to quickly fill it with “now”.
All conversions run directly in your browser. Nothing is sent to any server, so your timestamps and dates stay private.

Summary

Last conversion
Waiting for input…
Enter a Unix timestamp or pick a date & time, then click one of the convert buttons.
No conversion yet
Unix timestamp (seconds)
0
Seconds since 1 Jan 1970 (Unix epoch)
ISO 8601
—
Standard ISO 8601 UTC datetime (e.g. 2024-11-28T12:30:00Z)
Local time
—
Formatted using your browser's timezone
UTC time
—
Same moment converted to UTC clock time
Unix timestamps count the number of seconds since 1 January 1970 at 00:00:00 UTC. This tool helps you jump between that integer representation and human-friendly date & time strings.

What does the Unix Timestamp Converter do?

This tool helps developers quickly move between Unix timestamps and readable date & time values. You can paste a Unix timestamp like 1732769832 and instantly see what date & time that represents in your local timezone, in UTC, and in ISO 8601 format. You can also pick a date & time and get the corresponding Unix timestamp.

What is a Unix timestamp?

A Unix timestamp is a single integer that counts the number of seconds that have passed since the Unix epoch: 1 January 1970, 00:00:00 UTC. For example:

  • 0 → 1970-01-01 00:00:00 UTC
  • 946684800 → 2000-01-01 00:00:00 UTC
  • 1732769832 → a moment in late 2024

Many backends, APIs, and databases use Unix time because it is easy to store, compare, and sort, but the raw numbers are not very human-friendly.

Why this tool is useful for developers

  • Debugging backend responses. When an API returns created_at as a Unix timestamp, you can quickly see the actual date & time.
  • Generating test data. Start from a human date & time and convert it to a Unix timestamp for seeding databases or creating fixtures.
  • Comparing timezones. See how the same timestamp looks in your local time versus UTC.
  • Working across frontend & backend. Frontend devs can match what the backend stores and vice versa.

How conversions work in this tool

When you click Timestamp → Date & Time:

  • Step 1: Your timestamp (seconds) is converted to milliseconds.
  • Step 2: A JavaScript Date object is created from that value.
  • Step 3: The same moment is formatted as local time, UTC time, and ISO 8601.
  • Step 4: The local date & time field is updated so you can tweak it and convert back.

When you click Date & Time → Timestamp:

  • Step 1: The value from the date & time picker is interpreted in your local timezone.
  • Step 2: That moment is converted into milliseconds since the epoch.
  • Step 3: The milliseconds are turned into a Unix timestamp in seconds (rounded down).
  • Step 4: Local, UTC, and ISO 8601 outputs are updated to match.

Understanding the different formats

  • Unix timestamp (seconds): Integer seconds since the Unix epoch. Often used in databases and APIs.
  • ISO 8601: A standardized string representation like 2024-11-28T13:17:12Z. The Z means “UTC”.
  • Local time: The same instant shown in your current timezone, based on your browser settings.
  • UTC time: The instant shown as clock time in the UTC timezone.

Tips for working with Unix time

  • Check units. Many libraries use milliseconds while Unix timestamps are often in seconds. If your values look ~1000 times too large, you may be mixing the two.
  • Be explicit about timezone. Always clarify whether a time is local or UTC when sending/receiving data between systems.
  • Use this tool during debugging. When logs or JSON responses contain raw timestamps, paste them here to quickly see what they mean.

Use this Unix Timestamp Converter whenever you need a fast, browser-based way to translate between integer timestamps and human-friendly dates for backend, frontend, or DevOps work.