Forensic timestamp converter
Convert raw timestamps from Windows, Chrome, Apple, Unix and HFS+ into readable UTC dates, or turn a date into every format at once. It runs entirely in your browser: nothing you enter is uploaded.
Convert a timestamp
Loading the converter. If it does not appear, your browser needs JavaScript with BigInt support (any current browser).
Quick check only, provided as is. This is not validated forensic software. Verify any result you will rely on with your own validated tools, and record the method.
Download for offline or air-gapped use
Prefer not to trust a website? Download the tool as a single HTML file, read the code inside it, check its hash and open it in any browser on an offline machine. The file's own security policy blocks every network request, so it cannot load or send anything.
Download timestamp-converter-v1.0.0.html (13 KB)
SHA-256: 831f13b544ddde24b0f68847a1e8853b42a34a777a24777343f97b95dbe6d95b
Check the hash before use: sha256sum timestamp-converter-v1.0.0.html (Linux), shasum -a 256 timestamp-converter-v1.0.0.html (macOS) or certutil -hashfile timestamp-converter-v1.0.0.html SHA256 (Windows). All hashes are listed in SHA256SUMS.txt. Licence: MIT.
Worked example: the same moment in every format
All of these numbers are the same moment, 2026-11-16T14:30:00Z (16 November 2026, 14:30 UTC). The Windows FILETIME is 01DD75D6F5E72400 as a hex value, which appears as 00 24 E7 F5 D6 75 DD 01 in a hex editor.
| Format | What it counts | Value | Where you see it |
|---|---|---|---|
| Unix seconds | Seconds since 1 January 1970 UTC | 1794839400 | Linux and Android file system metadata (often with a separate nanoseconds field), many logs and databases |
| Unix milliseconds | Milliseconds since 1 January 1970 UTC | 1794839400000 | JavaScript and Java; often found in Android app databases and web APIs |
| Unix nanoseconds | Nanoseconds since 1 January 1970 UTC | 1794839400000000000 | APFS file system metadata (Apple's current file system uses the Unix epoch, not 2001), some Linux and Go logs |
| Windows FILETIME | 100-nanosecond intervals since 1 January 1601 UTC | 134393130000000000 | NTFS metadata, the Windows registry, event logs, LNK files |
| Chrome/WebKit time | Microseconds since 1 January 1601 UTC | 13439313000000000 | Chrome and Edge history, cookies and downloads databases |
| Apple Cocoa / Mac Absolute Time | Seconds since 1 January 2001 UTC | 816532200 | Many iOS and macOS app databases, Safari history |
| Apple Cocoa time in nanoseconds | Nanoseconds since 1 January 2001 UTC | 816532200000000000 | Some newer iOS databases, for example the Messages database from iOS 11 |
| HFS+ time | Seconds since 1 January 1904 UTC | 3877684200 | HFS+ file dates (the volume header creation date is local time, and the original HFS format used local time throughout) |
Checks before you rely on a result
- Confirm the format from the source, not the number of digits. Digit counts overlap: 9 digits can be Apple Cocoa seconds; 10 digits can be Unix seconds or HFS+; 13 Unix milliseconds; 16 Unix microseconds; 17 Chrome/WebKit; 18 Windows FILETIME or Apple Cocoa nanoseconds; 19 Unix nanoseconds (APFS). The wrong choice often still gives a plausible date, so check the artefact's documented format.
- Confirm the time zone. Most formats store UTC, but some do not (for example the HFS+ volume creation date).
- A timestamp records what the system's clock said, not necessarily the true time. Check for clock drift or a deliberately changed clock.
- Record the method and verify important results with validated tools.
Timestamp converter: questions
What is a forensic timestamp converter?
It turns the raw numbers that operating systems, browsers and apps store for dates into readable dates and times. Different systems count from different starting points (epochs) and in different units, so the same moment can be stored as very different numbers.
Is anything I enter uploaded?
No. The converter runs entirely in your browser and nothing you type is sent to this site or stored by it. We set no cookies. You can disconnect from the internet after the page loads and it still works, or download the offline copy below. Browser extensions and your own device are outside our control, so follow your organisation's rules for case data.
Why does Windows count from 1601?
Windows FILETIME counts 100-nanosecond intervals from 1 January 1601 UTC, the start of a 400-year Gregorian calendar cycle, which keeps leap-year arithmetic simple. Chrome and WebKit use the same 1601 starting point but count microseconds.
What is the difference between the FILETIME hex value and the bytes as stored?
Windows stores FILETIME as a 64-bit little-endian number, so in a hex editor the bytes appear in reverse order. Choose the little-endian input if you copied the bytes straight from a hex view, or the value input if a tool has already shown the number.
Which time zone are the results in?
The main result is UTC. The converter also shows the same moment in your device's time zone. Most of these formats store UTC, but some do not: the HFS+ volume creation date and the original Mac HFS format use local time. Check what the source system did before relying on a result. The device time zone line is for display only and drops fractions of a second.
Can I rely on this for a report or court?
Treat it as a quick check, not validated forensic software. Verify important results with your own validated tools and record the method you used. Nothing here is legal advice.