Tool Files & Artifacts
Windows Artifact Reader
Read a Prefetch file, a shortcut, a Recycle Bin $I file, or a carved MFT or USN record. It detects which one you dropped.
The small Windows files that prove a program ran or a file existed: Prefetch, shortcuts, Recycle Bin index files, and NTFS records. Drop one in and the page reads its signature, picks the parser, and lays out the fields that matter.
This runs in your browser. Nothing you type or open is uploaded.
How to read it
Prefetch proves execution, with a run count and up to eight last-run times on Windows 8 and later. Shortcuts prove a file was opened, and they remember the volume serial and full path even after the target is gone.
A $I file keeps the original path, size and deletion time of something in the Recycle Bin. The MFT and USN tab compares the two sets of NTFS timestamps, which is how timestomping is usually caught.
Every tab has a sample. Load it to see what a finished reading looks like before you trust your own file.
Tab by tab
Prefetch
Read a Windows Prefetch file for the executable name, run count and last run times. Prefetch is one of the few artifacts that shows a program actually ran.
Windows 10 and 11 files are MAM-compressed with LZXPRESS Huffman, and this tool does not decompress them on purpose. A subtly wrong decoder would emit plausible names and times, which is worse than none. Decompress them first, then paste the result.
Version 26 and later keep up to eight run times. The run count can be higher than the slots shown.
The path hash in the file name is computed from the executable's full path. Two prefetch files for the same name with different hashes mean two copies in different folders.
| Version | Windows | Storage | Run-time slots | Read here |
|---|---|---|---|---|
| 17 | Windows XP, Windows Server 2003 | uncompressed | 1 | yes |
| 23 | Windows Vista, Windows 7 | uncompressed | 1 | yes |
| 26 | Windows 8, Windows 8.1 | uncompressed | 8 | yes |
| 30 | Windows 10 | mam-compressed | 8 | no |
| 31 | Windows 11 | mam-compressed | 8 | no |
Shortcut (LNK)
Read a Windows shortcut byte by byte against the MS-SHLLINK spec. Windows writes .lnk files on its own for recently opened documents, so they record files a user opened even after the file or the USB stick is gone.
Resolved target is the full path the shortcut points at. A drive type of removable or a UNC path is a lead for USB or lateral movement work.
The volume serial ties the shortcut to one specific disk. Match it against the registry's MountedDevices and the USB keys.
The three times belong to the target as it was when the shortcut was made, not to the shortcut file itself.
Recycle Bin
Decode a Recycle Bin $I file into the original path, size and deletion time. Sending an item to the Recycle Bin renames it into $Recycle.Bin and writes this small index file beside it.
The folder above the $I file is named for the user's SID. That tells you who deleted it.
The $R file with the same suffix holds the original content. It has no header, so there is nothing to parse, only to recover.
Version 1 is Vista to 8.1 and version 2 is Windows 10 and later. The tool reports the version it found and rejects any other.
MFT and USN
Parse one carved MFT FILE record or USN journal record and line up the timestamps that matter. This is for one record at a time, pulled out with MFTECmd, a carver or a hex editor.
Every file has two sets of timestamps. $STANDARD_INFORMATION is what Explorer shows and what timestomping tools change. $FILE_NAME is updated by NTFS itself and is rarely forged.
A $SI time earlier than its $FN partner by more than a couple of seconds is the classic timestomping lead. It is a lead, since some copy tools cause it too.
A USN record's reason flags say what happened: create, rename, data overwrite, delete. Read them in order across records to rebuild a file's life.
| Flag | What it records |
|---|---|
| DATA_OVERWRITE | The data in the file or directory was overwritten. |
| DATA_EXTEND | The file or directory was extended (data added). |
| DATA_TRUNCATION | The data in the file or directory was truncated. |
| NAMED_DATA_OVERWRITE | The data in an alternate data stream was overwritten. |
| NAMED_DATA_EXTEND | An alternate data stream was extended (data added). |
| NAMED_DATA_TRUNCATION | An alternate data stream was truncated. |
| FILE_CREATE | The file or directory was created for the first time. |
| FILE_DELETE | The file or directory was deleted. |
| EA_CHANGE | The extended attributes for the file or directory changed. |
| SECURITY_CHANGE | The access rights (security descriptor) for the file or directory changed. |
| RENAME_OLD_NAME | The file or directory was renamed. This is the record for the old name. |
| RENAME_NEW_NAME | The file or directory was renamed. This is the record for the new name. |
| INDEXABLE_CHANGE | A user changed whether the file or directory is indexed for content searching. |
| BASIC_INFO_CHANGE | A change was made to attributes or timestamps (creation, last access, last write). |
| HARD_LINK_CHANGE | A hard link was added to or removed from the file or directory. |
| COMPRESSION_CHANGE | The compression state of the file or directory changed. |
| ENCRYPTION_CHANGE | The file or directory was encrypted or decrypted. |
| OBJECT_ID_CHANGE | The object identifier for the file or directory changed. |
| REPARSE_POINT_CHANGE | The reparse point for the file or directory changed, or a reparse point was added or removed. |
| STREAM_CHANGE | A named stream was added to or removed from the file, or a named stream was renamed. |
| TRANSACTED_CHANGE | The given stream change was made as part of a transaction. |
| INTEGRITY_CHANGE | The integrity state of the file or directory changed (ReFS/Storage Spaces). |
| CLOSE | The handle used to make changes was closed. The reasons in this record are final for that handle. |
Terms behind it
- Prefetch: A Windows artifact proving a program ran, and when.
- LNK Files: Windows shortcut files that embed rich metadata about their target.
- Recycle Bin ($I / $R): Per-user deleted-file store pairing metadata ($I) with recoverable content ($R).
- Master File Table: The NTFS index of every file, and a goldmine of timestamps.
- USN Journal: NTFS log of per-file change records, used to reconstruct activity.
- Timestomping: Forging file timestamps to hide when something really happened.
- MAC(b) Times: The Modified, Accessed, metadata-Changed, and Born timestamps of a file.
Sources
- [MS-XCA] Xpress Compression Algorithm: Microsoft Learn. Microsoft's own published specification for the LZ77+Huffman variant of Xpress: the algorithm that wraps every Windows 10/11 Prefetch file inside its MAM container, and the reason this browser tool stops at detecting those files instead of decoding them.
- RtlDecompressBufferEx (ntifs.h): Microsoft Learn. The Windows API that performs the decompression, documenting COMPRESSION_FORMAT_XPRESS_HUFF as a supported format. This is the function offline Prefetch tools call on a Windows host, which is why several of them require Windows 8 or newer to open a Windows 10 file at all.
- [MS-SHLLINK] Shell Link (.LNK) Binary File Format: Microsoft Learn. Microsoft's own authoritative binary-format spec that this tool's parsing logic implements, worth consulting directly when you need to verify a specific field or dig into a structure (e.g. LinkInfo, the LinkTargetIDList shell-item breadcrumb) beyond what the summarized output shows.
- libyal / dtformats: Windows Recycle.Bin file formats. Joachim Metz's byte-level documentation of the $I metadata record: the offset tables this tool's parser implements for both format version 1 and version 2. Microsoft publishes no specification for $I, so this format-documentation project (the same effort behind the libyal forensic libraries) is the closest thing to an authoritative reference and is worth reading directly for the raw structures.
- MITRE ATT&CK T1070.004 Indicator Removal: File Deletion. MITRE's authoritative page for the Stealth-tactic technique that makes this artifact matter: an adversary deleting the files their intrusion left behind. Useful for the detection guidance and real-world procedure examples that frame what a recovered $I record actually evidences.
- MITRE ATT&CK T1070.006: Timestomp. MITRE's authoritative reference for the Stealth-tactic Timestomp technique, including 'double timestomping' (where both $SI and $FN are altered to defeat exactly this kind of comparison) and real-world procedure examples for interpreting what a flagged mismatch actually indicates.
Worth using too
- libyal/libscca: Windows Prefetch File (SCCA) format documentation. Joachim Metz's reverse-engineered format specification (the per-version structure tables this parser's offsets come from) plus a C library and the sccainfo command-line tool that reads compressed Windows 10 files this browser tool cannot.
- Eric Zimmerman's PECmd (EZ Tools). The de facto industry-standard offline Prefetch parser. It handles the compressed Windows 10/11 format and can write the decompressed bytes back out, so it is the natural next step for any file this tool identifies as a MAM container, and for batch/CSV timeline output across a whole evidence set.
- Forensics Wiki: Windows Prefetch File Format. A second, independently maintained write-up of the same header and file-information structures, useful for cross-checking an offset before trusting it. It's the source this tool's own layout constants were verified against.
- SANS Internet Storm Center: Forensic Value of Prefetch. A practitioner diary on how to actually use the artifact: what the NAME-HASH.pf filename encodes, the eight-timestamp change in Windows 8, and the folder retention limits (128 files on Windows 7 and older, 1,024 on Windows 8 and newer) that shape how much history you can expect to recover.
- Eric Zimmerman's LECmd (EZ Tools). The de facto industry-standard offline LNK parser (part of the free EZ Tools/KAPE suite used by FBI and Kroll IR teams), useful as a deeper, batch-capable alternative when you need to process an entire evidence set of .lnk files with CSV/timeline output rather than one file at a time in the browser.
- ExifTool. Phil Harvey's widely used cross-platform metadata utility ships a dedicated LNK module, making it a handy way to cross-check a shortcut's extracted fields as part of a broader multi-format triage workflow spanning many file types at once.
- LnkParse3. An actively maintained open-source Python LNK parser with JSON output, useful as a scriptable alternative when you need to batch-process or pipeline many .lnk files programmatically instead of pasting them one at a time into a browser tool.
- rifiuti2. Abel Cheung's cross-platform open-source Recycle Bin parser, shipping separate binaries for the pre-Vista INFO2 index and for the modern $Recycle.Bin $I records, with XML/JSON output. A good scriptable second opinion on Linux/macOS, and its source is a useful cross-check on the $I field offsets.
- Magnet Forensics Artifact Profile: Windows Recycle Bin. A vendor-written practitioner overview of the artifact as a whole, where the per-user folders live, how the $I/$R pair works, and what the Recycle Bin does and does not capture. Useful investigative context around the raw fields this tool decodes.
- MFTECmd (Eric Zimmerman's EZ Tools). The free, actively-maintained, industry-standard command-line parser for $MFT, $J (USN journal), $LogFile, $Boot and $SDS. Run it against a full disk image or extracted $MFT to batch-extract every $SI/$FN timestamp pair at scale, complementing this page's single-record deep dive.
- USN Journal Viewer & Parser. A free tool that parses a raw $UsnJrnl:$J file entirely client-side in the browser (WebAssembly, nothing uploaded to a server) and can optionally cross-reference an uploaded $MFT to resolve full paths, useful for triaging a full USN journal export before drilling into one record here.
- SANS DFIR: Detecting Time Stamp Manipulation. A SANS walkthrough of a real intrusion where comparing $STANDARD_INFORMATION against $FILE_NAME timestamps exposed an attacker disguising a malicious binary as a legitimate system file: the same $SI-vs-$FN detection logic this tool automates, shown against a live case.