Nexa MemKeeper

Key Features

• Usage display in the tray The current memory usage % is drawn directly on the icon, in colors for Normal, Warning (80%), and Danger (90%). Hovering shows a tooltip with used/total, the amount reclaimed by the last cleanup, and the time elapsed since.
• Top 5 popup Left-click the tray icon to see the 5 processes using the most memory, by private working set. It refreshes automatically every 2 seconds, and you can right-click an item to trim or end just that process.
• Task Manager-style process list Divides processes into 3 sections — Apps / Background processes / Windows processes — and combines the same program into one entry with its memory summed. Names appear as Sublime Text rather than sublime_text.exe, drawn from the same source as Task Manager (FileDescription).
• 3 views · header sorting Switch between Group by App (default), Process Tree (parent-child), and Flat List. Click a header to sort; showing threads and hiding pseudo-processes (Memory Compression and others) are view options.
• Live search (name, PID, window title) Typing in the search box at the bottom filters instantly while keeping the structure. If a window title matches, only the app row and that window remain; in the tree, if a child matches, its ancestors remain too so the hierarchy is visible.
• Safe ending and trimming Trim (reclaim memory only), End Process, End Process Tree, and End Thread are available by right-click. Ending is a 2-step process that requests a normal shutdown and waits 3 seconds before forcing termination, and essential system processes are excluded outright at the list stage.
• 6 selectable cleanup areas Turn on working set trim, priority 0 standby purge, full standby purge, modified page flush, system working set, and page combining individually. Aggressive areas that discard the file cache are off by default, and the settings window describes their side effects.
• Auto cleanup that acts only when needed Triggered by a usage threshold (90% by default) and Windows low-memory notifications, with a cooldown (5 minutes by default) to prevent repeated runs. Periodic cleanup is off by default based on measured evidence, and the settings window states why it is not recommended.
• Watchlist targeted trim Write an entry such as chrome.exe:1500 and that process is quietly trimmed only when its private working set exceeds the threshold. Other apps' caches are left alone, and when it is off the processes are not even enumerated, so the idle cost is 0. (Currently set in the settings file — a list editing UI is in preparation.)
• Auto cleanup deferred during full screen Auto cleanup is postponed while a game or presentation is full screen. It uses the same criteria Windows uses to decide whether to show notifications, and does not block cleanups you run yourself or the hotkey.
• Cleanup history (history.csv) Each cleanup records the time, trigger (manual, hotkey, threshold, periodic, low memory), amount reclaimed, and decrease in Active. Notifications disappear after 6 seconds, but the record stays for you to examine later, and only the most recent 200 lines are kept so the file does not grow without limit.
• Remembers window position and column widths Drag a header border to adjust column widths; the window position, size, and view mode are remembered for the next launch. Before restoring, it checks that a monitor actually exists at that position, so unplugging an external monitor does not leave the window off-screen.
• Honest reporting of reclaimed amounts Measurements showed that the increase in available memory alone could not explain even 1/5 of what actually happened, so notifications also show the amount apps actually released (decrease in Active). If measurement fails, it is omitted rather than filled in with an estimate.
• Self-minimization budget gate CI and the packaging script check idle resident RSS ≤5MB, a single exe ≤3MB, 0 external DLLs, and idle CPU ~0% by the same criteria, and exceeding them stops packaging altogether. Measured: exe 0.67MB, idle 1.3MB, enumerating 500 processes in 7.5ms.
• Separate resident shell and on-demand workers What remains in the tray is a light shell that only observes and triggers; the list window and cleanup are handled by separate processes. When they finish, the OS reclaims all of that memory, so resident memory returns to its original level even after you use these features.
• Global hotkey · multiple languages · truly portable Assign your own global hotkey that runs cleanup from any window, and choose the UI language from English (default), Korean, or following the OS. Settings are saved to data\settings.ini next to the exe, so moving the whole folder moves your settings too (falling back to %LOCALAPPDATA%\NexaMemKeeper if that location is not writable).