Download RAMMap for Windows

Developer: Microsoft Sysinternals (Mark Russinovich)Official website ↗

A Sysinternals view of how Windows assigns physical memory to processes, files and system use.

Free Microsoft Sysinternals utility under its licence terms. The ZIP contains a shared installer, not a standalone copy of RAMMap. Check the available software before installing.

Understand where physical memory went

RAMMap is a Microsoft Sysinternals utility for inspecting how Windows allocates physical memory. It is useful when the total memory figure seems difficult to reconcile with a simple list of applications, or when you want to understand the file cache after a large workload. Its purpose is to expose categories and relationships, not to judge every occupied page as wasted RAM.

The verified release is RAMMap 1.63, published on March 26, 2026. Microsoft's page lists Windows Vista or later and Windows Server 2008 or later. The free utility is governed by Sysinternals licence terms and runs from its extracted files. Elevated permissions are used to inspect the system's memory state. A memory-allocation view is not a hardware error test or a promise to recover a faulty module.

Start with the summary, then follow the question

Use Counts groups physical pages by usage and their position in memory-management lists. Processes describes working sets, while Priority Summary helps examine standby memory by priority. The File Summary view organizes file data currently represented in RAM, and File Details provides a closer page-level view. Physical Pages and Physical Ranges address lower-level questions about allocation and addresses.

Choose the view that matches your question instead of adding every displayed number together. A process working set describes pageable memory currently resident in RAM, not all virtual memory that process has allocated. Shared data and system categories also complicate a direct comparison with other tools. Two different memory columns can both be correct while measuring different things.

Cache is part of useful memory management

Windows can retain file data in physical memory so it is available for reuse. Standby pages are not the same as permanently unavailable memory. A large cache after reading many files can be an expected result of that workload rather than proof of a leak. Relate the category to available memory and actual application responsiveness before deciding it represents a problem.

For a closer look at one running application's identity and activity, Process Explorer provides a complementary process view. RAMMap's broader allocation picture helps show why the total cannot always be explained by simply sorting a few application names. Neither view alone proves that a particular driver or process is responsible for an unexplained slowdown.

Compare snapshots before taking action

Refresh RAMMap to obtain an updated view, then save a snapshot with a note describing the workload and time. Repeat after the specific action you want to compare. Loading a saved snapshot lets you revisit that recorded state; it does not restore Windows to the previous memory allocation. Keep the two readings tied to comparable conditions rather than treating them as a continuous performance recording.

Commands that empty memory lists or trim working sets change the state you are investigating. A lower number after such an action does not demonstrate more physical capacity or a repaired allocation leak. Data may need to be brought back when applications use it again. Begin with observation and a defined question; use the resulting allocation evidence to guide the next investigation instead of making repeated cache clearing a routine performance promise.

Questions and answers

Does RAMMap increase the amount of installed RAM?

No. It shows allocation of existing physical memory and offers diagnostic actions affecting memory lists. Changing those lists does not add capacity or repair hardware that is physically defective.

Does a large standby list mean memory is wasted?

Not automatically. Standby pages retain reusable data and can participate in normal memory management. Examine available memory, workload and application behavior instead of judging the size alone as a fault.

Does loading a snapshot restore the old memory state?

No. A saved snapshot is a record you can inspect again. Loading it changes the data you are viewing, not the live allocations or running applications on the computer.

Softmesa is an independent catalog and is not affiliated with the developer. Product names and logos belong to their owners. Always check the file source before installing.

Browse by task

Similar programs

More in Utilities →