TOOLTIKI Lovable tool, really free
Date & time Timestamps

Windows FILETIME converter

Value
Reading it as
UTC date and time 2023-11-14T22:13:20Z
Readable Tue, 14 Nov 2023 22:13:20 GMT
Unix seconds 1,700,000,000
Unix milliseconds 1,700,000,000,000
Windows FILETIME 133,444,736,000,000,000
.NET ticks 638,355,968,000,000,000
Excel serial 45,244.925926
Mac HFS+ seconds 3,782,844,800
Note
Local · 0 and the maximum both mean “never”
Advertisement
320 × 100

A Windows FILETIME counts 100-nanosecond intervals since 1 January 1601 UTC. It turns up in file metadata, the registry and Active Directory.

How to use the windows filetime converter

1 Paste the value. Every other epoch is shown alongside the date.
2 Change what it is being read as if the number is from a different system.
3 All times are UTC — convert to your own zone separately if you need local time.

The 1601 epoch is not arbitrary: the Gregorian calendar repeats on a 400-year cycle, and 1601 was the start of the first full cycle before Windows NT was designed, which made date arithmetic simpler. The tick size of 100 nanoseconds is a compromise that gives good precision while still spanning about 58,000 years in a 64-bit integer. In practice you meet FILETIME values as an eighteen-digit number in a registry export or an LDAP attribute — and the same encoding is what Active Directory uses for `lastLogonTimestamp`, `pwdLastSet` and `accountExpires`. A value of 0 means never, and 9223372036854775807 also means never, which is worth knowing before treating it as a date in the year 30828.

Questions

The Gregorian calendar repeats every 400 years, and 1601 began the first full cycle before NT was designed. It made the arithmetic easier.

Microsoft — FILETIME structure
Advertisement
300 × 250
Was this tool any good?
INTERNAL SIGNAL ONLY · WE USE IT TO FIND TOOLS WORTH REBUILDING