Explore our new Cybersecurity Terms Glossary, explained by our experts.

View the Glossary View the Glossary
PRIVIA

Cybersecurity Terms Glossary

What Is FTK Imager?

FTK Imager creates verified forensic images of storage media and memory, and previews their contents, without altering the source evidence in any way.

Illustration for the cybersecurity term FTK Imager
Home / Blog / Cybersecurity Terms / What Is FTK Imager?
17 November 2026

What Is FTK Imager?

What Is FTK Imager?

FTK Imager is a free acquisition and preview tool from Exterro, formerly AccessData. It does one job properly: it copies storage media bit for bit into a forensic image file, calculates cryptographic hashes of the source and the result, and verifies that the two match. It also lets an examiner look inside an image or an attached drive without mounting it through the operating system.

It is deliberately limited. It does not carve deleted files from unallocated space in any depth, build timelines, index keywords, or parse artefacts. Those are the analysis tools’ job. Imaging and analysis are separate stages for good reason, and keeping the acquisition tool simple is part of why its output is trusted.

Why Imaging Comes First

The principle underneath forensic acquisition is that the original evidence must not change. Connecting a suspect drive to a running Windows machine without protection is enough to break that: the operating system will mount the volume, update access times, write to the recycle bin, index content, and possibly create restore points. None of it is malicious, and all of it alters the evidence.

The protection has two parts. A hardware write blocker sits physically between the drive and the examiner’s machine and refuses write commands at the interface level. A hash computed before and after imaging proves nothing changed during the process. FTK Imager performs the second automatically and reports the result; the first is the examiner’s responsibility and no software substitutes for it. See disk imaging and write blockers for the detail.

What It Produces

FormatCharacteristics
Raw (dd)Exact byte copy with no container. Universally readable, no compression, no embedded metadata, same size as the source.
E01 (EnCase Evidence File)Compressed, with case metadata and examiner notes in the header and CRC checks per block. The usual default.
AFFOpen format with compression and metadata, less common in current practice.
Logical AD1Selected files and folders rather than the whole device, for situations where full imaging is not permitted or not feasible.

Images can be split into segments, which remains useful for storage and transfer, and MD5 and SHA-1 hashes are recorded in the acquisition log alongside the drive serial number, the examiner’s name, and the case reference. That log is part of the evidential record.

Beyond Disk Acquisition

Three secondary functions earn their place in incident response:

Where It Fits in a Response

A realistic sequence on a compromised Windows server looks like this. Capture memory first, because every minute of uptime changes it. Collect triage artefacts with a tool such as KAPE if the system must stay running. Decide whether a full image is justified; for a single workstation in a straightforward matter it usually is, for forty virtual machines it usually is not. Image what you image with verified hashes, record the chain of custody, and analyse the copy in Autopsy or a commercial suite. Never analyse the original.

In England and Wales, investigations likely to reach court are expected to follow the ACPO principles of digital evidence, which require that evidence is not altered, that anyone accessing original data is competent to explain their actions, and that an audit trail allows an independent examiner to repeat the process and obtain the same result. The hash verification FTK Imager produces is the technical core of that third principle, and the chain of custody record is the procedural core.

At Privia Security, our Digital Forensic Incident Response Services follow a documented acquisition process with verified hashes and a maintained evidence record.

FAQ – Frequently Asked Questions

Is FTK Imager Free?

Yes. Exterro distributes it at no cost, and it is widely used in both law enforcement and corporate investigations. The paid Forensic Toolkit product is the analysis platform, with indexing, carving, timelines, and reporting. Many examiners acquire with the free imager and analyse elsewhere, including in open-source tools such as Autopsy, which is a perfectly normal arrangement.

Do We Still Need a Write Blocker?

Yes, and this is not negotiable for evidential work. FTK Imager does not write to the source, but the operating system will the moment the drive is attached, updating timestamps, indexing content, and creating restore points. A hardware write blocker refuses write commands at the interface. Software blocking is a secondary control, not a substitute for the hardware.

Which Image Format Should We Choose?

E01 for most work, because it compresses, carries case metadata and examiner notes in the header, and includes per-block integrity checks. Raw dd is the right choice when the image must be read by tools that do not support E01, or when another system will process it directly. Record the hashes either way, in the acquisition log and in your case notes.

Can It Image a Running Server We Cannot Shut Down?

It can perform a live acquisition, capturing memory and reading locked files such as registry hives through raw disk access. A live disk image is inherently inconsistent, because the file system changes while it is being copied, and that should be stated in the report. Capture memory first, since it is the most volatile evidence and the first thing lost.

Related Terms

You May Be Interested In These

What Is Tabnabbing?

Cybersecurity Terms

17 November 2026

What Is Tabnabbing?

Read More
What Is a Trusted Platform Module?

Cybersecurity Terms

17 November 2026

What Is a Trusted Platform Module?

Read More
What Is Hypervisor Security?

Cybersecurity Terms

17 November 2026

What Is Hypervisor Security?

Read More