← All Tools
Epoch Converter🔒 100% local
Unix timestamp to date. Privacy-first, no server uploads, no tracking.
Takes a Unix timestamp and prints the dates it corresponds to, or takes a date string and prints the timestamp. A value with eleven or more digits is read as milliseconds and anything shorter as seconds; a value that is not numeric is passed to the browser's date parser. The report covers seconds, milliseconds, ISO 8601, the GMT string, local time, days since epoch, weekday, and a rough relative description.
How to use it
- Enter a timestamp such as 1704067200, or a date such as 2024-01-01T00:00:00Z.
- Press Process - the input is classified as seconds or milliseconds automatically and the last line tells you which.
- Copy the exact ISO or GMT line where you need a value another system will parse, and ignore the local lines.
Worked example
1704067200becomesInput: 1704067200
Unix (seconds): 1704067200
Unix (milliseconds): 1704067200000
ISO 8601 (UTC): 2024-01-01T00:00:00.000Z
UTC string: Mon, 01 Jan 2024 00:00:00 GMT
Local time: Mon Jan 01 2024 00:00:00 GMT+0000 (Coordinated Universal Time)
Local date: 2024-01-01 00:00:00
Days since epoch: 19723
Weekday (local): Monday
Relative: 2.7 years ago
Also detected as seconds (auto).Computed with the clock and timezone set to UTC, so the Local and Relative lines read the same as the UTC ones. On your machine those three lines follow your device clock and timezone instead; the ISO, UTC, seconds, milliseconds, and days-since-epoch lines are fixed.
When to use it
- Reading a timestamp out of a log line or a database column in a form you can reason about.
- Getting a millisecond value to paste into a token expiry or a cron check.
- Checking how many days separate two timestamps before writing a retention rule.
What it does not do
- The seconds-versus-milliseconds guess turns on an 11-digit threshold, so a seconds value past the year 5138 is misread as milliseconds and the dates come out roughly a thousand times too early.
- Date strings go through the browser's own parser, which is lenient and engine-dependent for formats like 01/02/2024 and treats a bare date as UTC midnight.
- The local time, local date, weekday, and relative lines differ from machine to machine; only the ISO, UTC, epoch, and day-count lines are stable enough to paste into an issue.
- No timezone picker and no date arithmetic - it converts a single value, one per press.