Skip to main content
Skip to tool

Converter

Unix Timestamp Converter — Epoch, ISO & Time Zones

Convert Unix seconds and milliseconds to UTC, local, and IANA zones. ISO-8601, RFC 2822, Excel serial, Discord snowflakes, and batch convert — privately in your browser.
  • Convert
  • Mobile Friendly
  • Accessibility Tested
  • SEO Optimized
  • Fast Loading
  • Responsive

Version 1.0.0 · Last reviewed

How it worksShow guide

Introduction

Unix time counts seconds (or milliseconds) since 1970-01-01 00:00:00 UTC. This converter auto-detects 10-digit seconds vs 13-digit milliseconds, 17–20 digit Discord snowflakes, formats the instant in UTC and a chosen IANA zone, and can batch-convert one value per line. Hex seconds, ISO week, weekday, and Excel serial are included. Nothing is sent to a server.

Step-by-step

  1. Paste a Unix timestamp, ISO-8601 string, or Discord snowflake — or pick a date
  2. Choose an IANA time zone and optional 12-hour display
  3. Copy seconds, milliseconds, ISO, RFC 2822, or all formats at once

Worked example

1577836800 seconds is 2020-01-01 00:00:00 UTC. In Asia/Kolkata that instant is 05:30 the same morning. Hex seconds are 0x5e0be100.

Use cases

  • Decode log timestamps from APIs and databases
  • Build ISO-8601 strings for a specific time zone
  • Convert a spreadsheet column of epoch values in one paste
  • Turn a Discord message id into a UTC time

Frequently asked questions

Seconds or milliseconds?

Values around 10 digits are treated as seconds; around 13 digits as milliseconds. Mixed units are the usual source of “47 years off” bugs.

What is a Discord snowflake?

A 17–20 digit id that encodes a millisecond timestamp. This tool uses (id ≫ 22) + 1_420_070_400_000, Discord’s 2015-01-01 epoch. It does not call Discord’s API.

What is the Excel serial?

The spreadsheet day-number used by Excel’s 1900 date system (day 1 = 1899-12-31 in Excel’s leap-year bug convention; this converter uses the Unix-based 25569 offset). Good for checks, not for 1900-era worksheets.

Is Unix time timezone-aware?

The epoch itself is UTC. Displaying it in New York or Kolkata is a formatting choice — the underlying instant does not change.

Does this handle leap seconds?

JavaScript Date ignores leap seconds, like most application clocks. Do not use this for legal UTC-SLS or astronomical work.

Why can DST dates look wrong?

Converting a local civil time into an instant near a daylight-saving fold can be ambiguous. Prefer UTC or ISO strings with an offset when precision matters.

Related tools

Popular tools

Was this helpful?

Your feedback stays on this device only — it is not sent to the Bestrao team yet.

Share

Provided by Bestrao

Version 1.0.0 · Last updated: