Timestamp Converter
Unix timestamp ↔ human-readable date
Unix Timestamp: the Calendar Computers Use
What date is 1789000000? The human meaning of that log-file number is one paste away.
Computers don't keep dates the way you do: they count seconds elapsed since January 1, 1970 UTC (the epoch). Those 10-digit numbers in log files, API responses and databases are exactly that. This tool works both ways: paste a timestamp to see the readable date in your local time and UTC, or pick a date from the calendar to get its timestamp in seconds and milliseconds. Values with 13 digits are automatically treated as milliseconds — you can paste JavaScript's Date.now() output directly. The live counter at the top shows the current Unix time ticking by the second; copy it with one click whenever you need test data or a cache key.
Features
Live 'Now'
Current Unix time ticks second by second.
Two-Way
Timestamp → date and date → timestamp.
Smart Detection
13+ digits auto-detected as milliseconds.
Local + UTC
Results shown in your local time and UTC.
Epoch Guide
Need to know
- Epoch start: January 1, 1970, 00:00 UTC
- 10 digits = seconds · 13 digits = milliseconds
- Timestamps are timezone-free — zones apply only on display
- Year 2038 problem: 32-bit counters overflow on Jan 19, 2038
Example values
- 0 → January 1, 1970 00:00 UTC
- 1000000000 → September 9, 2001 (the first billion)
- 1700000000 → November 14, 2023
- 2000000000 → May 18, 2033
Frequently Asked Questions
Why does Unix time count from 1970?
When Unix was developed in the early 1970s, its engineers picked a recent, round starting point: January 1, 1970 UTC. That 'epoch' has been computing's shared clock reference ever since.
Should I use seconds or milliseconds?
Unix tradition is seconds (10 digits); JavaScript and many modern APIs use milliseconds (13 digits). The tool detects which one from the digit count and says so — still, check the documentation's unit when sending values to an API.
Does a timestamp have a timezone?
No — a timestamp is universal, the same instant everywhere on Earth. Timezones only apply when displaying to humans, which is why the tool shows the result in both your local time and UTC.
What is the Year 2038 problem?
A signed 32-bit integer maxes out at 2,147,483,647 — which corresponds to January 19, 2038, 03:14:07 UTC. At that moment 32-bit counters overflow. Modern 64-bit systems are fine for billions of years.
Can timestamps be negative?
Yes — they represent dates before 1970. For example, -86400 is December 31, 1969. The tool converts negative values correctly.
How do I get the current timestamp?
Copy it from the live counter at the top with one click. In code: JavaScript's Math.floor(Date.now()/1000), Python's time.time() and PHP's time() all return the same value.