β³ Epoch Converter
Epoch time counts the seconds since 1 January 1970 UTC. Paste an epoch value to see what moment it represents in your timezone and in UTC, or pick a date to get its epoch value back.
How the unit is detected
You do not pick seconds or milliseconds - the converter counts the digits, ignoring any minus sign and stripping commas, spaces and underscores first:
up to 11 digits -> seconds up to 17 -> microseconds
up to 14 digits -> milliseconds more -> nanoseconds
1786953600 is ten digits, so it is read as seconds: 17 August 2026, 08:00:00 UTC. The thresholds are deliberately loose, which is the thing to watch: an eleven-digit millisecond value is still read as seconds and lands in 2286 or later. Anything past the year 9999 is refused rather than shown wrong.
The rows under the conversion
- Local vs UTC - the same instant twice; the local ISO row carries your offset in brackets.
- ISO week number - the ISO-8601 week, which belongs to whichever year holds its Thursday. Early January can therefore be week 52 of the year before.
- Day of year - 1 for 1 January, 251 for 8 September 2026, 366 in a leap year.
- Relative - approximate above a day, using an average month of 30.4375 days and a year of 365.25 days, so "3 months ago" is a rough figure and the exact date rows are not.
Frequently asked questions
What is epoch time right now?
The box is pre-filled on load and the "Use current time" button refreshes it. It is a ten-digit number, and stays ten digits until November 2286.
Can epoch time be negative?
Yes. Negative values are dates before 1970 and the converter accepts them - -86400 is 31 December 1969. Many databases and APIs reject them, so check before storing one.
Why is my epoch date eight hours out?
You are comparing a local row against a UTC one. Epoch values carry no timezone; the Local time and UTC rows here show the same instant rendered two ways.