Chrome & WebKit Timestamp Converter. Microseconds Since 1601

Where these values come from

The WebKit epoch (1601-01-01) is the same reference Windows uses for FILETIME, Chromium adopted it for a handful of internal clocks, notably the last_visit_time and cookie timestamp columns in the old Chrome SQLite databases, so forensics and data-recovery tools regularly meet 16-digit values like 13430534400000000 that are neither Unix seconds nor ticks.

The conversion is: Unix time = value / 1,000,000 − 11,644,473,600 seconds. Divide the microseconds to seconds, subtract the 1601→1970 gap. The "Now" button shows the current instant in the same format.

Worked examples

• 13430534400000000 µs since 1601 → Aug 7, 2026 00:00:00 UTC — divide by 1e6 (13,430,534,400 s), subtract 11,644,473,600 → Unix 1,786,060,800.
• 12823142400000000 → Jan 1, 2007 00:00:00 UTC, the classic "start of 2007" probe value used in browser-forensics write-ups.
• Aug 7, 2026 12:00:00 UTC → 13430538000000000 µs — the reverse direction, plus the equivalent 100ns FILETIME ticks.

FILETIME, WebKit, and .NET, one family

Windows FILETIME counts 100-nanosecond ticks since 1601; WebKit counts microseconds since 1601, exactly ten times coarser. Both are handled here: every output row shows the value as µs and as 100ns ticks, so a value from either world converts in the same box. The LDAP / Active Directory converter covers the same 1601 epoch for Active Directory attributes.

Gotchas

• µs, not ms. One extra decimal place is easy to miss. A value that decodes to year 292 million instead of 2026 is in milliseconds, the converter flags values out of the sane range.
• Not the .NET ticks epoch.NET counts 100ns ticks since year 1, so values are ~621 trillion ticks larger. Different constant, different converter (here).
• Column context matters. The same column family appears in cookies, history, and downloads; always confirm which field you read before trusting the date.

Related tools

For the 1601 epoch in 100ns ticks see the LDAP / AD timestamp converter; for year-1 ticks use the .NET ticks converter. Once you have Unix seconds, the timestamp-to-date converter formats them in any timezone.