Record Multiple Apps in Loom Without Your Desktop

Use Loom’s Window mode first

If the explanation fits inside a single document, dashboard, or application window, use Loom’s own source selection. Open the target before you start so you can recognize its preview. A smaller capture surface is easier to inspect than a busy desktop.

The current Loom desktop instructions list Full Screen, Window, and Custom size, with custom dimensions depending on the plan. Choose Window, select the intended source, and make a brief recording before the real take.

Separately choose whether to include your camera and which microphone to use. Loom’s capture-mode guide distinguishes Screen and Camera, Screen Only, and Camera Only. Turning off the camera bubble does not change a full-screen recording into a window recording.

Play the test from the beginning. Check that the right window appears after the countdown and that the voice is audible. Open the dialog or second document you expect to use; do not assume every popup belongs to the originally selected source.

Separate several apps from several monitors

A walkthrough across a browser, editor, and terminal on one Mac display is different from recording two monitors at once. The distinction matters because the wrong workaround can enlarge the recording surface without delivering the requested result.

Atlassian’s multiple-monitor documentation says Loom cannot record two monitors simultaneously or switch between monitors during recording. ScreenK9 does not turn Loom into a multi-monitor recorder: its audience window is filtered capture from a selected display.

Loom documentation on Atlassian Support, captured September 11, 2026. The source distinguishes choosing a monitor from recording two monitors or switching between them.

For a composed scene with several independently positioned sources, the OBS multi-window recording guide answers a different task. Choose the output you need before adding software.

Record an approved app workflow through Audience View

Use ScreenK9 when the source app changes throughout a recording while personal apps need to remain open. For example, a support explanation might begin in a Work Chrome profile, show a configuration file in an editor, and finish with a terminal command.

Prepare the complete sequence first:

1. Put the required work apps on the display you will capture and replace real customer data with safe examples.
2. In ScreenK9, create an Allow only profile containing the required apps.
3. Classify the Chrome profiles intended for the recording as Work through the companion extension.
4. Start ScreenK9 and inspect ScreenK9 — Audience View while performing the sequence.
5. In Loom’s desktop recorder, choose Window and select ScreenK9 — Audience View.
6. Set the camera and microphone in Loom. Record a short take with every app transition, then review the saved playback.

Loom receives an ordinary macOS window; ScreenK9 supplies the filtered picture. Loom still controls the recording, camera, editing, storage, and sharing. The broader audience-window guide explains why this can be useful when a fixed native source no longer covers the job.

Do not switch Loom back to Full Screen because a source is missing. That selects a different capture boundary and bypasses the filtered output. Stop the take, inspect Audience View, and correct the approved app or Chrome profile selection.

A permitted app can still contain private data

ScreenK9 filters ordinary applications at the app level. It cannot allow one spreadsheet window while excluding another window of the same ordinary application. Check every document open in an approved app, including tabs, sidebars, recent-file lists, and account menus.

Chrome profile handling is more specific: personal, unclassified, stale, and ambiguous matches are excluded locally. Title matching is not cryptographic identity. The Chrome profile preparation guide explains the trust boundary you need to rehearse.

For content inside an allowed window, use clean data first. ScreenK9’s manual regions can conceal a fixed area of the audience picture, but they do not perform OCR, discover secrets, or follow moving text. A layout change means another test.

Loom also has a native option worth knowing about. Its Chrome-extension blur tool can hide selected website elements before or during recording on supported paid plans. The documentation says that tool is unavailable in the desktop app and does not blur information after recording. Use it for a supported web-only task; do not assume it protects an editor or terminal.

Check what is heard and where the video goes

ScreenK9 does not capture or route audio. Configure sound in Loom and listen to the saved test. A personal app excluded from the picture may still play a notification sound or interrupt your narration.

Apple lets you control screen and system audio recording permissions per app. Check Loom’s and ScreenK9’s permissions when a source is blank; follow any restart prompt. Adding a second capture app is not a way to bypass macOS permission requirements.

Capture privacy and distribution privacy are separate. ScreenK9’s local processing does not make the resulting Loom recording local-only. Loom’s storage and sharing rules still apply to the picture and audio it records.

Before copying a finished link, open Share and inspect the video’s access settings. Atlassian’s video-permissions guide describes the Link Settings controls. Set the audience appropriate for the actual content; a clean frame does not justify wider access to a client explanation.

Review the saved take before sending it

Spend the last minute on the artifact the recipient will watch:

• Play the opening, every app switch, and the final frame.
• Look for account names and private documents inside approved apps.
• Confirm that Personal Chrome and private ordinary apps stay outside the picture.
• Check narration, notification sounds, and camera framing.
• Inspect the final video title, thumbnail, and link-access setting.

If the take contains private content, make a corrected recording before distributing the link. Do not treat a trim, camera-background blur, or privacy setting as proof that every sensitive frame is gone.

The current ScreenK9 download page lists Mac availability and requirements. Use one native Loom window whenever it covers the explanation; use a tested Audience View when the recording needs to follow a changing set of approved apps.

Sources checked

• Atlassian Support: Get started with the Loom desktop app
• Atlassian Support: Record using multiple monitors
• How To Fix Pro: June 2026 recording overview

Platform documentation and ScreenK9’s implementation boundaries were checked on September 11, 2026. The independent video provides an introductory overview; the linked Atlassian documentation is the authority for current Mac options and availability.