Enter data
Date/Time- —
Settings
- 4
- 2
- 6
- 8
- 10
- 9.8 m/s²
- 9.81 m/s²
- 10 m/s² (school)
Result
CalcCoreWhat a Unix timestamp is
A Unix timestamp (epoch time, POSIX time) is the number of seconds that have passed since January 1, 1970 00:00:00 UTC. The number 0 is January 1, 1970, and 1700000000 is November 14, 2023 22:13:20 UTC (a Tuesday). It is a convenient way to store a moment in time as one number in databases, APIs, logs and file systems, regardless of the time zone. Leap seconds are not counted in Unix time: every day has exactly 86,400 seconds.
Seconds, milliseconds, microseconds and nanoseconds
A classic timestamp in seconds has 10 digits (up to the year 2286). JavaScript, Java and many APIs use milliseconds (13 digits), some databases and profilers use microseconds (16 digits), and Go, Rust and time series use nanoseconds (19 digits). The calculator detects the unit by the number of digits and shows which one it chose, and you can change it manually if needed. Numbers are parsed exactly, so a 19-digit value like 1700000000123456789 does not lose digits, unlike ordinary JavaScript numbers.
Time zones and formats
A timestamp always corresponds to one moment, while the date depends on the zone. The same 1700000000 is 22:13:20 in UTC and already 00:13:20 on November 15 in Kyiv. The calculator shows the date in the chosen zone (with a search among more than 500 cities and zones), in ISO 8601 with an offset, RFC 2822 and HTTP date formats. For each moment you see the weekday, the day of the year, the ISO week number and “how long ago or from now”.
Date to timestamp
The “Date → timestamp” tab converts a date and time (with seconds and a fractional part, for example 14:30:05.123) into a timestamp in seconds, milliseconds, microseconds and nanoseconds. The time is entered in the chosen zone: November 7, 2026 14:30:05 in Kyiv is 1794054605. If the time falls on a daylight saving change, the calculator warns you: an hour that does not exist or an hour that happens twice.
The Year 2038 problem
Old systems store a timestamp as a signed 32-bit integer: the largest value 2147483647 is January 19, 2038 03:14:07 UTC, and the next second overflows the number. The smallest value, −2147483648, is December 13, 1901. The calculator shows whether a value fits into 32 bits. Modern systems with 64-bit time do not have this problem.
Other epochs
Different systems count time from different dates. Windows FILETIME and LDAP use hundreds of nanoseconds since 1601, .NET ticks count from year 0001, Excel counts days since December 30, 1899, Apple counts seconds since 2001, WebKit browsers use microseconds since 1601 and astronomers use the Julian day. For January 1, 2000 these are 125911584000000000, 630822816000000000, 36526 and 2451544.5 respectively. In Excel, serial numbers 1–60 are shifted because of the well-known false leap year 1900.
Code snippets
Under the result there is a collapsed block with ready-made calls for JavaScript, Python, PHP, Go, Java, C#, Bash, PostgreSQL and MySQL: how to turn a timestamp into a date and how to get the current timestamp. The calculator itself loads and stores nothing, and the conversion runs in the browser.
Limits
Dates from the year 1000 to 2999 for date input, and for timestamps the browser's date limit of about ±275,760 years applies. Unix time does not count leap seconds and time zone rules come from the browser's database. The code snippets are typical, so check them for your version of the language.
Unix time does not count leap seconds. The unit is detected by the number of digits: you can change it manually.
FAQ
How do I convert a Unix timestamp to a date?
Paste the number on the “Timestamp → date” tab: the calculator shows the date in UTC, in the chosen zone and in ISO 8601. For example 1700000000 is 11/14/2023 22:13:20 UTC.
How do I tell whether it is seconds or milliseconds?
By the number of digits: 10 digits are seconds, 13 are milliseconds, 16 are microseconds, 19 are nanoseconds. The calculator detects it itself and lets you change it manually.
Why is my date in the year 55,840?
Milliseconds (13 digits) were entered as seconds. Choose “Auto” or “Milliseconds” and the date becomes correct.
How do I convert a date to a timestamp?
Open the “Date → timestamp” tab and enter the date, time and zone. 11/07/2026 14:30:05 in Kyiv is 1794054605.
Does Unix time account for time zones?
The timestamp itself does not: it is a moment in UTC. A time zone is needed only to show the date or to enter a local time.
What is the Year 2038 problem?
A signed 32-bit integer overflows at 2147483647, i.e. January 19, 2038 03:14:07 UTC. The calculator shows whether a value fits into 32 bits.
Are leap seconds counted?
No. Under POSIX every day in Unix time has exactly 86,400 seconds, so leap seconds are “stretched” into a neighbouring second.
Is precision lost for 19-digit numbers?
No. Numbers are parsed exactly, unlike ordinary JavaScript numbers, which lose the last digits after 15–16 digits.
How do I get the current timestamp?
The form has a live counter and a “Now” button. In code: Math.floor(Date.now() / 1000) in JavaScript, int(time.time()) in Python, time() in PHP, date +%s in Bash.
What are Windows FILETIME and .NET ticks?
They count intervals of 100 nanoseconds: FILETIME since January 1, 1601 and .NET ticks since January 1, 0001. The “Other epochs” tab converts them to Unix time and back.
Why are Excel dates before March 1900 wrong?
Excel treats 1900 as a leap year (although February 29, 1900 did not exist), so serial numbers 1–60 are shifted by a day.
Which dates does the calculator support?
For date input from the year 1000 to 2999, for timestamps about ±275,760 years. A negative timestamp is a time before 1970.