Date to Unix Timestamp

Turn any date and time into epoch seconds and milliseconds.

Date & time → Unix timestamp

How it works

  1. Wall-clock input (a date, an optional time, and a zone) is resolved to the exact UTC instant it denotes in that zone, including the daylight-saving offset in effect on that date.
  2. The instant is stored internally as milliseconds since the epoch; the seconds value is that number floored at 1000ths, so it stays consistent for pre-1970 dates too.
  3. A missing time is treated as midnight (00:00) in the selected zone, the same interpretation most databases apply to date-only values.

Good to know

  • Choose UTC in the zone picker when you want a zone-independent result that does not depend on where the input was recorded.
  • Times that do not exist (spring-forward gaps) or occur twice (fall-back overlaps) are detected and labeled; the tool never silently picks an offset.
  • Dates before 1970 produce negative timestamps; the full JavaScript Date range (±8.64×10¹⁵ ms) is supported.

Frequently asked questions

Is my input interpreted as UTC or local time?
You choose. Wall-clock input needs a zone to identify a real instant: 09:00 in New York and 09:00 in Tokyo are six hours apart in absolute time. UTC gives a stable, predictable result.
What if I enter a date without a time?
The time defaults to 00:00 (midnight) in the zone you selected, which is exactly how most databases and APIs interpret date-only values.
Can I convert dates before 1970?
Yes. Timestamps before the epoch are negative numbers, and this tool supports them. For example, the 1969 Moon landing has a timestamp of about −14182940.