Development

FILETIME & LDAP Timestamp Converter

Free online FILETIME and LDAP/Active Directory timestamp converter. Convert 18-digit Windows FILETIME, 64-bit Hex, or byte sequences to dates and back with zero network uploads.

Free to use No sign-up Runs in your browser

Tool workspace

Current FILETIME (updates every 10s)
Unix:
ISO 8601 (UTC)
2025-01-01T00:00:00.000Z
UTC String
Wed, 01 Jan 2025 00:00:00 GMT
Local Time
1/1/2025, 12:00:00 AM
Unix Timestamp (s)
1735689600
Unix Timestamp (ms)
1735689600000
FILETIME (100ns ticks)
133801632000000000
Hexadecimal (64-bit)
0x01DB5BE019BA4000
Win32 DWORDs (Low, High)
431636480 (0x19BA4000), 31153120 (0x01DB5BE0)

What Is a FILETIME / LDAP Timestamp?

A FILETIME (also known as an LDAP or Active Directory timestamp) is a 64-bit value representing the number of 100-nanosecond intervals since January 1, 1601 (UTC). It is used extensively in Microsoft Windows APIs, NTFS file system metadata, Active Directory, and LDAP directory attributes such as 'whenCreated', 'pwdLastSet', 'accountExpires', and 'lastLogonTimestamp'. The timestamp is stored as an 18-digit decimal number — for example, 133801632000000000 represents January 1, 2025 00:00:00 UTC. Unlike Unix timestamps (which count seconds since 1970), FILETIME uses a much earlier epoch and a much finer resolution (100-nanosecond ticks).

How to Use the FILETIME Converter

  1. 1To convert FILETIME to a date: enter the 18-digit decimal value, a 64-bit hex string (with or without 0x prefix), or little-endian bytes. The tool instantly displays the corresponding date in ISO 8601, UTC, local time, and Unix timestamp formats.
  2. 2To convert a date to FILETIME: switch to the 'Date to FILETIME' tab, paste any valid ISO/datetime string or select fields with dropdowns, then read the generated FILETIME value.
  3. 3The live clock at the top shows the current FILETIME and Unix timestamp, updating every 10 seconds.
  4. 4Click the copy button next to any value to copy it to your clipboard.

Common Use Cases

Active Directory Troubleshooting

Decode AD attributes like 'pwdLastSet', 'accountExpires', 'lastLogonTimestamp', and 'lockoutTime' to understand when events occurred.

NTFS File System Analysis

Convert NTFS file timestamps ($MFT records, $STANDARD_INFORMATION, $FILE_NAME) during forensic analysis or file recovery.

Windows API Development

Debug FILETIME values returned by Windows APIs like GetFileTime(), GetSystemTimeAsFileTime(), and FindFirstFile().

LDAP Query Interpretation

Translate 18-digit timestamps from LDAP search results into human-readable dates for reporting and auditing.

Frequently asked questions

What is the difference between FILETIME and Unix timestamp?

Unix timestamps count seconds since January 1, 1970 (UTC). FILETIME counts 100-nanosecond intervals since January 1, 1601 (UTC). To convert: Unix_seconds = (FILETIME - 116444736000000000) / 10000000.

How can I get or parse FILETIME via command line?

In PowerShell, run: [DateTime]::FromFileTimeUtc(133801632000000000) to decode, or [DateTime]::UtcNow.ToFileTimeUtc() to get the current timestamp. In Linux/macOS bash: echo $(( (133801632000000000 - 116444736000000000) / 10000000 )) | xargs -I{} date -u -d @{}.

What do 0 and 9223372036854775807 (0x7FFFFFFFFFFFFFFF) mean in Active Directory?

Both are sentinel values. In Active Directory 'accountExpires', 0 and 9223372036854775807 mean 'Never Expires'. In 'pwdLastSet', 0 indicates that the user must change password at next logon. In 'lockoutTime', 0 indicates the account is not locked out.

How do I troubleshoot hexadecimal or raw byte FILETIME strings?

Windows tools like Procmon, Volatility, or Registry export 64-bit values as hex (e.g. 0x01DA42E973C91400) or little-endian bytes (e.g. 00 14 c9 73 e9 42 da 01). Souus Tools parses all these formats automatically without requiring manual endianness swaps.