Batch Epoch Converter
How to Use
Paste one or more Unix timestamps, one per line or comma-separated. Each timestamp is converted to ISO 8601, UTC, and local time formats. Both seconds and milliseconds are auto-detected.
What is Unix Epoch Time?
Unix epoch time (also called POSIX time or Unix time) is a system for tracking time as a running total of seconds since January 1, 1970 00:00:00 UTC — known as the Unix epoch. This format is widely used in operating systems, databases, APIs, and log files because it is timezone-independent and easy to store as a single integer. This batch converter lets you decode multiple timestamps at once, saving time when working with large datasets.
Epoch Timestamps
Unix timestamps count the seconds (or milliseconds) since January 1, 1970 00:00:00 UTC. Values below 10^12 are treated as seconds; above as milliseconds. Invalid entries are marked with an error.
Common Use Cases
- Log analysis — convert timestamps from server logs to human-readable dates for debugging
- Database debugging — decode epoch values stored in database columns to verify data integrity
- API development — translate timestamp fields in API responses to confirm correct behavior
- Data migration — verify that timestamps are preserved accurately when moving between systems
- Incident investigation — quickly convert multiple timestamps from alerts and logs during outage analysis
Tips
You can paste timestamps in mixed formats — seconds and milliseconds can be combined in the same input. The tool auto-detects the precision of each value. If you see unexpected dates, check whether your timestamps are in seconds or milliseconds. Common sources like JavaScript's Date.now() return milliseconds, while many Unix command-line tools output seconds.
Privacy
All processing happens in your browser. No data is sent to any server.
FAQ
How does it tell seconds apart from milliseconds?
The tool auto-detects based on the magnitude of each value: anything below 10^12 is treated as seconds, and anything above as milliseconds. You can mix both in the same input and each value is detected independently.
Are the timestamps I paste sent to a server?
No. Both the batch conversion and the date formatting happen entirely in your browser. Your timestamps are never sent to a server, stored, or logged, so you can safely convert log and production data.
Is there a limit on how many timestamps I can convert at once?
There is no explicit count limit — you can paste many values, one per line or comma-separated. Because everything runs in the browser, extremely large inputs may make rendering a little slower.
What separators are supported and how are invalid values handled?
Both newline-separated and comma-separated input are supported. Entries that cannot be parsed as numbers are marked as 'Invalid', while the valid values are still converted.
Which time zone is used for the local time output?
In addition to ISO 8601 and UTC, the tool shows local time based on your browser's settings. UTC is always Coordinated Universal Time, which is useful when you want a value that doesn't shift by region.