Unix timestamp converter

Unix timestamp converter: epoch seconds, milliseconds, microseconds or nanoseconds to an ISO 8601 UTC date and local time, and dates back to epoch time.

Atualizado Exemplos verificados: 8

Digits (optionally negative or with a decimal part), an ISO 8601 date-time such as 2026-01-15T09:00:00Z, or “now”.
Experimentar
ISO 8601 (UTC)
2026-09-29T05:10:36.154Z
ISO 8601 (UTC): 2026-09-29T05:10:36.154Z
Local time in the chosen zone
2026-09-29 05:10:36.154 (UTC+00:00)
Unix seconds
1790658636.154
Milliseconds
1790658636154
Microseconds
1790658636154000
Nanoseconds
1790658636154000000
Day of the week (UTC)
Tuesday
Read as
current time
Relative to now
Now

Unix time 1790658636.154 is 2026-09-29T05:10:36.154Z, a Tuesday, which is the current time.

Where this instant sits

20,725 days from the epoch: 1 Jan 1970 to 29 Sep 202620,725 days from the epochEpoch1970-01-01T00:00ZThis timestamp2026-09-29T05:10:36.154ZNow29 Sep 2026
Como é calculado S
  1. Days and seconds since the epoch

    1790658636=86400×20725+186361790658636 = 86400 \times 20725 + 18636

    Unix time ignores leap seconds: every day has exactly 86,400 seconds.

  2. Day number to calendar date

    Day 20725 after 1 January 1970 is Tue 29 Sep 2026; 18636 s after midnight is 05:10:36 UTC.

  3. Shift to the chosen zone

    UTC is UTC+00:00 at that instant, so the local time is 2026-09-29 05:10:36.154 (Tue 29 Sep 2026).

Sobre Unix timestamp converter

A Unix timestamp counts the seconds since 00:00:00 UTC on 1 January 1970, the Unix epoch, with every day counted as exactly 86,400 seconds. The converter splits the count into whole days and seconds of the day, turns the day number into a calendar date, then applies the chosen zone's offset from the IANA time zone database. Date to timestamp runs the same steps backwards.

Developers use it to read log lines, database columns and API fields. With the unit left on automatic, up to 11 digits are read as seconds, 12 to 14 as milliseconds, 15 to 17 as microseconds and 18 or more as nanoseconds, so 1700000000000 is read as milliseconds: 22:13:20 UTC on 14 November 2023.

Results cover the years 0001 to 9999, the range of a four-digit ISO 8601 year. Negative timestamps are instants before 1970; −86400 is midnight UTC on 31 December 1969.

Exemplos resolvidos

The epoch

Conversões
Timestamp to date
Timestamp
0
Timestamp unit
Seconds
Time zone
UTC
ISO 8601 (UTC)
1970-01-01T00:00:00Z
Day of the week (UTC)
Thursday

Fonte de verificação: POSIX definition; Python datetime.fromtimestamp(0, timezone.utc)

Largest signed 32-bit value (year 2038)

Conversões
Timestamp to date
Timestamp
2147483647
Timestamp unit
Detect from length
Time zone
UTC
ISO 8601 (UTC)
2038-01-19T03:14:07Z
Read as
seconds

Fonte de verificação: Python 3.8: datetime.fromtimestamp(2147483647, timezone.utc)

Milliseconds shown in India

Conversões
Timestamp to date
Timestamp
1700000000000
Timestamp unit
Detect from length
Time zone
India (Kolkata)
ISO 8601 (UTC)
2023-11-14T22:13:20Z
Local time in the chosen zone
2023-11-15 03:43:20 (UTC+05:30)
Unix seconds
1700000000
Read as
milliseconds

Fonte de verificação: Python 3.8: datetime.fromtimestamp(1700000000, tz=Asia/Kolkata) = 2023-11-15 03:43:20+05:30

Negative timestamp

Conversões
Timestamp to date
Timestamp
-86400
Timestamp unit
Seconds
Time zone
UTC
ISO 8601 (UTC)
1969-12-31T00:00:00Z
Day of the week (UTC)
Wednesday

Fonte de verificação: Python 3.8: datetime.fromtimestamp(-86400, timezone.utc)

Perguntas

What is the year 2038 problem?

Software that stores Unix time in a signed 32-bit integer can count only to 2,147,483,647 seconds, reached at 03:14:07 UTC on 19 January 2038. One second later the value wraps to −2,147,483,648, which reads as 20:45:52 UTC on 13 December 1901. A signed 64-bit count, the usual size on current 64-bit systems, lasts about 292 billion years.

How can I tell whether a timestamp is in seconds or milliseconds?

Count the digits. Present-day times have 10 digits in seconds, 13 in milliseconds, 16 in microseconds and 19 in nanoseconds; the seconds count reached 1,000,000,000 on 9 September 2001 and stays at 10 digits until 20 November 2286. JavaScript's Date.now() and Java's System.currentTimeMillis() return milliseconds, while the shell command date +%s and Python's time.time() return seconds.

Does Unix time count leap seconds?

No. POSIX defines every day as 86,400 seconds, so the 27 leap seconds added to UTC between 1972 and 2016 have no timestamps of their own, and 23:59:60 cannot be written as Unix time. Systems either repeat a second when one occurs or spread it out; Google, for example, smears a leap second over the 24 hours from noon to noon UTC.

Is a Unix timestamp the same in every time zone?

Yes. A timestamp names one instant, and the zone only changes how that instant is written. Timestamp 0 is 00:00 UTC on 1 January 1970, which was 05:30 the same day in India, 19:00 on 31 December 1969 in New York, and 01:00 in London, where British Standard Time kept clocks on UTC+01:00 all year from 1968 to 1971.

How do I get the current Unix timestamp?

Type now in the timestamp box, or ask the system clock: date +%s in a Linux or macOS shell, Math.floor(Date.now() / 1000) in JavaScript, int(time.time()) in Python, and SELECT UNIX_TIMESTAMP() in MySQL. The count grows by 86,400 a day and passes 1,800,000,000 at 08:00 UTC on 15 January 2027.

Qual é a precisão de “Unix timestamp converter”?

A precisão depende dos dados inseridos e das hipóteses do método. O cálculo decimal usa 50 algarismos significativos, mas estimativas, métodos numéricos e dados de origem podem ter menor precisão; o arredondamento exibido não elimina essas limitações. Exemplos resolvidos verificados com fontes independentes: 8. Por exemplo, “The epoch” é verificado com POSIX definition; Python datetime.fromtimestamp(0, timezone.utc).

De onde vem o método?

POSIX.1-2017, §4.16 Seconds Since the Epoch; ISO 8601-1:2019 — Date and time representations; IANA Time Zone Database.

Sobre esta calculadora

t=86400×N(date)+3600h+60m+s,N=days since 1970-01-01t = 86400 \times N(\text{date}) + 3600h + 60m + s,\qquad N = \text{days since 1970-01-01}

Fontes

  1. POSIX.1-2017, §4.16 Seconds Since the Epoch
  2. ISO 8601-1:2019 — Date and time representations
  3. IANA Time Zone Database

Verificado com as referências

Esta calculadora inclui 8 exemplos resolvidos com respostas de fontes independentes. Eles fazem parte do conjunto de testes e você também pode executá-los aqui.

Calculadoras relacionadas