Two directions, one tool
Timestamp to date is the direction you need when reading logs, database rows and API responses. Date to timestamp is the direction you need when constructing a query parameter or seeding test data. Doing both in one box avoids the classic mistake of converting the wrong side first.
Format reference
| Format | Example | Used by |
|---|---|---|
| Unix seconds | 1763311200 | POSIX APIs, most databases |
| Unix milliseconds | 1763311200000 | JavaScript, Java Instant, browsers |
| ISO 8601 UTC | 2025-11-16T14:00:00Z | JSON APIs, OpenAPI, RFC 3339 |
| RFC 2822 | Sun, 16 Nov 2025 14:00:00 GMT | Email headers, HTTP dates |
| Local time | 2025-11-16 22:00:00 +08:00 | Logs, user-facing displays |
Why auto-detection is safe enough
Seconds are 10 digits until November 2286. Milliseconds are 13 digits for the same range. A 10-digit value interpreted as milliseconds would point to January 1970; a 13-digit value interpreted as seconds would land in the year 56000. The digit count alone separates them for any plausible date.
If you paste a value outside those lengths, the converter still tries, but check the result. Pure-digit values are always interpreted by length; an 8-digit value such as 20251116 is treated as seconds, not as a compact date string.
When an API returns a timestamp as a string, verify the unit before arithmetic. Adding 1 to a seconds value is one second; adding 1 to a millisecond value is one millisecond.
Timezone display
The local output uses your browser's timezone. If you need a specific zone, use the timezone converter, which accepts IANA names and formats the same instant in several zones at once.