Unix Timestamp & Konverter Tanggal
The top of the page shows the current timestamp ticking in both seconds and milliseconds; below it you can convert in either direction — enter a timestamp to get a readable date, or pick a date and time to get the matching timestamp.
Results come out in ISO 8601, RFC 2822, local and UTC formats, and you can switch between several common timezones to compare them.
Features
- Seconds or Milliseconds — A 10-digit value is read as seconds and a 13-digit value as milliseconds, with no unit selector to fiddle with.
- Two-Way Conversion — Timestamp to date and date to timestamp, both on the same page.
- Live Clock — A continuously updating Unix timestamp in seconds and milliseconds, useful for checking drift between a server clock and your own.
- Timezone Comparison — Switch between local time, UTC, Beijing, New York, London and Tokyo at any time.
- Standard Formats — ISO 8601 and RFC 2822 side by side, the two formats you meet most often in logs and HTTP headers.
How to use
- Enter a 10- or 13-digit number under "Timestamp to date" and convert.
- Pick a date and time under "Date to timestamp" and convert to get both second and millisecond values.
- Use the timezone dropdown below to see the same instant in other zones.
- Switch the buttons at the top between ISO 8601, RFC 2822, local and UTC output.
FAQ
What is the difference between a 10-digit and a 13-digit timestamp?
A 10-digit value counts seconds (Unix time) and a 13-digit value counts milliseconds. JavaScript Date.now() returns milliseconds, while backends and databases commonly store seconds; the two differ by a factor of 1000, and mixing them is one of the most common causes of timestamps that do not line up.
What is the year 2038 problem?
A signed 32-bit integer can hold Unix seconds only up to 2147483647, which is 2038-01-19 03:14:07 UTC. Past that instant, systems still storing timestamps in a 32-bit int overflow. Today 64-bit systems and JavaScript are not affected.
Do Unix timestamps include leap seconds?
No. Unix time is counted in UTC at a fixed 86400 seconds per day, and leap seconds are smoothed over elsewhere by the operating system, so a timestamp never shows a 60th second.
Why is the converted date a few hours off from my server logs?
Almost always a timezone setting. A Unix timestamp is an absolute UTC value; whether you display it as local time or UTC only affects the presentation. Compare the two with the timezone switcher to confirm.