Convert Unix timestamps to human-readable dates, or dates to timestamps. Supports seconds and milliseconds.
Share this tool
Found it useful? Help a fellow developer discover it.
A Unix timestamp is the number of seconds that have elapsed since January 1, 1970, 00:00:00 UTC. This moment is known as the Unix epoch. It is also called epoch time or POSIX time. It is the most common way to represent a point in time in software because it is a single integer with no timezone ambiguity. Every programming language, database, and operating system can convert it to a human-readable date in any timezone.
JavaScript's Date.now() returns milliseconds, not seconds. This is a common source of bugs. This converter supports both. 10-digit numbers are treated as seconds. 13-digit numbers are milliseconds.
| Format | Example |
|---|---|
| ISO 8601 (UTC) | 2026-03-16T14:30:00.000Z |
| ISO 8601 (with offset) | 2026-03-16T14:30:00+05:30 |
| ISO 8601 (date only) | 2026-03-16 |
| RFC 2822 | Mon, 16 Mar 2026 14:30:00 GMT |
| Locale string | March 16, 2026 14:30:00 |
Select the Timestamp to Date direction, choose Seconds or Milliseconds depending on your timestamp length (10 digits for seconds, 13 for milliseconds), paste your timestamp into the input, and the results appear instantly. ISO 8601, UTC, local time, and relative time are all shown simultaneously so you can copy whichever format you need.
Click the Now button to populate the input with the current Unix timestamp in seconds. The output updates to show today's date and time across all formats. Refresh or click Now again to get a fresh timestamp. The current time is read from your device clock and converted entirely in your browser.
A 10-digit Unix timestamp represents seconds since the epoch. JavaScript's Date.now() and many modern APIs return milliseconds, a 13-digit number that is 1000 times larger. Use the Milliseconds option in this converter when you have a 13-digit value.
32-bit signed integers overflow at 2,147,483,647, which corresponds to January 19, 2038. Systems that store timestamps as 32-bit integers, including older C code and some databases, will break at that point. Most modern systems use 64-bit integers, which will not overflow for billions of years.
The ISO 8601 and UTC fields always show the time in UTC. The Local field shows the time in your browser's detected time zone. If you see a discrepancy, check whether your input is in seconds or milliseconds. That mismatch is the most common source of confusion.
No. All conversion logic runs entirely in your browser using JavaScript's built-in Date API. Nothing is sent to a server.
The converter accepts any string that JavaScript's Date constructor can parse: ISO 8601 (recommended), RFC 2822, and many locale-aware strings. ISO 8601 with an explicit timezone such as 2026-03-16T14:30:00Z is the most reliable format across all browsers.
Select the Date to Timestamp direction, type or paste a date string in the input field (ISO 8601 format is most reliable, for example 2026-06-15T09:00:00Z), and the Unix timestamp in both seconds and milliseconds appears in the output immediately.
In Java and C#, a millisecond epoch timestamp is typically stored as a long (a 64-bit integer), so developers often search for 'long to date' or 'long timestamp' when they really mean a millisecond Unix timestamp. It's the same 13-digit number this converter already handles. Select Milliseconds and paste the value in.
Not usually. 'Timecode' more often refers to a video or audio position (hours:minutes:seconds:frames, as in SMPTE timecode) rather than a point in calendar time. If what you actually have is a 10 or 13-digit number representing seconds or milliseconds since 1970, that's a Unix timestamp and this converter handles it directly.
UUID / ULID Generator
Generate RFC-4122 UUIDs (v1, v4, v5) and ULIDs instantly.
Cron Expression Builder
Build and validate cron expressions with a human-readable description.
Number Base Converter
Convert numbers between binary, octal, decimal, and hexadecimal.
JSON ↔ TOON
Convert JSON to TOON (Token-Oriented Object Notation) to reduce LLM prompt token usage by ~40%. Lossless and bidirectional.
An explainer on the Unix timestamp overflow event on January 19, 2038 and why every developer writing date-handling code needs to understand it.
Read article