Timestamp to Date
Paste a Unix timestamp and instantly see the equivalent UTC date, local date and RFC 3339 / ISO 8601 string without sending anything to a server.
This page is useful when you only need a quick one-way conversion from Unix time to a readable date.
Supports timestamps in seconds and milliseconds.
Result
Result will appear here.
Examples
1710153600 1704067200000 -1
Unix time, RFC 3339 and ISO 8601
A Unix timestamp counts seconds (or milliseconds) since 1 January 1970 UTC — compact, unambiguous and what most systems store internally. RFC 3339 is the human-readable interchange format built on ISO 8601 that APIs, logs and JSON payloads use to exchange the same moment, for example 2026-07-02T08:30:00Z.
Every RFC 3339 timestamp is a valid ISO 8601 timestamp, but RFC 3339 is stricter: it always includes a full date and time, requires a numeric UTC offset or Z, and allows a space-free T separator only. The ISO output of this converter follows that profile, so you can paste it straight into API requests or config files.
| Format | Example | Typical use |
|---|---|---|
| Unix seconds | 1782030600 |
Databases, caches, epoch fields in APIs |
| Unix milliseconds | 1782030600000 |
JavaScript Date.now(), Java, event logs |
| RFC 3339 (UTC) | 2026-07-02T08:30:00Z |
JSON APIs, OpenAPI date-time, logs |
| RFC 3339 with offset | 2026-07-02T15:30:00+07:00 |
Calendars, local-time records |
| ISO 8601 (extended) | 2026-07-02T08:30:00.000Z |
JavaScript toISOString(), .NET, exports |
FAQ
Does this support milliseconds?
Yes. Longer inputs are treated as milliseconds, while shorter Unix values are treated as seconds.
Why do UTC and local time look different?
UTC is timezone-neutral. Local output uses your current browser and operating system time zone.
Can I use negative timestamps?
Yes. Negative values represent dates before the Unix epoch.
Is the ISO output RFC 3339 compliant?
Yes. The ISO string uses the UTC “Z” form with a T separator, which satisfies both RFC 3339 and ISO 8601, so it works in JSON APIs and OpenAPI date-time fields.
What is the difference between RFC 3339 and ISO 8601?
RFC 3339 is a strict profile of ISO 8601 for internet timestamps: full date and time, a T separator and an explicit UTC offset or Z are always required.
Learn how this tool is commonly used
Read the timestamp guide for common scenarios, readable date checks and timezone context.