Is Monosnap using too much memory?

1. Record a clean baseline

1. Save your work and restart Windows.
2. Open Monosnap but do not capture anything for five minutes.
3. Open Task Manager with Ctrl+Shift+Esc. Microsoft describes Task Manager as the built-in view for process resource consumption.
4. Record the Monosnap version, Windows version, monitor count, and the Memory value shown for the process.

Microsoft: Task Manager and Windows system tools

2. Run the same capture sequence

Choose a sequence you can repeat exactly, for example:

• 10 region captures with no annotations;
• 10 region captures with one arrow and one blur;
• three short recordings, fully stopped and saved;
• five Cloud uploads;
• 10 minutes idle after the final task.

Record memory after each stage. A workload spike that falls after the task is different from a value that continues rising during repeated identical cycles and does not settle after idle time.

3. Check the right memory columns

The default Task Manager Memory column is useful for a quick comparison, but it is not a complete diagnosis. Microsoft's leak-troubleshooting guidance distinguishes physical working set from committed virtual memory and recommends checking commit behavior when investigating sustained growth.

Microsoft: application and service memory-leak troubleshooting

4. Use Process Explorer or PerfMon for a longer run

Microsoft Sysinternals Process Explorer exposes process handles, loaded DLLs, and more detailed process information. For a time series, Microsoft documents Performance Monitor and recommends collecting enough duration to see whether values settle or keep growing.

Keep the machine and workload consistent. Do not compare a fresh idle launch in one app with an active recording session in another.

5. Rule out common confounders

• Update Windows and the display driver, then repeat the same test.
• Test with one monitor if the problem only occurs on a mixed-DPI setup.
• Separate screenshot capture from video recording; encoders have different resource behavior.
• Check whether the high value belongs to Monosnap itself, a browser/WebView child process, Desktop Window Manager, or another application.
• Repeat after a clean restart before concluding that a single outlier is persistent.

6. Send evidence to the vendor

A useful report includes app version, Windows build, monitor/DPI layout, exact reproduction steps, timestamps, and a CSV or screenshots of the same memory columns over time. That is more actionable than “it used a lot of RAM once.”

Compare an alternative fairly

If the issue persists, install another tool alongside Monosnap and run the identical sequence after a fresh restart. Maxisnap is one Windows option; ShareX, Greenshot, and Snagit are others. Use the sourced Maxisnap–Monosnap comparison for features and plans, then use your own measurements for performance.