Tool

Batch timestamp converter and timezone comparison

Convert a pasted column or CSV time field using explicit Unix seconds, milliseconds or offset ISO 8601. Compare UTC, Beijing, local and IANA timezone results; keep original columns and row errors in the CSV export.

1. Add your time column

All parsing and export happen in this tab. Data is never uploaded, saved or put into a link. Refreshing clears the current session; downloaded files stay unchanged.

Suggestions use numeric magnitude and are only hints. The selected unit always wins. ISO requires Z or an explicit offset; timezone-free dates are rejected. Up to 10,000 rows, millisecond precision, years 0001–9999.

Units, DST and limitations

Seconds and milliseconds describe an instant relative to 1970-01-01 UTC. A column uses one selected unit: mixed values are flagged, never silently converted with different units. A millisecond value resembling modern epoch seconds gets a unit warning because dates in January 1970 may be intentional.

Timezone output follows the browser’s IANA rules at that instant, including DST. During autumn clock rollback, identical wall-clock hours can occur twice with different UTC offsets; the offset shown on every result distinguishes them. Spring gaps do not represent an instant. ISO without an offset is rejected, so ambiguous local input is never guessed. Rules depend on your browser/OS database; this tool does not synchronize a server timezone database or parse natural-language dates and logs.

Only UTF-8 comma-separated CSV with a header is supported. Duplicate names and quoted multiline cells are preserved; source line numbers refer to the physical start line. Missing cells are padded with empty values and extra fields receive numbered headers. CSV syntax errors stop import; invalid timestamps remain in the export with error codes.

FAQ

Will mixed seconds and milliseconds be converted automatically?

No. Suggestions show the detected mix, but the selected unit applies to every row. Reparse with a different unit to review suspect rows. The original value, source line and any error stay in the CSV export.

Can I use an ISO date without a timezone?

No. Include Z or an explicit offset such as +08:00. Local times during DST rollback can mean two different instants; an explicit offset removes that ambiguity. Invalid calendar dates and precision finer than milliseconds are rejected.

Does the CSV keep my original data?

Yes. Original columns and their order are preserved, including duplicate headers and multiline quoted cells. Result columns are appended with unique names. Spreadsheet software may reinterpret original cells, so import them as text to preserve literal formulas, leading zeros and long numbers.

Which timezone rules are used?

Your browser's IANA timezone rules for each instant. UTC offsets are shown beside every result, including DST changes. There is no server database synchronization. Input and results stay in this tab, and refreshing clears the session without changing downloaded files.

Related tools