Keep a reference window handy without putting it on stream

A reference window is useful precisely when you need it close: a runbook beside a terminal, a checklist beside a demo, or a document you consult while presenting. But keeping it on top of other windows can also put it in the audience’s view. Pinning and privacy solve different problems. Pinning keeps a window above others on your desktop. Cloaking is what keeps selected windows out of screen capture and recording tools.

With nocapture, the practical aim is to keep the reference accessible locally while protecting it from capture. Do not treat “always on top” as a privacy setting. Set up both parts of the boundary, then verify the result in the live preview before sharing.

1. Choose the reference and the shareable surface

Decide which app or window you need to consult and which screen or windows you intend to show. Keep the reference narrow in purpose: one checklist or reference document is easier to reason about than an entire workspace full of unrelated material. Close or move anything you do not need for the task.

Also consider what the window reveals beyond its main content. A title can expose a client, project, or document name even when the window itself is not in view. nocapture can mask window titles in places such as Alt+Tab, the taskbar, and window lists. That helps with desktop-level exposure, but it is separate from checking what the capture tool displays.

2. Cloak before pinning

Select the reference window for protection in nocapture. Then use the always-on-top behavior to keep it above other desktop windows while you work. The order is not a substitute for verification; it is simply a useful setup habit. First define the privacy boundary, then arrange the local workspace around it.

Keep the distinction clear: a pinned window can still be visible to screen capture if it has not been protected. Conversely, a cloaked window need not be closed just because you are sharing. The purpose of combining the two is to retain the reference in your working context while excluding it from the capture path that nocapture protects.

If the window contains sensitive material, avoid relying on a title mask alone. Masking a label does not hide the contents of the window. Protect the window itself, and use title masking as an additional measure where names could leak through desktop lists.

3. Check the actual share view

Before you start presenting or recording, open nocapture’s live preview and inspect what the sharing tool displays. Confirm that the reference is absent from the captured view, while the material you intend to present remains visible. Check the full layout, not just the reference window: overlapping windows, additional displays, and a changed desktop arrangement can alter what appears in a capture.

Make a small change to your working arrangement if needed, then check the preview again. Do not infer privacy from the fact that a window is pinned, or from the fact that you can still see it locally. The preview is the useful test because it shows the capture output in real time. If the result is not what you expect, pause the share and adjust the protection or layout before continuing.

4. Keep alerts and titles in the plan

A private reference is only one possible leak. A notification from a protected app can interrupt a presentation, and an exposed title can identify the work even if the content is not shown. nocapture’s stated protections include hiding selected app titles and notifications from capture and recording tools. Include the relevant apps in your protection check rather than assuming the reference window is the only sensitive item.

For recurring work, smart routine presets can apply window-cloaking configurations automatically. A routine can reduce repeated setup, but it does not remove the need to check the current desktop. Windows change, meetings change, and an old configuration may not match the material you are about to share.

5. Test the combination in your own workflow

Before using this arrangement for a high-stakes call or recording, test it with the same displays and window layout you expect to use. Verify that the reference remains usable locally, that the capture preview excludes it, and that the titles and alerts you care about are not exposed. Repeat the check after switching displays, changing apps, or changing the protected set.

This is a practical boundary, not a reason to put every private item on screen. Keep the shared workspace lean and avoid opening unrelated sensitive material while recording. For a closer look at the separate role of window labels, see why title masking differs from renaming a document.

The working rule is simple: pin for local access, cloak for capture privacy, and use the live preview to confirm the audience’s view. Treat each as a separate step. That makes a reference layer useful to you without assuming it is invisible to everyone else.