Inside
StillSwitch.

You don’t need to know any of this.
But if you’re curious, here’s what goes into a switch.

A little more than Tab.

Hold Command and press Tab to open StillSwitch. Keep Command held while choosing a window. The familiar actions are there when you need them; there’s no set of gestures to learn before you start.

Tab
Move to the next window. Hold it to keep moving.
Shift
Move back one window while Command is held. Hold Shift to keep moving backward.
Arrow keys
Move left or right through the choices, or up and down between rows.
Release Command
Switch to the selected window.
Escape
Cancel and stay where you were.
Point and click
Move the pointer over a window to select it; click to switch.
Command–W
Ask the selected window to close.
Command–Q
Ask the selected window’s app to quit.

Close and quit are normal requests to the other app. An unsaved document can still ask you to save, and an app can refuse to close. StillSwitch doesn’t force-quit it or treat an unanswered request as proof that the window is gone.

A place for the window you just used.

Recency belongs to individual windows. When you focus a window, that window moves to the front of the recent order. The other windows from the same app keep their relative places.

For a practical two-window routine, see how to toggle back and forth with a quick Command–Tab.

Once you open the switcher, the order stays steady while you choose. Background activity doesn’t keep reshuffling the list. Confirmed closures can remove an entry, but the remaining choices retain their order.

Starting with 1.0.8, StillSwitch also carries that recent order across an app update, including the previous destination for a quick Command–Tab. It matches windows that are still open and captures fresh previews after reopening. This does not reopen closed windows or restore a desktop after a Mac restart. See how automatic updates work and what the temporary local handoff stores.

The switcher opens on the display containing your pointer and stays there for that interaction. Cards are sized for the display, with additional windows arranged in rows.

A window isn’t always a picture.

Minimized windows use their app icon. So do windows whose preview is unavailable. That leaves a recognizable destination even when there isn’t a usable image.

A running app with no open windows can appear as an app icon too. Selecting it asks the app to reopen in its normal way. Finder is the exception: it appears only when it has an eligible window.

Fresh enough to recognize. Small enough to keep.

Previews are snapshots, not continuous video feeds of every window. StillSwitch reuses available images while requesting updates. A newly changed window can therefore appear briefly with its previous image before the next capture arrives.

Opening the switcher prioritizes the windows you can see. Focus changes, new windows and resized windows also trigger work when needed. While the list is open, visible previews are checked for refresh. With the list closed, the regular visible-preview refresh timer stops; relevant window events can still prepare images for the next switch.

Capture happens separately from the keyboard and window-selection work. If an image takes time, choosing a destination doesn’t have to wait for that image to arrive.

More windows shouldn’t mean unlimited images.

StillSwitch gives its central preview cache a 64 MiB budget, measured in decoded image bytes. When it needs room, it removes the least recently used cached images. Windows that no longer need a preview are removed from that cache too.

That is a cache budget, not a promise that the whole app uses only 64 MiB. The interface, temporary capture buffers, helper process and system resources also use memory. Looking only at the cache would miss those costs.

Images are captured at thumbnail sizes appropriate for the cards, and only a limited number of captures run at once. Pending work is bounded as well. Opening more windows doesn’t start an unrestricted capture operation for each one.

When macOS reports memory pressure, StillSwitch clears the preview cache and pauses capture briefly before rebuilding what is needed. Sleep also clears previews; waking starts a fresh round of preparation.

The balance matters more than one number.

Keeping a useful image in memory avoids capturing it again immediately. Refreshing less often saves work, but can leave a preview behind the window it represents. Smaller images use less memory, but still need enough detail to recognize a window.

StillSwitch balances those costs with a bounded cache, limited capture work and priority for visible windows. The goal is a useful preview without continually recapturing everything. There is no single CPU or memory figure that describes every Mac, window count and workload.

We check memory while the app and its capture connection remain running. A low reading just after a restart doesn’t demonstrate that a long-running problem has been fixed.

What a memory bug taught us.

During development, memory grew far beyond the preview cache’s size. Investigation found temporary image-transfer buffers accumulating in a long-lived read loop. They weren’t being released after each message, even though the code had finished using them.

The correction was to drain temporary autoreleased objects around each read-and-decode cycle, while keeping the image data that was still needed. Apple describes this technique for loops that create many temporary objects.

A sustained regression check now sends full-size preview frames while keeping the connection open. It checks temporary memory growth and image contents. The regression and extended daily-use review support the correction to this retention path. They don’t establish a memory ceiling for every workload.

A resize needs more than a new image.

A preview that appeared unusually small exposed a gap between cached capture geometry and a window’s current dimensions. Asking for a new image with old size information can still produce the wrong result.

StillSwitch now checks the window’s geometry before capture and checks the returned image against fresh bounds afterward. A result that no longer fits is rejected and the metadata is refreshed. Resize checks cover tall, wide and small windows, rather than treating one successful screenshot as enough evidence.

A stalled preview needs a bounded response.

Another development incident left capture requests without completion callbacks, occupying the available capture slots. Capture work is now isolated in a helper, with limits on outstanding work, retries and replacement helpers. Late results from obsolete requests are discarded.

Recovery also has to respect macOS’s ownership of an active capture session. Retiring a helper and letting its outstanding work finish is different from abruptly killing it and starting another. An icon fallback keeps selection usable, but doesn’t by itself prove that a capture fault is resolved.

The initiating trigger of that original stall is not fully established. Signed capture checks and repeated lock/recovery checks now cover the corrected path. A passing test is evidence for the case it exercised, not a promise that the problem can never happen again.

Your Mac does the work.

Window previews and switching are processed on your Mac. Your screen and window contents are not sent to a backend for processing. No cloud service needs to see what you’re working on.

Preview images stay in memory. StillSwitch doesn’t save them as screenshot files or upload them. Window titles, the list of your apps and windows, and switching history stay local too.

The StillSwitch app has no usage analytics, behavior tracking or automatic external crash reporting. This website’s separate measurement is explained in the website privacy notice.

Network access, for two jobs.

Licensing. Activating, verifying or deactivating a license contacts Lemon Squeezy over HTTPS, using license and activation information. Saved activation is read locally when the app opens; the current implementation doesn’t make scheduled or startup license-server checks. The license key and activation ID are stored in macOS Keychain.

App updates. The updater uses HTTPS to check for and download signed app updates. These requests include app and version information. System-profile sharing is disabled.

These services receive ordinary connection information, such as your IP address. Neither licensing nor update requests include your preview images, window titles, window contents or switching history.

Permission stays in your hands.

Accessibility allows StillSwitch to select windows. Screen Recording allows it to make previews. You control both in macOS System Settings. Without Screen Recording access, StillSwitch uses app icons; switching remains available when Accessibility and the input path are ready.

Those permissions allow local functionality. They don’t enable screen uploads or usage tracking.

Details you can leave to the app.

StillSwitch handles these details automatically. You don’t need to tune them: the everyday interaction remains Command, Tab, and the window you wanted.

Guide & FAQApp privacy & securityWhy direct distribution?Is StillSwitch right for you?Why I made StillSwitch