What is a Unix timestamp?
From the epoch to its units

What a Unix timestamp means

A Unix timestamp expresses how far one instant lies from a fixed reference point. That reference is 1970-01-01 00:00:00 UTC, commonly called the Unix epoch.

When the unit is seconds, the epoch is 0, one second later is 1, and one day later is 86400. A continuous number is easier to sort and compare across regions than separate year, month, day, hour and minute fields.

Why the epoch begins on January 1, 1970

The date is not the beginning of time in a scientific sense. It is a conventional origin chosen for Unix-family timekeeping. Once one origin is fixed, later instants can be positive and earlier instants negative.

The year 1970 is therefore a starting value, not an absolute limit on representable dates. If the numeric and calendar ranges are wide enough, values can describe both dates before 1970 and dates far into the future. For example, -31536000 seconds moves roughly one common year before the epoch.

Epoch versus timestamp

The epoch is the origin; a timestamp is a measured value from that origin. “The Unix epoch is 1970-01-01 UTC” and “this event has timestamp 1704067200” describe different things.

Seconds, milliseconds, microseconds and nanoseconds

Unix time is not always stored in seconds. Systems that need shorter intervals use milliseconds, microseconds or nanoseconds. Without the unit, the same digits can point to a completely different calendar date.

Digit length is only a clue

Positive values near the present are often 10 digits in seconds, 13 in milliseconds, 16 in microseconds and 19 in nanoseconds. Historical dates, distant future dates, leading zeros, negative signs and fractional values can fall outside that pattern. Prefer the source documentation, then verify that the converted date is plausible.

A Unix value does not contain a time zone

The value represents an instant relative to UTC, but it does not store a region such as Korea or New York. Displaying 1704067200 in UTC gives midnight on January 1, 2024; displaying the same value in Korea gives 9:00 a.m. that day.

“Convert a timestamp to KST” therefore means showing the same instant on a Korean clock, not moving the event to a different moment. The underlying Unix value remains unchanged.

Fixed offsets and regional zones

Korea Standard Time is currently UTC+09:00 all year. Regions with seasonal changes cannot be handled accurately for all dates by adding one fixed number of hours. Their historical and future rules must be looked up for the date in question.

Fractional seconds and precision

Intervals shorter than one second can be written as a fraction. 1704067200.5 seconds is 500 milliseconds after 2024-01-01 00:00:00 UTC. The same value is 1704067200500 milliseconds.

Changing the unit does not make the source measurement more accurate. Multiplying an integer seconds value by 1,000 creates a millisecond-shaped number, but the three new zeros do not prove that the original clock measured milliseconds. Keep measurement precision separate from display unit.

Handling nanoseconds

Nanosecond values are long enough that ordinary number formats can round their final digits. Preserve the original as an integer string when exact comparison matters, and check how many fractional digits remain in the human-readable date.

Negative time and leap seconds

Negative values identify pre-epoch instants

-1 second is 1969-12-31 23:59:59 UTC. In Korea that same instant is already 1970-01-01 08:59:59, so the sign alone does not determine the local calendar year.

Conventional Unix time does not count leap seconds separately

POSIX-style Unix time does not assign an ordinary additional Unix second to the rare UTC display 23:59:60. This distinction matters when treating the subtraction of two timestamps as a very long physical elapsed-time measurement.

What is the Year 2038 problem?

A signed 32-bit integer can store Unix seconds only through 2147483647. That value is 2038-01-19 03:14:07 UTC; one additional second cannot fit in the same signed format.

This does not mean Unix time ends in 2038. It is a storage-width limitation. A wider signed integer can continue representing later dates.

If a file or tool may hold contract dates, birthdays or long-lived schedules after 2038, confirm that it supports a wider range.

Unix time compared with ISO 8601

A Unix value is compact and easy to sort, but people cannot identify its date by sight and may omit its unit. An ISO 8601 date is longer but can include the calendar, clock and UTC offset.

For an important instant, a safe record includes the UTC ISO form, the original Unix value and its unit: 2024-01-01T00:00:00Z (1704067200 seconds).

A checklist for preventing the wrong date

1. Find the numeric unit. Look for s, ms, μs or ns in the source documentation.
2. Compare UTC and the intended local zone. Check whether an offset crosses midnight.
3. Check the expected digit range. Present-day seconds are usually 10 digits and milliseconds 13.
4. Preserve fractions and signs. Removing them identifies a different instant.
5. Include a time zone when sharing. Provide a date with Z or a numeric offset.

Authoritative references and further reading

• The Open Group: POSIX time and leap seconds
• RFC Editor: internet date and time format
• IANA: world time-zone rules
• MDN: representable calendar range
• MDN: UTC ISO string format

Regional time-zone rules can change through government policy. For historical dates or future local schedules, confirm the IANA rule that applies on the relevant date.

Try the concepts in a converter

Unix timestamp questions