Microsoft 365, AD and Windows · #35
Online AD Timestamp Converter
Converts AD's 18-digit FILETIME values to UTC and a chosen time zone, and dates back to FILETIME.
- Data is processed in your browser and not sent to a server
Tool
What does this tool do?
Most AD date attributes count 100-nanosecond intervals since 1601-01-01 (FILETIME). These are 64-bit numbers, so ordinary JavaScript numbers lose the last digits. The tool uses BigInt and shows attribute-specific special meanings such as 0 or the maximum value.
How to use it
- Paste the value: FILETIME (18 digits), Unix seconds/milliseconds or an ISO date (
2026-11-16T09:00:00Z). - Choose which attribute it comes from; special values are interpreted accordingly. Enter the time zone as an IANA name (
Europe/Berlin).
Fields
- Value
- FILETIME, Unix time or ISO 8601 date
- Attribute
- The meaning of special values like 0 and 9223372036854775807 depends on the attribute.
- Time zone
- IANA time zone name.
Worked example
| Input | Value |
|---|---|
| Value | 133801920000000000 |
| Attribute | lastLogonTimestamp |
| Time zone | Europe/Istanbul |
Expected result: 133801920000000000 → 2025-01-01T08:00:00Z, 11:00 in Istanbul; Unix 1735718400.
lastLogonTimestamp is replicated between domain controllers with a 9–14 day lag; do not expect day-level accuracy for 'last logon'. For the exact time use lastLogon on the relevant DC or the security log.
Method and assumptions
FILETIME → Unix ms: (value − 116444736000000000) / 10000, computed with 64-bit BigInt. Unix (9–11 digits seconds, 12–14 digits milliseconds) and ISO dates are also accepted; an ISO date without a time zone is taken as browser local time with a warning.
Special values: for accountExpires 0 and 9223372036854775807 mean 'never'; for pwdLastSet 0 means 'must change password at next logon'.
Using the result and troubleshooting
For stale account clean-up use lastLogonTimestamp with at least 14 days of uncertainty, e.g. 104 days for a 90-day threshold.
Limits and common mistakes
- Generalized Time values (
20261116090000.0Z) such as whenCreated are not decoded in this version.
Frequently asked questions
What is the difference between lastLogon and lastLogonTimestamp?
lastLogon is kept per DC and not replicated; lastLogonTimestamp is replicated but only updated at intervals.
Related tools and service
- userAccountControl DecoderSplits a userAccountControl number into flags and reads disabled, locked and expired state from the right source.
- Security Incident Timeline BuilderMerges EDR, firewall, SIEM and team notes into one sorted, time-zone-corrected timeline.
Related service: Server and Cloud Management