Monosnap for Windows,
without the freezing.

Why Monosnap freezes on Windows

The freeze you're hitting usually lands in the same spot: you press the region hotkey, the overlay appears, you drag a rectangle, and then the app hangs for three to eight seconds before the editor opens — or never opens at all. Task Manager shows Monosnap spiking to 400 MB or more.

Three things contribute. First, Monosnap ships as an Electron app, so every capture spins up a Chromium renderer to composite the editor window. Second, the capture pipeline doesn't always release GDI handles promptly, which matters on Windows because each monitor has a bounded handle pool. Third, a long-running session accumulates a memory leak that never releases back to the OS. By hour four of a workday, the freeze isn't a bug — it's the predictable end-state.

What Maxisnap does instead

Maxisnap is built directly against the Win32 capture surface. No Electron. No embedded browser. No Chromium memory model. The editor is a PyQt6 window — a proper native OS widget — that opens in under 200 ms after capture. Multi-monitor region capture spans all displays. Handles get cleaned up in finally blocks. Idle RAM hovers around 50 MB and stays flat over a full workday.

For everything outside of performance, the experience is intentionally familiar. Annotation tools cover arrows, numbered pins, text, blur, crop, shapes, and highlights. Upload destinations include SFTP, FTP, S3, custom HTTP endpoints, and built-in Maxisnap Cloud. System tray icon. Global hotkeys. Auto-copy URL to clipboard. It's the same job, done without the freeze.