A real leap day
2024-02-29T08:00:00+08:00Expected: UTC: 2024-02-29T00:00:00.000Z
The +08:00 offset is subtracted to obtain UTC.
Unix Timestamp
Timestamp Converter
Go from Unix timestamps to readable dates and back again.
Something missing? Suggest an improvement →
Worked examples: try and compare
These examples show expected results and common failure cases. Loading an example replaces the tool input after confirmation when you already have text.
Reject an impossible date
2025-02-29T00:00:00ZExpected: Invalid calendar date; no timestamp.
2025 is not a leap year. The converter must not silently turn this into a March date.
How to use Timestamp Converter
Enter an integer timestamp and choose seconds or milliseconds, or enter an ISO date with a timezone, such as 2026-01-01T00:00:00Z. Results show UTC and your local timezone.
Choose seconds or milliseconds explicitly
Unix time measures elapsed time from 1970-01-01T00:00:00Z. Enter 0 in seconds mode to see that instant. The seconds value 1704067200 and milliseconds value 1704067200000 both represent 2024-01-01T00:00:00Z. The selected mode controls interpretation; the tool does not guess from the digit count.
Include a timezone when converting a date
Use an ISO date such as 2024-01-01T08:00:00+08:00. It represents the same instant as 2024-01-01T00:00:00Z. A date without Z or an explicit offset is rejected so that a local-time assumption cannot silently shift the conversion.
Read UTC and local output correctly
UTC output is stable across computers. Local time uses your browser’s environment, so a colleague in another timezone may see a different clock reading for the same instant. Use UTC or a stated offset when sharing logs. Impossible calendar dates and invalid clock fields are rejected before conversion. This tool does not resolve named timezones or schedule daylight-saving transitions.
Do you upload my data?
This tool runs in your browser. Inputs and results are not sent to our server. Closing or refreshing the page clears your work, so save any results you need.