How rows are interpreted
Each row goes through the same exact engine as the single converter. With the unit on Auto, each row is detected on its own, and rows with low-confidence detection say so in the output. With a fixed unit, every row uses it. Rows that cannot be converted keep their original text and get a stable error code (INVALID_INPUT, AMBIGUOUS_SEMANTICS, UNSUPPORTED_FORMAT), so you can filter them later. Rows with a wall-clock time inside a daylight-saving gap or overlap are rejected unless you choose a DST policy.
Files, columns and exports
Open a CSV or TSV file. The delimiter is detected and you can choose the column that holds the timestamps. You can also paste a log, and "Extract from text" finds ISO dates, Common Log Format times, HTTP dates, UUIDs and 10/13/16/19-digit epochs. Conversion runs in a Web Worker so the page stays responsive, and you can cancel it at any time. CSV export escapes cells that would start a spreadsheet formula. JSON export includes a versioned manifest with your settings.
Questions
- How many rows can it handle?
- Up to 200,000 rows or 50 MB per run. 100,000 simple timestamps take about a second on a typical desktop.
- Is the file uploaded?
- No. The file is read by your browser and processed in a Web Worker on your device.
- Can I extract timestamps from log lines?
- Yes. Choose "Extract from text" to find timestamps inside free text and convert each match.