All posts

Memory forensics tools compared: Volatility, Rekall, ramparser, Magnet

5 min read

There is no single best memory forensics tool. There are tools for acquisition, tools for triage, tools for deep analysis, and tools for carving. The right answer is almost always a chain of two or three. This is the 2026 view of what is worth running and what each is best at. For the broader context first, the RAM forensics field guide covers the discipline end-to-end.

Acquisition tools

You cannot analyze a dump you did not capture. Acquisition tools differ mostly in OS support, output format, and how invasive they are on the live host.

ToolOSOutputNotes
Magnet RAM CaptureWindows.rawFree, signed driver, simple GUI. The default for IR — step-by-step guide.
DumpItWindows.raw / Microsoft .dmpSingle-file, no install. Great for field acquisition.
FTK ImagerWindows.raw + AD1Useful when you also need disk imaging.
WinPmemWindows.raw / .aff4Open source. AFF4 support is rare among analyzers.
LiMELinux.lime / .rawKernel module; the target's compiler must match.
AVMLLinux.raw (compressed)Microsoft. Built for cloud / hostile environments.
VBoxManage / vmware-vdiskmanagerVMs.vmemPause the VM, grab the file.

Two things matter regardless of tool: hash the output (SHA-256) and write to external media. A capture that contaminates the host is worth much less in court. See memory dump file formats for the formats analyzers read natively and the ones needing a conversion pass.

Analysis frameworks

Acquisition is mostly a checkbox — "did you get the bytes". Analysis is where the choice of tool changes what you can see.

Volatility 3

The reference framework. Python 3, plugin-based, supports Windows, Linux, and macOS. Pulls kernel symbols on demand. Active development by the Volatility Foundation.

Strengths

  • Plugin breadth — a plugin for almost every artefact.
  • Symbol-driven, so process lists and structures are exact per build.
  • Cross-platform: Windows, Linux, macOS in one tool.
  • Solid timeline and YARA integration.

Weaknesses

  • Python environment + dependencies + symbol packs to manage.
  • CLI-only; the output is text tables you grep.
  • Setup friction is real, especially in restricted environments.

Rekall (legacy)

A fork of Volatility 2 from Google. No longer actively maintained; still in the wild for certain Mac dumps. Do not start new work here. Start with Volatility 3 and only fall back if a specific historical need shows up.

ramparser

A browser-based, WebAssembly memory analyzer. Runs every applicable plugin automatically on a dropped image. The RAM image never leaves the device.

Strengths

  • Zero install. A static web page. Open it, pick a file.
  • Zero upload. Parsing in WebAssembly inside a Web Worker. The dump stays local — full privacy model.
  • Symbol-accurate for Windows: fetches the matching public ntoskrnl PDB to get exact _EPROCESS offsets.
  • All applicable plugins (pslist, psscan, psxview, pstree, cmdline, dlllist, modules, netscan, threads, getsids, handles, envars) run in one pass.

Weaknesses

  • Triage-focused. No timeline reconstruction or YARA scanning yet.
  • Linux support is experimental (a heuristic taskscan).
  • Browser tab needs to stay focused for best throughput on large dumps.

The honest framing: ramparser is a triage front-end; Volatility 3 is the deep-analysis back-end. They complement each other.

Magnet AXIOM Cyber

Commercial, end-to-end IR platform that also does memory analysis. Strong case-management story, paid, and orthogonal to the open-source toolset.

Carving and IOC tools

These run across the dump, not against structured kernel objects:

  • YARA — rule-based pattern matching. Pair with Volatility's yarascan plugin or run standalone.
  • bulk_extractor — e-mail addresses, URLs, IPs, key material, and Bitcoin addresses straight from raw bytes.
  • strings — the classic Unix tool, still useful as a first-pass sanity check.

A practical combination

For the typical Windows IR case:

  1. Capture with Magnet RAM Capture (or DumpIt). Hash it.
  2. Triage with ramparser. Confirm the process list, command lines, and network sockets without setting anything up.
  3. Deep-dive with Volatility 3 — malfind for injection, timeliner for timelines, yarascan for rule-based hunts.
  4. Carve with bulk_extractor for indicators not in structured objects.

Each step plays to a specific strength. The open-source toolchain is mature enough to do real work without buying anything. The end-to-end memory analysis workflow post breaks this same flow into five evidence-driven stages with concrete deliverables.

What about Mac?

Mac memory forensics is harder. Volatility 3 has macOS plugins but kernel changes (System Integrity Protection, the move to Apple Silicon) routinely break offsets. Acquisition itself often requires Apple's osxpmem or specialized tooling. ramparser does not support macOS today.

Where each tool fits

For 2026 memory forensics:

  • Acquisition: Magnet RAM Capture (Windows), LiME or AVML (Linux).
  • Triage: ramparser. Fast, private, in a browser.
  • Analysis: Volatility 3.
  • Carving: bulk_extractor + YARA.

The right answer is rarely one tool. It is three or four, chained.

Further reading