Share multiple Mac apps without sharing your screen

Pick the simplest share mode that works

Google Meet supports a tab, a window, or the entire screen. Zoom can share one or more specific applications; on macOS, hold Shift while selecting the windows.

If one tab or window covers the whole task, stop there. A smaller native share boundary is easier to understand and usually safer.

A five-minute setup for a moving demo

When the call needs a browser, terminal, editor, and deck, prepare the audience path instead of cleaning the whole desktop.

1. List what the audience needs. Keep the list short: perhaps Work Chrome, Terminal, and your slide deck.
2. Open the exact windows. Include the file picker, new browser window, or dialog you expect to use.
3. Choose the share mode. Use Zoom’s multi-app selection if the set is fixed. Use ScreenK9 when the workflow changes often or must work across meeting tools.
4. Rehearse the risky transitions. Switch to a private app, a personal Chrome profile, and a newly opened window while watching the audience preview.
5. Share the verified surface. In the meeting tool, select the windows you tested—or select ScreenK9 — Audience View.

This check takes less time than closing and later reopening every private app. More importantly, it tests what the audience will actually receive.

When Zoom’s multi-app picker is enough

Zoom’s picker is a good answer when you know the required windows before the call and you are staying in Zoom. It keeps the entire desktop out of the share and needs no extra app.

Before relying on it, open one new document and one new browser window. Confirm whether they enter the share automatically or require another selection. Admin settings can also limit the available sharing options.

The privacy decision is window-based. Two Chrome windows may belong to different client or personal profiles, so select the exact window instead of thinking only in terms of “the Chrome app.”

When one audience window is easier

ScreenK9 is for the harder case: the approved source changes during the demo, private apps must stay available, or the same setup needs to work in Zoom, Meet, Teams, Loom, or OBS.

ScreenK9 uses Apple’s public ScreenCaptureKit APIs to build a separate macOS window from approved apps and verified Work-profile Chrome windows. The meeting tool sees that output as an ordinary window; ScreenK9 does not intercept or modify meeting traffic.

The setup is intentionally plain:

• choose an Allow only profile;
• approve the work apps;
• label Chrome profiles as Work, Personal, or Unclassified;
• start ScreenK9 and check the audience preview;
• share ScreenK9 — Audience View.

Personal, unclassified, stale, and ambiguous Chrome matches stay hidden. If capture starts slowly, stalls, or becomes uncertain, ScreenK9 shows a protected placeholder instead of guessing that a frame is safe.

Keep the boundary honest

ScreenK9 protects only the audience window it creates. Sharing the physical display directly in a meeting app bypasses ScreenK9.

Redaction regions are also manual. They can cover a stable private area for the audience, but they are not OCR or automatic secret detection. Test them against the layout you will actually use.

For a browser-heavy demo, set up work and personal Chrome profiles as separate trust decisions. For the local capture and data boundary, read what ScreenK9 processes.

The practical rule is simple: share one native surface when you can; use one verified audience window when the work needs to move. ScreenK9 is a screen sharing privacy app for Apple silicon Macs running macOS 14+, with a 7-day free trial.

Sources checked

• Google Meet Help: Present during a video meeting
• Zoom Support: Sharing your screen or desktop
• Zoom Support: Screen sharing security
• Apple Developer Documentation: Capturing screen content in macOS

Platform documentation and ScreenK9 app behavior were rechecked on August 29, 2026.