Chrome Timestamp Converter
Convert Chrome/WebKit timestamps (microseconds since January 1, 1601 UTC) to and from regular dates - useful for reading Chrome history and cookie databases.
Recommended Settings
Pro Tips
- •Edit either the Chrome/WebKit timestamp or the date/time field - the other one updates automatically
- •Use the Copy buttons to grab any value in the format you need, including Unix seconds, milliseconds, or ISO 8601
- •Click Use Current Time to instantly see the current moment represented in this format
- •This runs entirely in your browser - nothing you enter is sent to a server
Most Popular
Most users paste in a raw value from a database or log file to see what date and time it actually represents
When to Use This Tool
Convert a raw Chrome/WebKit timestamp into a readable date and time.
Work backward from a known date to the equivalent Chrome/WebKit timestamp.
Quickly verify what a specific timestamp value actually represents.
Figure out why a timestamp value looks wrong by converting it to a human-readable date.
How It Works
Take the Chrome/WebKit timestamp you enter, which represents microseconds elapsed since January 1, 1601 UTC (the Windows/WebKit epoch)
Convert it to a standard Unix millisecond timestamp using the correct epoch offset and unit scale
Display the result in several common formats, and support converting in the opposite direction too
100% Private
Files never leave your device. All processing happens locally in your browser.
Lightning Fast
Powered by Client-side epoch arithmetic for optimal performance on modern browsers.
Open Source
Built with verified, open-source libraries. Fully transparent.
Frequently Asked Questions
What epoch does this format use?
Microseconds elapsed since January 1, 1601 UTC (the Windows/WebKit epoch).
Why would I need to convert this format?
Chrome and other Chromium-based browsers store timestamps in their SQLite databases (like History and Cookies) as microseconds since January 1, 1601, the same epoch used by Windows FILETIME values.
Is my data sent to a server?
No. All conversion happens entirely in your browser using JavaScript.
Does this account for timezones?
The underlying timestamp is timezone-independent (a single point in time), and the 'Date & Time' field shows it in your browser's local timezone alongside UTC for reference.
What if I enter an invalid value?
The tool will show a warning that the value doesn't look valid rather than silently displaying an incorrect date.