Paste one Unix timestamp per line. Supports seconds (10-digit), milliseconds (13-digit), microseconds (16-digit).
Paste one date per line. Accepts YYYY-MM-DD, YYYY-MM-DD HH:MM:SS, ISO 8601, or any JS-parseable date string.
Paste one Unix timestamp per line. Supports seconds (10-digit), milliseconds (13-digit), microseconds (16-digit).
Paste one date per line. Accepts YYYY-MM-DD, YYYY-MM-DD HH:MM:SS, ISO 8601, or any JS-parseable date string.
Convert large lists of Unix timestamps in bulk. Paste directly from log files, spreadsheets, or database exports. Supports automatic detection of seconds, milliseconds, and microseconds precision. Export results as CSV for use in Excel or Google Sheets.
Batch conversions often come from mixed logs, CSV exports, and analytics tools. Review the detected unit column before copying results. One row in milliseconds beside rows in seconds can shift dates by decades and make downstream reports unreliable.
When converting many rows for debugging, keep a UTC column in the export. Local time is useful for people, but UTC makes it easier to compare server logs, database records, queue events, and third-party API payloads.
Milliseconds vs seconds explains unit mistakes, while MySQL timestamp conversion and PostgreSQL timestamp conversion cover database workflows.