File & System Timestamp Converter

Decode timestamps from files, metadata, and different operating systems. Convert Windows FILETIME, Mac OS times, and other formats to standard dates.

File Timestamp Converter

Convert between Unix timestamps and human-readable dates

Input Format

Output Format

Input Timestamps

Converted Timestamps

Quick Reference

Unix Timestamp:

Seconds since Jan 1, 1970

Example: 1705312200

Unix MS:

Milliseconds since Jan 1, 1970

Example: 1705312200000

How It Works

This file timestamp converter translates file system timestamps from various formats (Windows FILETIME, Mac OS time, Unix time) into human-readable dates.

The conversion process:

Format detection: Identify the timestamp format based on its magnitude and structure.
Epoch normalization: Convert the input to a standard internal representation (Unix timestamp).
Date formatting: Transform the normalized timestamp into a human-readable date string.
Multiple format output: Display the result in various common formats for flexibility.

Different operating systems store file timestamps differently - Windows uses FILETIME (100-nanosecond intervals since 1601), while Unix uses seconds since 1970.

When You'd Actually Use This

Digital Forensics

Analyze file creation and modification times from different operating systems during investigations.

Cross-Platform Development

Understand file timestamps when working with files shared between Windows, Mac, and Linux systems.

Backup System Analysis

Interpret timestamps from backup metadata to understand when files were actually backed up.

File System Debugging

Troubleshoot file synchronization issues by comparing timestamps across different systems.

Archive Extraction

Verify file dates when extracting archives that preserve original timestamps from different platforms.

Metadata Extraction

Read and interpret embedded timestamps in file metadata for documentation or compliance purposes.

What to Know Before Using

Different epochs for different systems

Windows FILETIME starts at 1601, Unix at 1970, Mac OS Classic at 1904. The converter handles these automatically.

Timezone affects displayed time

The underlying timestamp is UTC, but the readable date may be shown in your local timezone.

File system precision varies

Some file systems store timestamps with second precision, others with nanosecond precision.

NTFS stores three timestamps per file

Created, Modified, and Accessed times. Each may have different values depending on file operations.

Network transfers can alter timestamps

Copying files over networks or between file systems may change or lose timestamp information.

Common Questions

What is Windows FILETIME format?

FILETIME counts 100-nanosecond intervals since January 1, 1601 UTC. It's a 64-bit value used by Windows NT-based systems.

How do I get a file's timestamp?

Windows: Right-click > Properties. Mac: Get Info. Linux: stat command. Or use file explorer details view.

Why are my file timestamps wrong after copying?

Some copy operations preserve timestamps, others set them to the copy time. Use tools that preserve metadata if needed.

What's the Mac OS timestamp format?

Classic Mac OS used seconds since January 1, 1904. macOS (Unix-based) uses standard Unix timestamps since 1970.

Can timestamps be faked?

Yes, tools exist to modify file timestamps (touch command, Timestomp). Don't rely solely on timestamps for security.

What's the difference between created and modified time?

Created: when the file was first made. Modified: when content last changed. Accessed: when the file was last read.

Do timestamps survive cloud uploads?

Often not. Cloud services may set upload time as the timestamp. Check your service's documentation.

Other Free Tools

Search tools