Download RAMMap for Windows PC v1.63 for Windows PC
RAMMap 1.63 is Microsoft Sysinternals' advanced physical-memory analyser for Windows: see exactly how Windows assigns RAM across the file cache, processes...
Technical Specifications & System Requirements
Software notes
Features
- The Use Counts view breaks physical memory down by purpose and state — cache, pools, drivers, processes, standby and modified — in a way no built-in Windows tool matches.
- File Summary and File Details name the exact files held in the system cache and how much memory each one occupies, which settles cache arguments with evidence.
- Standby memory is shown split across all eight priorities alongside the modified and free lists, so memory-pressure problems can be diagnosed rather than guessed at.
- Snapshots can be saved and reloaded, letting you compare memory use before and after an application run or a suspected leak and share the evidence with a support team.
- It is free, Microsoft-signed and fully portable in a ZIP under 1 MB, with x86, x64 and ARM64 binaries that run from any folder or USB stick with no installation.
Considerations
- Emptying the standby list is only a temporary troubleshooting step, and because the discarded cache must be re-read from disk it can make applications feel slower afterwards.
- The data assumes real knowledge of the Windows memory manager, so standby priorities, page states and pool types will overwhelm users looking for a simple percentage.
- RAMMap is almost entirely read-only diagnosis: it identifies where memory went but does not fix a leaking driver, a faulty application or a machine that simply needs more RAM.
How RAMMap for Windows PC Compares to Top Alternatives
ZoomIt is the Sysinternals tool for presenters — live screen zoom, annotation and break timers — while RAMMap is the Sysinternals diagnostic that shows exactly where physical memory has gone, down to the files in the cache.
Process Explorer is Microsoft's advanced task manager — process trees, DLLs, handles and per-thread CPU — while RAMMap looks at memory itself: kernel pools, page tables, the file cache by file name, and standby lists by priority.
Process Monitor logs every file system, registry and process event in real time, while RAMMap takes the memory manager's snapshot — use counts, cached files and page states — and can save snapshots for before-and-after comparison.
About & Overview: RAMMap for Windows PC
RAMMap, written by Mark Russinovich and published by Microsoft Sysinternals, answers the question Task Manager cannot: where has all the physical memory gone? Its Use Counts view breaks RAM down by purpose — process working sets, the system file cache, paged and nonpaged kernel pools, drivers, the page table and shared memory — and by state, showing how much is active, on the modified list, or sitting in the standby lists at each priority. The File Summary and File Details views name the actual files occupying the cache and how many bytes each one holds, the Physical Pages view exposes the page database, and the Processes and Priority Summary views complete the picture. Snapshots can be saved and loaded later, so memory use before and after a workload can be compared directly. The Empty menu can clear working sets, the modified page list and the standby lists, which is why troubleshooters reach for RAMMap when diagnosing memory pressure. Version 1.63 is a portable ZIP containing RAMMap.exe, RAMMap64.exe and RAMMap64a.exe — there is no installer, and it runs as administrator.
In-Depth: RAMMap for Windows PC
Where the memory actually went
RAMMap, written by Mark Russinovich and published by Microsoft Sysinternals, answers the question Task Manager cannot: where has all the physical memory gone? Its Use Counts view breaks RAM down by purpose — process working sets, the system file cache, paged and nonpaged kernel pools, drivers, the page table and shared memory — and by state, showing how much is active, on the modified list, or sitting in the standby lists at each priority, alongside the Processes, Priority Summary and Physical Pages views. Task Manager will tell you memory is 90 percent used; RAMMap tells you why — that a backup tool cached 9 GB of files into standby, that the nonpaged pool has been growing since a driver update, or that one process's working set, not a leak, is what squeezed everything else. It is also genuinely useful in the other direction, proving that high standby use is Windows caching working as designed rather than a fault.
File views and snapshots: evidence, not guesses
The File Summary and File Details views are the forensic highlight: they name the actual files occupying the cache and how many bytes each one holds, so 'the cache is full' becomes evidence rather than suspicion. Snapshots can be saved and loaded later, so memory use before and after a workload — or a suspected leak — can be compared directly and shared with a support team, turning guesswork about memory growth into evidence. Version 1.63 is a portable ZIP containing RAMMap.exe, RAMMap64.exe and RAMMap64a.exe; there is no installer, it is free and Microsoft-signed, and it runs as administrator, because reading kernel memory data requires it. RAMMap remains the clearest window into the Windows memory manager that Microsoft gives away.
Diagnosis, not a cure
RAMMap is a diagnostic instrument, not a memory optimiser: apart from the Empty commands, it changes nothing, and it does not fix a leaking driver, a faulty application or a machine that simply needs more RAM. The Empty menu — which can clear working sets, the modified page list and the standby lists — is why troubleshooters reach for it under memory pressure, but emptying the standby list is only a temporary troubleshooting step whose benefit is temporary: the discarded cache must be re-read from disk, which can make applications feel slower afterwards, not faster. And the page-level data assumes you understand terms like modified, transition and standby priority, so it will overwhelm users looking for a simple percentage. For developers, administrators and support engineers, that depth is precisely the point. It runs on Windows 10 or 11, on x86, x64 or ARM64, with 10 MB of space.
How to Install & Verify RAMMap for Windows PC
Download RAMMap.zip (under 1 MB) from Microsoft Sysinternals on Microsoft Learn, or directly from download.sysinternals.com, and save it to your Downloads folder.
Extract the ZIP to a folder such as C:\Sysinternals. It contains RAMMap.exe, RAMMap64.exe for 64-bit Windows and RAMMap64a.exe for ARM64 — nothing is installed.
Right-click RAMMap64.exe on a 64-bit system and choose Run as administrator, then accept the Sysinternals licence on first run. Press F5 whenever you want to refresh the display.
Related Windows PC Software & Alternatives
Frequently Asked Questions & Verification Guide
Is RAMMap free?
Yes. RAMMap is free, Microsoft-signed and fully portable: version 1.63 ships as a ZIP under 1 MB containing RAMMap.exe, RAMMap64.exe and RAMMap64a.exe, with no installer. It does need administrator rights, because reading kernel memory data and using the Empty commands requires elevation.
What is the RAMMap tool from Microsoft?
RAMMap, written by Mark Russinovich and published by Microsoft Sysinternals, answers the question Task Manager cannot: where has all the physical memory gone? Its Use Counts view breaks RAM down by purpose — process working sets, the system file cache, paged and nonpaged kernel pools, drivers, the page table and shared memory — and by state, active, modified or standby.
What can you do with RAMMap?
Diagnose memory pressure with evidence: see RAM by purpose and state in Use Counts, name the actual files occupying the cache in File Summary and File Details, inspect the page database in Physical Pages, and save snapshots to compare memory use before and after a workload. The Empty menu can clear working sets, the modified page list and the standby lists, which troubleshooters use when testing whether a problem is cache-related.
Why is 90% of my RAM being used?
Often it is the file cache doing its job rather than a leak: standby memory holds pages Windows has finished with — most often cached file data — and it is repurposed instantly the moment an application needs RAM. RAMMap lets you verify that in the File Details view, which names the cached files and how many bytes each holds, instead of guessing from Task Manager's single percentage.
Is RAMMap a good tool?
It remains the clearest window into the Windows memory manager that Microsoft gives away, precisely because it shows categories Task Manager folds into one bar or hides entirely. Its limit is that it is a diagnostic instrument, not a memory optimiser: apart from the Empty commands it changes nothing, and its page-level data assumes you understand terms like modified, transition and standby priority.