Anything that makes a sound.

Natively does not connect to apps. It listens to your computer's audio and looks at your screen at the operating-system layer, underneath whatever is running. There is no integrations list because there is nothing to integrate with.

Zoom
Any app
OS audio & display
System layer
Natively
On your machine

No plugin to install

Nothing is added to Zoom, to your browser, or to the meeting. The app you are already in does not change.

No bot in the room

Nobody joins, no participant appears in the roster, and no recording notice fires on anyone's screen.

No waiting for support

A tool that shipped this morning works this morning. Compatibility is not a roadmap item here.

So what is the real question? Whether the other side sees it.

The first column is nearly always yes. The second is the one that varies — and there the answer is sometimes no.

Video & voice

System audio is captured from the OS, so the conferencing app is irrelevant to whether Natively hears the room.

  • Zoom1Audio + screenOne setting
  • Google MeetAudio + screenHidden
  • Microsoft TeamsAudio + screenHidden
  • Slack huddles & callsAudio + screenHidden
  • WebexAudio + screenHidden
  • DiscordAudio + screenHidden
  • FaceTime2Audio + screenHidden
  • A phone on speaker3AudioNot applicable
  • In the room, no call at all4AudioNot applicable

Coding & assessment

These run in a browser, so what matters is screen capture and OCR rather than any platform API.

  • LeetCodeScreenHidden
  • HackerRankScreenHidden
  • CoderPadAudio + screenHidden
  • CodilityScreenHidden
  • CodeSignalScreenHidden
  • HackerEarthScreenHidden
  • A shared editor over a call5Audio + screenHidden

Browsers

Anything browser-based inherits the browser's behaviour, so a page in a tab is a page in a tab.

  • ChromeAudio + screenHidden
  • SafariAudio + screenHidden
  • FirefoxAudio + screenHidden
  • EdgeAudio + screenHidden
  • ArcAudio + screenHidden

Where it does not hold

The cases worth knowing before you rely on it. None of these are bugs — they are the edge of what window-level exclusion can do.

  • Remote desktop (TeamViewer, AnyDesk, Chrome Remote Desktop)6Audio + screenVisible
  • A webcam pointed at you7—Not applicable
  • A locked-down proctoring machine8—Not applicable
  • Linux, iOS, Android9—Not applicable
  1. 1Hidden under normal capture. Zoom's hardware-accelerated screen sharing grabs the framebuffer instead of compositing windows, and that path captures everything.
  2. 2macOS only.
  3. 3Captured through your microphone channel rather than system audio. Nothing is being shared, so there is nothing to hide from.
  4. 4A lecture hall or a meeting room works the same way: microphone in, notes out.
  5. 5Chain several captures before you ask and a multi-part question is answered as one thing.
  6. 6These stream the framebuffer by design. Window-level exclusion has nothing to act on, so the overlay is visible to whoever is watching.
  7. 7No software can help here, and any product claiming otherwise is selling you something.
  8. 8If the exam runs on hardware you do not control, Natively is not on it.
  9. 9macOS 12+ and Windows 10/11 only. There is no Linux build and no mobile app.
The one caveat

Zoom has one setting that changes the answer.

Hardware-accelerated screen sharing grabs the framebuffer rather than compositing individual windows, and then there is no window-level exclusion to apply. Turning it off takes three steps — but the checking is worth doing before a call that matters, not during one.

How to check it

The only test that counts is yours.

Ten minutes, no account and no card. Start a meeting with yourself, share your screen, and look at what the other side actually sees.

Put it on your own machine.

A live-conversation assistant that runs locally. Nothing leaves your machine.

macOS 12+ · Windows 10/11

© 2026 Natively AI Private Limited

Source-available under the Natively Personal Use Source License v1.0 · IP geolocation by DB-IP