Epoch & Unix Timestamp Converter
Two-way Unix timestamp converter with live system clock and client-side bulk log/CSV batch conversion.
Unix Timestamp → Human Date
Auto-detects s / ms / µs / nsHuman Date → Unix Timestamp
Local TimezoneBulk Timestamp Batch Converter
Paste a column of timestamps or drop a CSV/Log file to convert hundreds of entries at once.
| Timestamp | Read as | UTC Time | Local Time |
|---|---|---|---|
| Paste timestamps on the left or upload a file to view batch conversions. | |||
Intelligent Precision Detection
Automatically resolves Unix seconds, JavaScript milliseconds, microseconds and nanoseconds (including decimals and negative values) and tells you which one it assumed.
Bulk Column Conversion
Drop raw database exports, server logs, or CSV dumps to parse thousands of records in local memory in milliseconds.
Zero Telemetry & Private
No log data or server timestamps ever leave your browser. All string parsing and mathematical formatting execute client-side.
Frequently Asked Questions
What is a Unix epoch timestamp?▼
A Unix epoch timestamp is the count of elapsed seconds (or milliseconds) since 00:00:00 UTC on January 1, 1970 (the Unix Epoch), excluding leap seconds. It is a universal standard for storing timestamps in databases and system logs.
How does the converter distinguish seconds from milliseconds?▼
It counts the digits in the whole-number part. Up to 11 digits is read as seconds (10 digits is the usual form, e.g. 1700000000), 12 to 13 digits as milliseconds (e.g. 1700000000000, as used by JavaScript), 14 to 16 as microseconds and 17 to 19 as nanoseconds. A note under the box always tells you which unit it assumed. Decimals such as 1700000000.123 (seconds with a fraction, as many logs and Python's time.time() produce) are supported.
Why does my number show an error or a surprising date?▼
The box accepts digits with an optional minus sign and decimal point, so letters, exponents (1e9) and hex (0x...) are refused. A number with more than 19 digits is longer than any Unix timestamp. An 11-digit value is read as seconds, which gives a date between the years 2286 and 5138. If you actually meant a millisecond timestamp from the first few years of 1970 to 1973, those are the only values this rule cannot tell apart from seconds.
Can I paste an entire spreadsheet column or log file?▼
Yes. Switch to the 'Batch & Bulk Converter' tab to paste raw log outputs or spreadsheet columns, or upload a .csv/.txt file. All conversions execute 100% locally in browser memory without sending data to an external server.