Negative Unix timestamps and dates before 1970

Short answer

A negative timestamp represents an instant before the Unix epoch. The minus sign does not mean the value is corrupt; it measures backward from 1970-01-01 00:00:00 UTC.

Exact examples

The arithmetic is symmetric around zero. In milliseconds, the second before the epoch is -1000; the millisecond immediately before it is -1.

Why some systems reject them

Unix time is a model, but each database, language, or protocol chooses its range. An unsigned field cannot store negatives. Older libraries and 32-bit integer formats may impose narrower boundaries. A user interface may also limit years even when its internal type could represent more.

Separate two questions:

1. Does the date have a mathematically valid timestamp?
2. Does the destination support that value and range?

The Unix timestamp converter supports pre-1970 dates within its documented range and checks integer scaling before creating a date object.

Historical calendars

Converting a very old date does not prove that people in that place used the same civil calendar notation at the time. Modern APIs commonly extend the Gregorian calendar backward uniformly. That is useful for technical arithmetic, while historical research may require local calendar transitions.

Recommended boundary checks

• Preserve the sign through serialization and transport.
• Declare seconds or milliseconds.
• Test -1, 0, and 1 at the epoch boundary.
• Verify the destination storage range.
• Display the resulting UTC date as a sanity check.

Primary source

The ECMAScript time value specification defines the epoch, milliseconds, and days before it through negative values.