The timezone is part of the input

A date string without an offset is ambiguous. 2025-11-16 09:00:00 in Shanghai is 1763254800; in New York it is 1763298000. The converter applies the timezone you select, so the resulting number corresponds to a specific instant, not a floating wall clock.

This page takes a local date and time. If you already have an ISO 8601 string with Z or an offset, use the timestamp converter page, which parses the offset directly.

Seconds or milliseconds?

Most APIs accept seconds; JavaScript and some Java APIs expect milliseconds. The converter shows both, with the 13-digit form ready to paste into new Date(...) or Date.now()-style code.

  • Database timestamp / datetime columns usually take seconds or a formatted string, not milliseconds.
  • JWT iat and exp claims are seconds; passing milliseconds makes the token valid for millennia.
  • OpenAPI format: int64 often means milliseconds; check the schema rather than guessing.

Dates before 1970

Negative timestamps are valid: 1969-12-31T23:59:59Z is -1. Some databases and languages handle them inconsistently — MySQL's TIMESTAMP type cannot store them, while DATETIME and PostgreSQL's timestamp can.

If your input has no time and no zone, the converter assumes midnight in the selected timezone. Midnight does not always exist on DST transition days.