Batch Timestamp Converter

Paste a column of epoch values — or raw log lines containing them — and convert every row at once. Nothing is uploaded; the work happens in your browser, so it is safe to use on production data.

Raw log lines work too — the epoch-looking number on each line is picked out, so a leading date will not be mistaken for the timestamp.

Typical uses

  • Making a log extract readable before pasting it into a ticket.
  • Adding a human-readable column next to an exported database dump.
  • Checking whether a run of timestamps is evenly spaced, or has a gap where a job died.
  • Spotting rows that fell back to 0 — they show up immediately as 1970.

Reading the output

Each output line is the original value, a tab, then the converted form. Tabs mean a paste into a spreadsheet lands in two proper columns rather than one mangled one. Lines that could not be parsed are preserved and marked, so the output always has the same number of rows as the input — important when you are pasting a column back alongside the original data.

Mixed units in one column

Auto-detect resolves each line independently by digit count, so a column that mixes 10-digit and 13-digit values still converts correctly row by row. That happens more often than you would expect in tables written by more than one service. If you know the whole column shares a unit, set it explicitly — an explicit unit is more reliable than a heuristic for values near the digit boundaries, such as dates before 2001 in milliseconds.

Related tools

Frequently asked questions

How many timestamps can I convert at once?

There is no hard limit beyond your browser's memory. Tens of thousands of rows convert in well under a second because everything runs locally with no network round trip.

Is my data uploaded anywhere?

No. The conversion happens entirely inside your browser tab. Nothing you paste is transmitted to a server, which is what makes this safe to use on production log extracts.

What input formats does it accept?

One value per line, or a whole CSV column. The parser picks the epoch-looking number out of each line and ignores surrounding text, so you can paste raw log lines and still get usable output — a leading date such as 2024-01-01 will not be mistaken for the timestamp. Blank lines are skipped.

Can I get the result back as CSV?

Yes. The output is tab-separated so it pastes straight into Excel, Google Sheets or Numbers as proper columns, and there is a download button for a real .csv file.