About the Epoch Timestamp & Date Converter
The Epoch Timestamp & Date Converter translates between a date-time value and Unix timestamps in seconds or milliseconds. It is useful when inspecting log entries, API examples, and scheduled data. Timestamps represent instants, while displayed local dates depend on timezone settings, so check the selected unit and timezone interpretation before comparing values.
How to use this tool
- Select whether you are converting a date to a timestamp or back.
- Enter the date or numeric value and choose seconds or milliseconds.
- Convert and inspect the resulting timestamp and human-readable date.
- Confirm the timezone expected by the system that will consume the value.
Example
Input
1970-01-01 00:00:00 UTC; seconds Possible output
0 The Unix epoch begins at midnight UTC on January 1, 1970. A timestamp of zero is a useful reference point, but local date-time controls may display values in a local timezone. The timezone must be explicit when a date is copied between systems.
Practical tips and limitations
Seconds and milliseconds differ by a factor of one thousand and are a common source of integration errors. Check whether an API expects integer seconds, integer milliseconds, or a decimal value. Daylight-saving changes affect local clock representations but not the underlying UTC instant.
Frequently asked questions
How can I tell seconds from milliseconds?
Use the unit selector and the surrounding system documentation; do not infer units from digits alone.
Why does the converted date differ on another device?
The same timestamp can be displayed in different local timezones while representing the same instant.
Does Unix time include a timezone?
A timestamp represents time relative to the UTC epoch; timezone is used when formatting it as a human-readable date.