Are timestamps or dates sent to a server?

No. All conversion runs in your browser using the JavaScript Date API. Nothing is transmitted or stored.

How does the tool tell seconds from milliseconds?

Automatically. A value whose absolute magnitude is below 1e12 is treated as seconds; anything larger is treated as milliseconds. 1700000000 parses as seconds, while 1700000000000 parses as milliseconds — both point to the same moment in 2023.

What date formats does the Date-to-Epoch field accept?

Anything the JavaScript Date parser understands. ISO 8601 strings like 2024-01-01T00:00:00Z are the most reliable; strings without a timezone offset are interpreted per your browser's rules, which can shift the result.

Unix Time Converter

Overview

Unix time counts seconds since 1970-01-01T00:00:00Z (the epoch). This tool converts in both directions: paste an epoch value to see the date, or type a date to get its epoch. A live Current Unix time readout ticks every second at the top, handy for eyeballing token expiry, log timestamps, or cron output.

How to use

Check Current Unix time at the top; press use to drop it into the converter.
Enter a timestamp in Epoch → Date (auto s/ms) — seconds or milliseconds are detected automatically, and the ISO 8601 (UTC) plus local time appear below.
Enter a date string in Date → Epoch (e.g. 2024-01-01T00:00:00Z) to get the timestamp in both seconds and milliseconds.

Examples

1700000000 → 2023-11-14T22:13:20.000Z (plus your local time)
2024-01-01T00:00:00Z → 1704067200 (s) · 1704067200000 (ms)

Notes

Date strings without an explicit timezone (like 2024-01-01 09:00) are parsed using browser-specific rules — include Z or an offset such as +09:00 for unambiguous results. Negative epochs (dates before 1970) are supported.