Timestamp Converter

Date to Unix Timestamp

Convert any date and time into a Unix timestamp — epoch seconds and milliseconds — instantly and privately in your browser.

ISO 8601
UTC string

Runs entirely in your browser — nothing you enter is uploaded or stored.

How to convert a date to a Unix timestamp

  1. Type a date into the date field above (ISO 8601 works best).
  2. Read the resulting epoch value in the timestamp field.
  3. Switch the unit selector to get seconds or milliseconds.

Why convert dates to epoch time?

Many systems — databases, APIs, JWT tokens, cron-like schedulers — expect a plain integer rather than a formatted date string. Converting a human-readable date to its Unix timestamp is the standard way to feed a specific point in time into that kind of system.

Seconds vs. milliseconds

Unix time is traditionally counted in seconds, but JavaScript and many web APIs work in milliseconds instead. This tool shows both, so you can copy whichever unit your target system expects without doing the ×1000 or ÷1000 conversion by hand.

Related tools

Frequently asked questions

How do I convert a date to a Unix timestamp?
Type or paste a date into the date field above, in a format like 2023-11-14T22:13:20.000Z or even just 2023-11-14. The equivalent Unix timestamp — in both seconds and milliseconds — appears immediately.
What date formats are accepted?
The date field accepts anything JavaScript's Date parser understands: full ISO 8601 strings (2023-11-14T22:13:20.000Z), date-only strings (2023-11-14), and most common human-readable formats. ISO 8601 is the most reliable choice since it has no ambiguity.
Why does a date-only input give midnight as the time?
When you enter a date without a time component, it is interpreted as midnight UTC on that day (00:00:00). This is standard JavaScript date-parsing behaviour, not a limitation of this tool.
Do I get seconds or milliseconds as the result?
Both. The epoch field shows whichever unit is selected in the dropdown, and the ISO/UTC results underneath confirm the exact instant, so you can copy whichever value your project needs.
Does the timezone of my browser affect the result?
No — the conversion is always computed against the parsed instant, and the resulting epoch value is the same regardless of your local timezone. Only the display of the reconstructed date is shown in UTC.
Is this useful for setting expiry times or scheduling?
Yes. Converting a target date to its epoch value is exactly what many APIs, cron-like schedulers, and token expiry fields (e.g. JWT `exp`) expect — a plain epoch integer rather than a formatted date string.