EpochLab

Batch decode

A whole column at a time

Each row is detected on its own, so a paste mixing Unix seconds, ISO strings and FILETIME all works. Log lines get the timestamp pulled out of the noise.

Decoding a whole paste at once

Paste a column from a spreadsheet, a list of IDs from a database, or a chunk of a log file. Put one value or one log line on each line. The page reads every line on its own, so a paste that mixes Unix seconds, milliseconds and ISO dates still works.

Log lines are messy, so the decoder hunts for timestamps inside them. It finds ISO dates, web server log dates and long runs of digits, and it can pull out every match on a line, not just the first. A line with a start and an end gives you both.

Each result shows the line it came from and where on that line it was found, so you can trace any row back. A timeline puts every instant on one axis, which makes gaps and outliers easy to spot. You can drop duplicates and sort by time.

When you are done, copy the table as CSV, TSV, Markdown or JSON and paste it where you need it. Lines that could not be read are listed apart, with a hint as to why.

Questions people ask

How many lines can I paste?

Hundreds or thousands is fine. It all runs in your browser, so the only limit is your machine. Very large logs are faster if you trim them to the part you care about first.

Can one list mix seconds and milliseconds?

Yes. Each line is judged by itself, from its digit count and the date it gives. You do not have to tell the page which unit a line is in.

Why was one of my lines skipped?

Most often the number was cut short, the date was in a local format the page could not be sure of, or the line held no timestamp at all. Skipped lines are shown at the bottom so you can check them.

Can I choose which columns to export?

Yes. Pick the output columns you want, such as UTC, local time, ISO 8601 or the raw value, and the copied table uses just those.