Epoch to DateTime — Unix Timestamp Converter Across Timezones
Convert Unix epoch timestamps to date and time across 6 timezones (UTC, Los Angeles, New York, London, Tokyo, Shanghai). Auto-detects seconds vs milliseconds. 100% local, no upload.
Epoch to DateTime
Convert Unix epoch timestamps to human-readable dates across timezones. Everything runs in your browser.
| Timezone | Date / Time | Offset |
|---|---|---|
| UTC | 1970-01-01, 00:00:00 | GMT (+0 local) |
| Los Angeles (PST/PDT) | 1969-12-31, 16:00:00 | GMT-8 (+0 local) |
| New York (EST/EDT) | 1969-12-31, 19:00:00 | GMT-5 (+0 local) |
| London (GMT/BST) | 1970-01-01, 01:00:00 | GMT+1 (+0 local) |
| Tokyo (JST) | 1970-01-01, 09:00:00 | GMT+9 (+0 local) |
| Shanghai (CST) | 1970-01-01, 08:00:00 | GMT+8 (+0 local) |
| UTC seconds | 0 | 10-digit |
| UTC milliseconds | 0 | 13-digit |
{ “title”: “Epoch to DateTime — Unix Timestamp Converter Across Timezones”, “description”: “Convert Unix epoch timestamps to date and time across 6 timezones (UTC, Los Angeles, New York, London, Tokyo, Shanghai). Auto-detects seconds vs milliseconds. 100% local, no upload.”, “category”: “dev”, “relatedTools”: [ “epoch-to-date”, “date-to-epoch”, “timestamp-diff”, “cron-generator” ], “platforms”: [ “mac”, “windows”, “linux”, “web” ], “howTo”: [ { “title”: “Open the tool”, “body”: “Open the tool page at /tools/epoch-to-datetime in your browser. The interface loads from your device — nothing is fetched from a server.” }, { “title”: “Read the byte-level inputs”, “body”: “Each control is wired to a JavaScript handler that processes input locally. Drop a file or paste a value and the work runs immediately.” }, { “title”: “Download the result”, “body”: “When the result is ready, click Download or Copy to grab it. The output stays on your device; close the tab and it is gone.” } ], “faq”: [ { “q”: “How does the Epoch to DateTime work in my browser?”, “a”: “All the processing for /tools/epoch-to-datetime is implemented in JavaScript and WebAssembly. We open the file or input locally with the FileReader API or a paste, process it in JavaScript on the same page, and produce the result without ever uploading the file to a server. The work happens on your device, not ours.” }, { “q”: “Is the input file uploaded to any server?”, “a”: “No. Every tool on ToolConvoy processes files strictly in your browser. Network requests never carry your input. You can verify this by opening the Network tab of your browser’s developer tools while using the tool — you will see only the initial page load.” }, { “q”: “What happens to my file after I close the tab?”, “a”: “All data lives in browser memory while the tab is open. Closing the tab releases that memory. There is no server-side storage, no analytics database, no logging of file contents.” }, { “q”: “Does this tool work offline?”, “a”: “Once the page loads, all processing continues to work offline. Subsequent page navigations may require a network connection if you move to a different route.” } ], “limitations”: [ { “label”: “Browser memory limits”, “detail”: “For very large inputs (hundreds of MB), the browser tab may run out of memory. The /tools/epoch-to-datetime tool runs in the same JavaScript runtime as your other tabs.” } ], “platformNotes”: [ { “platform”: “web”, “note”: “All processing happens in the browser tab. Open in any modern browser on any OS.” }, { “platform”: “mac”, “note”: “Safari and Chrome work. Use Cmd+V to paste input from clipboard.” }, { “platform”: “windows”, “note”: “Edge, Chrome, Firefox supported.” }, { “platform”: “linux”, “note”: “Any modern browser with JavaScript and FileReader API support.” } ], “updated”: “2026-08-01” }
How to use
Open the tool
Open the tool page at /tools/epoch-to-datetime in your browser. The interface loads from your device — nothing is fetched from a server.
Read the byte-level inputs
Each control is wired to a JavaScript handler that processes input locally. Drop a file or paste a value and the work runs immediately.
Download the result
When the result is ready, click Download or Copy to grab it. The output stays on your device; close the tab and it is gone.
Frequently asked
How does the Epoch to DateTime work in my browser?
All the processing for /tools/epoch-to-datetime is implemented in JavaScript and WebAssembly. We open the file or input locally with the FileReader API or a paste, process it in JavaScript on the same page, and produce the result without ever uploading the file to a server. The work happens on your device, not ours.
Is the input file uploaded to any server?
No. Every tool on ToolConvoy processes files strictly in your browser. Network requests never carry your input. You can verify this by opening the Network tab of your browser's developer tools while using the tool — you will see only the initial page load.
What happens to my file after I close the tab?
All data lives in browser memory while the tab is open. Closing the tab releases that memory. There is no server-side storage, no analytics database, no logging of file contents.
Does this tool work offline?
Once the page loads, all processing continues to work offline. Subsequent page navigations may require a network connection if you move to a different route.
Limitations
- Browser memory limitsFor very large inputs (hundreds of MB), the browser tab may run out of memory. The /tools/epoch-to-datetime tool runs in the same JavaScript runtime as your other tabs.
Platform notes
- Web
- All processing happens in the browser tab. Open in any modern browser on any OS.
- macOS
- Safari and Chrome work. Use Cmd+V to paste input from clipboard.
- Windows
- Edge, Chrome, Firefox supported.
- Linux
- Any modern browser with JavaScript and FileReader API support.