Switch to English?

Switching reopens this page. Unsubmitted files, edits and browser processing results will not move to the other domain.

Submitted server tasks remain accessible. Files keep their original deletion deadlines.
Destination website:

Timestamp Converter

Convert seconds, milliseconds and dates with explicit time zones.

Improve this tool

Timestamp workbench

Use UTC or an IANA name. Language and IP do not determine the zone.

Requires a modern browser with time zones, BigInt, Workers and a secure connection.

Editing either field converts automatically. Changing the zone keeps the current input: timestamps keep the instant, while dates are reinterpreted in the new zone.

Current input
Seconds: up to 3 decimals. Milliseconds: integers only.
YYYY-MM-DD HH:mm:ss[.SSS]

Choose an explicit offset for repeated local times; nonexistent times are reported as errors. Years 0001–9999 are supported. Historical and future zone rules follow the current browser’s time zone data.

Processed content stays in this page’s memory and cannot be recovered after clearing or closing.

About this tool

Convert between timestamps and dates with explicit units and time zones. Batch checks provide per-row errors, offset choices for repeated times, copying and CSV download. Input and results stay in browser memory; only run status, duration, checked row counts and copy/download events are reported.

How to use

  1. Choose a unit and zone, then edit either single-value field to convert automatically.
  2. In batch mode enter one value per line and convert all; fix errors or choose an offset for repeated times.
  3. Copy a value or download all rows as CSV, then clear the page.

Frequently asked questions

Are seconds and milliseconds detected automatically?

No. Choose the unit explicitly. Seconds accept up to three decimals and milliseconds must be integers. Common 10/13-digit mistakes show a hint, never an automatic switch. Switching units after a valid single conversion preserves the instant; the reinterpret action preserves the original number.

How are daylight-saving transitions handled?

Nonexistent local times are errors. Repeated times show each candidate offset, seconds and UTC time; an explicit choice is required. Unresolved rows export candidates without a unique timestamp. Zone rules use the browser’s data.

What are the batch limits and counts?

The default is 1000 rows and 100 characters per row. All empty rows, including a trailing empty row, remain and report errors. Item count means rows checked, not rows converted successfully. CSV includes all rows and prefixes dangerous initial characters with an apostrophe to prevent formula execution.

Which dates and zones are supported?

Use YYYY-MM-DD HH:mm:ss[.SSS], optionally with T as separator. Implicit zones, ambiguous abbreviations, 24:00 and leap seconds are not accepted. UTC and local years must both be 0001–9999. Negative timestamps and millisecond precision are supported. UTC is the default; choose a browser zone or IANA name explicitly. Historical offset seconds are displayed separately, while UTC output ends in Z.

COMMUNITY

Discussion & comments

Share your experience and discover more ways to use this tool.

Loading comments…