Timestamp Converter

Converts Unix epoch and ISO-8601 datetimes in the browser. Paste epoch seconds, epoch milliseconds, or an ISO-8601 datetime and read UTC ISO, epoch seconds, and epoch milliseconds. Values with an absolute value of 1e12 or more are treated as milliseconds; smaller integers are seconds. Output is UTC only; this is not a timezone-law product.

Timestamp converter

UTC only. This is also an epoch converter on this same page. Not a timezone-law product (no IANA timezone picker, no DST tables). Client-side only — input never leaves the browser.

How to use

  1. Paste epoch seconds (e.g. 1704067200), epoch milliseconds (e.g. 1704067200000), or ISO-8601 (e.g. 2024-01-01T00:00:00.000Z).
  2. Read UTC ISO, epoch seconds, and epoch milliseconds. Output is UTC only.
  3. Nothing is sent to a server. This is not a timezone-law product and not a scheduler. Refreshing the page clears the form.

Results

Paste a Unix epoch or ISO-8601 datetime to convert.

Runs in your browser. Nothing is uploaded.

Frequently asked questions

What is the difference between Unix epoch seconds and milliseconds?

Unix epoch seconds count seconds since 1970-01-01T00:00:00.000Z. Epoch milliseconds count milliseconds since that instant. On this page, a numeric value whose absolute value is 1e12 (1,000,000,000,000) or more is treated as milliseconds. Smaller integers are treated as seconds. Example: 1704067200 is seconds; 1704067200000 is milliseconds. Both convert to 2024-01-01T00:00:00.000Z. This timestamp converter is also an epoch converter on this same page.

How does this timestamp converter parse ISO-8601?

Paste an ISO-8601 datetime such as 2024-01-01T00:00:00.000Z. Parsing uses Date.parse and the Date constructor and requires a valid date. Unparseable values such as 2024-13-40 or not-a-date fail closed. Output ISO always includes milliseconds, for example 2024-01-01T00:00:00.000Z.

Does this convert timezones or DST?

No. Results are UTC only. This is not a timezone-law product: there is no IANA timezone picker, no DST table, and no local civil-time conversion. You can read the same instant as ISO UTC (and an optional UTC locale string). It does not apply timezone law.

What is the 1704067200 worked example?

1704067200 seconds, 1704067200000 milliseconds, and 2024-01-01T00:00:00.000Z are the same instant. Paste any of those three forms to see the other two. The page uses Date to convert; output ISO includes milliseconds.

Is my value sent to a server? Do I need an account?

No. Conversion runs in your browser. The value never leaves the browser. There is no signup, and Tallymill does not save what you paste. Refreshing the page clears the form.

Is this a scheduler?

No. This is a timestamp converter and epoch converter, not a scheduler. It does not run cron, does not queue jobs, and does not convert timezone law or DST rules. For a 5-field Unix cron expression, use the cron expression generator.