Practical guide
How to Convert Unix Timestamps and Epoch Time
Convert Unix seconds, milliseconds, readable dates, and batch timestamp values. Learn how to compare UTC, local time, and optional timezones without confusion.
Quick answer
Use this guide when logs, APIs, databases, or events show timestamps that are hard to read. The calculator helps convert one value, many values, or a date difference.
Who this is for
- Developers debugging logs and API responses
- Support teams checking event times
- QA teams comparing incident timelines
- Analysts converting timestamp exports
What to remove or avoid
- No data normally needs redaction here unless pasted logs include private details
- Sensitive log text if you only need timestamps
What to keep visible
- Original timestamp value
- Detected format such as seconds or milliseconds
- UTC and local time
- Optional timezone comparison when working across regions
Useful controls in the tool
- Single convert for one timestamp or date.
- Batch convert for pasted lists, CSV, JSON, or log text.
- Difference mode to measure time between two dates.
- Export CSV or JSON when reviewing many timestamps.
Step-by-step
- 1Paste a timestamp or readable date.
- 2Check the detected format.
- 3Review UTC, local, and relative time.
- 4Use optional timezone only when another region matters.
- 5Use batch mode for many values.
Example
Before: 1777728000 1777728000000 2026-05-02T12:00:00Z After: Unix seconds -> 2026-05-02T13:20:00.000Z Unix milliseconds -> 2026-05-02T13:20:00.000Z
What to do after review
- Check whether the source value is seconds or milliseconds.
- Use timezone comparison for teams in another region.
- Export batch results when reviewing many timestamps.
Tip: Most timestamp mistakes happen when seconds and milliseconds are mixed.