Chrome (WebKit) timestamp to date
For example, 13385836800000000 is Fri, Mar 07, 2025, 04:00:00 PM UTC, which is 2025-03-07T16:00:00.000Z in ISO 8601 and 1741363200 in Unix seconds.
Microseconds since 1601-01-01T00:00:00 UTC, the timestamp format of Chrome, Chromium, and Safari browser databases.
Detected: WebKit / Chrome timestamp/t/13385836800000000
Your timezone
UTC · GMT+00:00 · UTC
Fri, Mar 07, 2025, 04:00:00 PM
Common formats
UTC
Fri, Mar 07, 2025, 04:00:00 PM
ISO 8601
2025-03-07T16:00:00.000Z
Unix (seconds)
1741363200
Unix (millis)
1741363200000
Relative
…
Chrome, Chromium, and Edge store times in their History and Cookies SQLite databases as microseconds since January 1, 1601: a 17-digit number often called a WebKit timestamp. It's a staple of browser forensics and of anyone poking at their own profile data. Paste one below to decode it.
Do it with the API
curl https://parsetime.dev/api/t/13385836800000000?format=webkitThe same conversion as JSON: no key, no signup, permissive CORS. Try this call or read the API docs.
Common questions
- Where do WebKit timestamps appear?
- The visits.visit_time and urls.last_visit_time columns of Chrome's History database, cookie creation and expiry times, download records, and equivalent tables in Chromium-based browsers like Edge, Brave, and Opera.
- How is this different from a Unix timestamp in microseconds?
- Same unit, different zero: WebKit counts from 1601, Unix from 1970. The difference is a constant 11644473600 seconds. A 2026 Unix-microseconds value has 16 digits; the WebKit form has 17.
- How do I convert it in SQL?
- In SQLite: datetime(visit_time / 1000000 − 11644473600, 'unixepoch') turns a Chrome visit_time into a readable UTC date.