Timestamp Converter
Convert Unix timestamps to readable dates and date values back to timestamps.
Local date
UTC date
Unix seconds
Unix milliseconds
Date tool
Timestamp Converter
Convert seconds, milliseconds, local dates, and UTC output quickly.
All tools
Related Tools
Continue the workflow with nearby developer and data utilities.
How To Use The Timestamp Converter
To turn a number into a date, type or paste a Unix timestamp into the Unix timestamp field. The tool instantly shows the matching local date in your own time zone, the UTC date, and the value in both seconds and milliseconds. To go the other way, pick a moment in the Date and time picker and read off the corresponding timestamps. The Use current time button fills in the present moment, which is handy for grabbing a fresh epoch value to drop into a log entry, a database row, or an API request.
What A Unix Timestamp Actually Is
A Unix timestamp is a single whole number that counts the seconds elapsed since the Unix epoch: midnight on 1 January 1970, measured in Coordinated Universal Time (UTC). Every second that passes adds one to the count, so the value is always growing. Because it is one absolute number with no time zone, no month names, and no daylight-saving rules baked in, it is the cleanest way for computers to store and compare moments. The same instant can then be displayed as a friendly date in whatever time zone the reader happens to be in. That separation between the stored number and the displayed date is exactly what this converter makes visible.
Example Timestamps And Their Dates
The table below maps a few Unix timestamps (in seconds) to their UTC dates so you can see how the count grows over time. A present-day timestamp is a 10-digit number; the epoch itself is simply zero.
| Unix seconds | UTC date and time | What it marks |
|---|---|---|
0 | 1970-01-01 00:00:00 | The Unix epoch (the start) |
1000000000 | 2001-09-09 01:46:40 | One billion seconds |
1500000000 | 2017-07-14 02:40:00 | 1.5 billion seconds |
1700000000 | 2023-11-14 22:13:20 | 1.7 billion seconds |
2147483647 | 2038-01-19 03:14:07 | 32-bit limit (year 2038) |
Multiply any of these values by 1000 to get the millisecond version used by JavaScript and many logging systems.
Worked Example: Reading A Log Line
Suppose a server log records an event at 1700000000. Pasting that number into the converter shows a UTC date of 14 November 2023, 22:13:20, and your own local time beside it. If the log instead stored 1700000000000, that is the millisecond form of the very same instant; the converter recognises the longer 13-digit number and still resolves it to November 2023 rather than a date far in the future.
Why This Tool Is Useful
Timestamps are everywhere a developer looks: in application logs, database created_at columns, JSON from APIs, analytics events, JWT expiry fields, and cron schedules. Reading a raw 10-digit number tells you nothing at a glance, and doing the conversion by hand is error-prone because of time zones and the seconds-versus-milliseconds trap. This converter gives you the local date, the UTC date, and both numeric forms together, so you can sanity-check a value, line up events from different servers, or generate a fresh epoch number without leaving the page or installing anything.
Accuracy And Privacy
All conversions run locally in your browser using its built-in date functions and your device's clock, so the local time shown matches your own system settings and nothing you enter is uploaded, logged, or stored. That makes it safe to convert values from private logs and internal systems. Two things to keep in mind for correctness: confirm whether your source value is in seconds or milliseconds, and remember that the UTC date is the neutral reference, while the local date shifts with your time zone and any daylight-saving offset.
FAQ
What is a Unix timestamp?
A Unix timestamp is a single integer that counts the number of seconds elapsed since the Unix epoch, which is midnight on 1 January 1970 in Coordinated Universal Time (UTC). Because it is one absolute number with no time zone attached, it is the most reliable way to store and compare moments in time across databases, log files, and APIs.
What is the difference between seconds and milliseconds?
A timestamp in seconds is a 10-digit number such as 1700000000, while the same instant in milliseconds is a 13-digit number such as 1700000000000, one thousand times larger. JavaScript and many logging systems use milliseconds, whereas databases and Unix command-line tools usually use seconds. If your converted date lands near 1970, you most likely passed milliseconds where seconds were expected, or the reverse.
Why does the same timestamp show two different dates?
A Unix timestamp always points to one exact moment in UTC, but that moment is displayed differently depending on the viewer's time zone. This tool shows both the UTC date and your local date side by side so you can see the offset. When you store or compare times across servers, always use the UTC value to avoid confusion.
What is the year 2038 problem?
Older systems store Unix time in a signed 32-bit integer, which can only count up to 2,147,483,647 seconds. That limit is reached at 03:14:07 UTC on 19 January 2038, after which the counter overflows and wraps to a negative number, jumping back to 1901. Modern 64-bit systems store the value in a wider integer and are unaffected for billions of years.
Does this converter upload my data anywhere?
No. Every conversion is computed locally in your browser using your device's own clock and date functions. Nothing you type into the timestamp or date field is sent to any server, logged, or stored, so it is safe to convert values from private logs and internal systems.