Skip to main content
Tool Factory

Date & Time

Windows Filetime to UNIX Timestamp Converter

Calculate or transform time data with Windows Filetime to UNIX Timestamp. Enter the date or time values, choose the format, then review the result.

Tool workspace

Your input stays in this browser.

Add the required input to continue.

Needs input

You can run the tool again after any change.

Options

Your result appears here

Calculate or transform time data with Windows Filetime to UNIX Timestamp. Enter the date or time values, choose the format, then review the result.

This tool runs open-source code from CyberChef by GCHQ (Apache License 2.0). See open-source credits.

Windows Filetime to UNIX Timestamp Converter: Convert Windows FILETIME ticks to Unix time in seconds, milliseconds, microseconds, or nanoseconds. FILETIME counts 100-nanosecond intervals from January 1, 1601 UTC. The converter preserves exact fractional Unix values.

The result is an exact Unix timestamp in the selected units. Fractional Unix values can represent whole FILETIME ticks.

  • Compare numeric Windows file timestamps with Unix timestamps in logs.
  • Convert decimal and hexadecimal FILETIME values without losing 100-nanosecond precision.
  • Check the epoch offset and byte order of an extracted numeric timestamp.

Sources: Microsoft FILETIME structure; Microsoft FileTimeToSystemTime range

Instructions

  1. Enter one numeric FILETIME value. Choose its Decimal or Hex input format.
  2. For Hex formats, omit the 0x prefix and use the correct byte order. Prefer complete byte pairs for little endian.
  3. Choose the Unix output units. One tick equals 0.0000001 seconds or 100 nanoseconds.
  4. Check the result, then use Copy result. FILETIME 116444736000000001 produces 0.0000001 Unix seconds.

Example

Input: 133444736000000000

Settings: Output units Seconds (s), Input format Decimal

Result: 1700000000

Output units Milliseconds (ms) returns 1700000000000 for the same input.

Limits

  • The converter accepts whole FILETIME counts from 0 through 18446744073709551615.
  • The full raw storage range differs from Windows API limits. FileTimeToSystemTime requires values below 0x8000000000000000.
  • This tool performs numeric epoch arithmetic. It does not interpret special Windows API sentinel values or convert ticks to calendar dates.
  • Input allows at most 4096 characters. Decimal scientific notation uses exponents from -10000 through 10000.

Questions

How do I convert FILETIME to Unix time?

Select the FILETIME input format and Unix output units. Enter one numeric tick count. FILETIME 116444736000000000 equals Unix 0 seconds.

Does the converter preserve 100-nanosecond precision?

Yes. FILETIME 116444736000000001 produces 0.0000001 Unix seconds or 100 Unix nanoseconds. The result keeps exact fractional Unix values.

Which FILETIME values does this tool accept?

Enter whole numeric tick counts from 0 through 18446744073709551615. The converter rejects negative counts, fractional ticks, and larger values.

Should I include 0x in Hex input mode?

No. Omit the prefix in Hex modes. Choose big endian or little endian to match the stored byte order. Prefer complete byte pairs for little endian.

Why does FILETIME 0 produce a negative Unix timestamp?

FILETIME starts on January 1, 1601 UTC. Unix time starts on January 1, 1970 UTC. FILETIME 0 therefore equals -11644473600 Unix seconds.

Does the tool interpret Windows sentinel values?

No. The tool treats input as numeric epoch ticks. Some Windows APIs give particular bit patterns special meanings. Check those API rules separately.

Why can a valid numeric value fail FileTimeToSystemTime?

That API requires a value below 0x8000000000000000. This numeric converter supports the full unsigned 64-bit storage range, which extends beyond that API limit.