Epoch Timestamp Converter
Every API response, database row and log line stores time as a Unix timestamp - seconds since January 1, 1970, UTC. This converter turns those numbers back into dates humans can read, and turns dates into timestamps for the query you are about to write. It also shows the current timestamp ticking live, which is the fastest way to check whether a mystery number is in seconds or milliseconds.
Developers live in this conversion daily; everyone else meets it once and never forgets it. Paste, read, move on - all locally in your browser.
How to use
- Paste a Unix timestamp (seconds) - the UTC and local date appear instantly.
- Toggle the milliseconds switch if your number is 13 digits.
- Or pick a date and time to get its timestamp for your API call.
Frequently asked questions
What is a Unix timestamp?
The number of seconds elapsed since 00:00:00 UTC on January 1, 1970 - the moment computers agreed to call zero. Right now it is a 10-digit number; in 2038 the 32-bit version overflows, which is the Y2K of embedded systems.
Why is my timestamp 13 digits?
It is in milliseconds, not seconds - common in JavaScript (Date.now()). Divide by 1,000 or use the milliseconds toggle to convert honestly.
Does the timestamp depend on my time zone?
The number itself is always UTC-based. The converter shows it both as UTC and in your local time zone, so the same timestamp reads differently but means identically.
What happens at timestamp 0?
That is the Unix epoch: January 1, 1970, 00:00:00 UTC. Negative timestamps count backwards from it - historical dates before 1970 work fine.