Windows FILETIME to date converter
FILETIME values appear in the Windows registry, forensic artifacts and event logs. Enter one to see its date.
Loading the tool…
Processing and privacy: The result is calculated inside your browser and your data is not sent to any server.
How to use it
- Enter filetime value, value format and time zone (optional).
- The result appears straight away and updates as you edit.
- Copy the result, or copy a link that keeps the same values to share it.
How it is calculated
FILETIME counts 100-nanosecond intervals since 1601-01-01 00:00:00 UTC. Unix seconds = (FILETIME - 116444736000000000) / 10000000.
Example
Inputs: FILETIME value = 134352864000000000, Value format = Decimal, Time zone (optional) = Riyadh (Saudi Arabia). Result: Date and time (UTC): 2026-10-01 00:00:00; Weekday: Thursday.
134352864000000000
2026-10-01 00:00:00
Limits and caveats
- A hex value must be the whole number, not the reversed little-endian bytes shown in a registry editor.
- FILETIME is UTC by design, but some programs store local time in it, so check the source.
Questions about this tool
Why does FILETIME start in 1601?
It is the start of a 400-year Gregorian cycle, which keeps the leap year math in Windows simple.
How do I convert a value from the registry?
If it appears as bytes like 00 C0 46 CD 37 51 DD 01, reverse them to 01DD5137CD46C000 and choose hex.
How is FILETIME different from an LDAP timestamp?
They are the same number from the same epoch. Active Directory stores it in decimal in attributes such as lastLogonTimestamp.