What is it?
A Unix timestamp counts the seconds since 1 January 1970, 00:00 UTC. The Unix Timestamp Converter turns it into a readable date in any time zone, and turns dates back into timestamps.
Who is it for?
Developers reading logs and databases, testers checking expiry times, data analysts converting exported timestamps, and support staff working out when an event happened in a user’s time zone.
How to use it
- Timestamp → date: paste the number in Unix timestamp (seconds or milliseconds), e.g. 1767225600, and choose the zone in That time is in.
- Date → timestamp: pick the Date and time and copy the number. Now: shows the current timestamp.
Seconds or milliseconds?
- A 10-digit number (like 1767225600) is seconds: used by Linux, PHP, Python and most APIs.
- A 13-digit number (like 1767225600000) is milliseconds: used by JavaScript, Java and many databases. The tool detects which one you pasted.
- A date in 1970 or far in the future usually means the unit was mixed up.
The time is off by hours
Timestamps are always UTC. A log written in India (IST, UTC+5:30) shows 5½ hours ahead of the same timestamp read as UTC. Pick the right zone in That time is in.
Good to know
Systems that store timestamps as 32-bit numbers run out on 19 January 2038 (the “Year 2038 problem”). Modern 64-bit systems are not affected.
Errors and how to fix them
- Date shows 1970: you pasted milliseconds as seconds or a very small number; check the number of digits.
- Date far in the future: seconds read as milliseconds the other way; check the unit.
Open the tool: Unix Timestamp Converter
Still stuck?
Contact support. Tell us which tool or page you were using, what you tapped, what you saw, and your phone or computer and browser (for example: Android phone, Chrome). We reply by email.
Questions, or an error not listed here?
Tell us in the comments: what you were doing, the exact message you saw, and your device and browser. We read every comment and add new fixes to this article.