Epoch Converter: Unix Timestamp to Date and Back
Paste a Unix timestamp in seconds or milliseconds to read it as a UTC date and time, or turn a UTC date and time into its timestamp.
A Unix timestamp counts the seconds since 00:00:00 UTC on January 1, 1970, with every day counted as exactly 86400 seconds. So 1234567890 is 2009-02-13T23:31:30Z, and 2147483647, the largest value a signed 32-bit counter holds, lands on 2038-01-19 at 03:14:07 UTC. A 13-digit value is usually milliseconds: divide by 1000 to get seconds.
This converter works in UTC on the proleptic Gregorian calendar and ignores leap seconds, as Unix time does. Check results against your own system before relying on them for billing, contract deadlines or scheduling, since applications differ in time zones, units and how they handle dates before 1970.
Timestamp to date (UTC)
2009-02-13T23:31:30Z
- Readable
- Friday, February 13, 2009, 23:31:30 UTC
- Seconds
- 1,234,567,890
- Milliseconds
- 1,234,567,890,000
- Day of the year
- 44
Date to timestamp (UTC)
2147483647
- Milliseconds
- 2147483647000
Embed this calculator on your site →
About the Epoch Converter
Unix time is the count of seconds since the epoch, 1970-01-01 at 00:00:00 UTC, and it is how most operating systems, databases and log files store a moment. This converter works both ways. Paste a timestamp to see the UTC date and time, the weekday, the day of the year and an ISO 8601 string you can drop into code, or enter a UTC date and time to get its timestamp. Pick milliseconds when the number has 13 digits, which is what JavaScript's Date.now() and Java's System.currentTimeMillis() return. Negative timestamps are dates before 1970, so -1 is one second before midnight on New Year's Eve 1969. The count treats every day as 86400 seconds and does not add leap seconds, which is why a timestamp never shows a 60th second. Everything here is in UTC; your local clock reads the same instant offset by your time zone and any daylight saving rule.
Frequently asked questions
Is my timestamp in seconds or milliseconds?+
Count the digits. A timestamp for a date in recent decades has 10 digits in seconds and 13 in milliseconds. If a 13-digit value comes out tens of thousands of years from now, switch the unit to milliseconds.
What happens in 2038?+
A signed 32-bit integer tops out at 2147483647, which is 2038-01-19 at 03:14:07 UTC. Software that still stores Unix time in 32 bits will overflow one second later. Systems using 64-bit time are fine for billions of years.
Why is the result in UTC and not my time zone?+
A Unix timestamp has no time zone; it names one instant everywhere. Showing it in UTC keeps the answer the same for every reader. To get local time, apply your offset from UTC, for example subtract 5 hours for US Eastern Standard Time.
Does Unix time count leap seconds?+
No. Each day is counted as exactly 86400 seconds, so when a leap second is added to UTC the Unix count does not include it. That keeps date arithmetic simple at the cost of being off from atomic time by the leap seconds added since 1972.
Embed this calculator
Free to use on your own site. Paste this snippet where you want the epoch converter to appear — it resizes itself automatically.
<iframe
src="https://manytools.co/embed/epoch-calculator"
title="Epoch Converter by ManyTools"
data-manytools="epoch-calculator"
width="100%"
height="640"
loading="lazy"
style="border:0;width:100%;max-width:720px"></iframe>
<script>
(function () {
window.addEventListener("message", function (e) {
if (e.origin !== "https://manytools.co") return;
var d = e.data || {};
if (d.type !== "manytools:embed:height" || d.slug !== "epoch-calculator") return;
var f = document.querySelector('iframe[data-manytools="epoch-calculator"]');
if (f && d.height) f.style.height = d.height + "px";
});
})();
</script><a href="https://manytools.co/dev/epoch-calculator">Epoch Converter by ManyTools</a>