Toybird Labs BlogThis guide provides a reproducible check and an empty record template. It does not present new measurements or imply that one successful screenshot proves every meeting application will behave the same way.
Prepare a harmless reference first
Put only “TEST — reference view” in the source. Open the Pocket Screen reference and the capture-exclusion setting available in your installed version. Record the macOS version, Pocket Screen version and meeting/capture application version before starting. Do not use a real customer name, password or confidential note as the test content.
A setting screenshot can show where a control is located. It cannot show what a remote participant received. Similarly, a preview on the sending Mac is not a substitute for inspecting the saved file or receiving device.
Run each output path separately
| Output | What to do | What to inspect |
|---|---|---|
| macOS screenshot | Capture while the TEST reference is visible locally | Open the saved image, not just its thumbnail |
| macOS recording | Record a short interaction with the TEST view present | Play the finished recording |
| Meeting: entire display | Share the selected display in a test meeting | Inspect the receiving device or participant's view |
| Meeting: one window | Switch to the intended application window | Inspect that mode separately on the receiver |
For Zoom and Google Meet, record the precise mode used. A tab, window and entire display are not interchangeable test cases. Apple's screen-recording instructions and the meeting provider's current help can identify the controls in your environment.
Use a record that permits “not checked”
| Field | Record this |
|---|---|
| Date and time | Your actual test time |
| Mac and macOS | Model and installed version |
| Pocket Screen | Installed version and relevant setting |
| Capture/meeting application | Name, version or browser version |
| Shared target | Display, window or tab; identify the target |
| Local TEST visible | Yes / no |
| TEST in saved output or receiver | Visible / not visible / not checked |
| Change since prior test | Application update, display or sharing-mode change |
Leave a result as not checked if you could not observe it. Do not fill it with an expected outcome. This is a template for your own environment, not a prefilled certification table.
Recheck at the points that change the result
If you switch from a window to a whole display, move to another monitor, replace the source, or update the software, repeat the relevant check. Do not assume an earlier result transfers unchanged. For an important meeting, a brief rehearsal with a second device is more informative than a setting that merely looks correct.
If the reference is visible to the receiver
Stop sharing or hide the reference before investigating. Check which setting is enabled, the actual target being shared, whether another capture application is involved, and whether the behavior began after a version or mode change. Collect the harmless TEST example and version information for support rather than sending confidential footage.
Do not promise that restarting or rebuilding a view will fix every case. If exclusion cannot be confirmed in the environment you must use, keep private notes outside the shared target or use a separate device.
Exclusion is a convenience, not a security boundary
Reference-view exclusion can support a presentation workflow, but it is not permission to display passwords or secret keys. Notifications, another recording path or a change in software can create different exposure. The reliable habit is to minimize sensitive material and verify the output you are actually sending.