Browser Capture Guide

Nojoin records live meetings directly from the web app using browser capture APIs. There is no desktop helper or native tray process in the browser-only release.

Use this guide when you are preparing a browser for live recording, choosing what to share, troubleshooting missing audio, or recovering a paused recording.

Supported Environments

Live capture has two browser modes:

Browser or OS Capture support
Chrome on Windows Shared audio + microphone
Edge on Windows Shared audio + microphone
Brave on Windows Shared audio + microphone
Arc on Windows Shared audio + microphone
Chrome, Edge, Brave, or Arc on Linux with PipeWire screen capture Shared audio + microphone
Chrome on macOS Shared audio + microphone
Other Chromium browsers on macOS Best-effort shared audio + microphone
Chrome on Android Microphone-only
Chrome on iOS Microphone-only
Firefox Not supported for live capture
Safari Not supported for live capture
Other mobile browsers Not supported for live capture

Unsupported browsers can still review recordings, play audio, edit transcripts, manage speakers, use search, and administer Nojoin. They cannot start live capture.

Chrome on macOS is a supported desktop capture path. Tab audio is the most reliable macOS option. Window and entire-screen audio should work on current Chrome and current macOS when the browser picker exposes and grants the audio toggle, but older browser or OS versions may return video without a shared-audio track. Other Chromium-family browsers on macOS are allowed by Nojoin but treated as best-effort because their picker behavior can lag Chrome.

What Nojoin Captures

Nojoin combines two browser-granted audio sources:

On desktop shared-audio capture, the browser mixes those sources in the Nojoin tab, uploads short audio segments to the backend, and the worker transcodes each segment to the canonical 16 kHz, two-channel WAV path used by live transcription and final processing. Channel 0 carries shared/system audio when available and channel 1 carries microphone audio; speech recognition can use a mono mix derived from those preserved channels.

On mobile Chrome, Nojoin records only the phone microphone. The browser still uploads live segments into the same backend pipeline, but remote participants are captured only if the phone microphone can hear them from the room or device speaker. Keep the Nojoin tab open and the phone awake while recording.

For support and debugging, browser recording segments are numbered from 0 and resume with the next sequence after the last uploaded segment. Finalization rejects missing sequence gaps. Live ASR and rolling speaker-window diarization are tracked separately in the backend, so a recording can have transcript coverage before every speaker-window pass has completed. Final processing reuses live text and speaker decisions only when they align by stable utterance id or clear time overlap; ambiguous spans keep the final pipeline output.

Before Your First Recording

  1. Open Nojoin in Chrome on Windows, Linux, or macOS for shared-audio capture, in Chrome, Edge, Brave, or Arc on Windows or Linux, or in Chrome on Android/iOS for microphone-only capture. Other Chromium-family browsers on macOS are best-effort.
  2. Confirm your meeting platform is open in a browser tab if you want reliable tab audio capture.
  3. Check that your microphone is available to the browser.
  4. Open Settings > Capture if you need to choose a microphone or adjust system and microphone gain.
  5. Start a short test meeting and verify that the live waveform responds before relying on Nojoin for an important meeting. If AI is configured, Meeting Edge guidance should begin updating once enough speech has accumulated.

Starting A Recording

  1. Open the Nojoin dashboard.
  2. Select Start Meeting.
  3. On desktop, when the browser share picker opens, choose the meeting tab, application window, or entire screen you want Nojoin to hear.
  4. On desktop, enable the browser’s audio-sharing option before selecting Share.
  5. Allow microphone access if prompted.
  6. On mobile Chrome, keep the phone close enough for the microphone to hear the meeting audio.
  7. Keep the Nojoin tab open and the device awake while recording.

Chrome and Edge may focus the chosen tab, window, or screen after you select Share. That is normal. You can continue using your computer, switch windows, or interact with the meeting while Nojoin keeps recording in the original browser tab.

Mobile Chrome does not show a share picker for Nojoin because the mobile path is microphone-only.

Choosing Tab, Window, Or Entire Screen

Browser Tab

Tab sharing is the preferred option for Google Meet, Microsoft Teams, Zoom, Webex, and other web meeting apps.

Window

Window sharing can work, but some Chromium builds and operating systems do not provide window audio. If Nojoin warns that no shared audio track is present, share the meeting browser tab instead.

Entire Screen

Entire-screen sharing is useful when the meeting audio comes from a native app or from multiple windows. On Windows, enable Also share system audio in the picker. On Linux, entire-screen audio depends on the browser, desktop environment, and PipeWire support.

On macOS, entire-screen and window audio should work on current Chrome and current macOS when Chrome offers an audio toggle in the picker. If the toggle is absent or Nojoin warns that no shared-audio track was granted, update Chrome and macOS, then retry with tab sharing.

Browser Picker Audio Options

The exact wording is browser-dependent:

If the share button is disabled, select a source first and confirm that any required audio toggle is enabled.

Mobile Chrome Microphone Recording

Chrome on Android and iOS can start recording from the same Start Meeting button, but it records only the phone microphone. It does not capture another mobile app, browser tab, headset output, or system audio. For best results, keep the meeting audio audible to the phone microphone, keep Nojoin visible, and prevent the phone from locking.

Pause, Resume, Stop, And Cancel

Refreshing, closing, or navigating away from the Nojoin tab during a recording moves that recording to PAUSED. Nojoin keeps uploaded segments, drops only the in-memory tail, and shows a mandatory resume-or-discard modal the next time you open the app.

Switching to another browser tab, changing the active window, or using another application does not pause recording. The Nojoin tab only pauses automatically when it is actually unloaded or when you intentionally navigate away inside the Nojoin app.

Paused Recording Lock

Nojoin allows one active browser capture per user. If a paused recording exists, new capture and import entry points stay blocked until you choose one of the modal actions:

Paused recordings are retained indefinitely. They are not cleaned up automatically.

Capture Settings

Open Settings > Capture to configure:

These settings are stored in browser-local storage for the current cutover. They do not roam between browsers or devices.

Nojoin intentionally does not include a settings-page capture preview. Validate capture by recording a short test meeting.

Troubleshooting

No audio track in the shared stream

The browser granted screen or tab visibility but no audio track. Start again and make sure the audio sharing checkbox is enabled. If you shared a window, try sharing the meeting browser tab instead.

Live waveform is quiet

Check that the meeting is producing audible sound, verify the browser share picker audio option, then adjust gain in Settings > Capture. If only your microphone appears, the shared tab/window/screen audio was not granted.

Meeting Edge is still empty during capture

Confirm the waveform shows speech activity. Meeting Edge only updates after Nojoin has enough completed speech to build guidance, so very short tests may show waveform activity before any live guidance appears. The user-facing transcript is expected to appear after final processing rather than during capture.

Linux screen audio does not work

Use a recent Chromium-family browser and a desktop session with PipeWire screen capture. PulseAudio-only screen capture is not supported for reliable system audio.

macOS shared audio does not work

Use current Chrome and current macOS, then choose the meeting tab and enable the audio option in the picker. If window or entire-screen audio is missing, retry with tab sharing first. Other Chromium-family browsers on macOS are best-effort, so switch to Chrome when troubleshooting.

The browser asks for permissions again on resume

That is expected. Browsers do not let Nojoin silently recreate shared tab, window, screen, or microphone capture after a reload, close, or pause that released the previous tracks.

Nojoin says a paused recording exists

Use the resume-or-discard modal. Starting a second recording while a paused upload exists is intentionally blocked to avoid overlapping segment streams and accidental data loss.

Unsupported browser notice appears

Open Nojoin in Chrome on desktop for shared-audio recording, another supported desktop Chromium browser, or Chrome on Android/iOS for microphone-only recording. Review and playback still work in unsupported browsers, but live recording does not.

Privacy Notes

The browser picker controls what Nojoin can receive on desktop. Nojoin cannot silently capture your screen, tab, system audio, or microphone without browser permission. On mobile Chrome, Nojoin receives only the microphone stream granted by the browser. Stop sharing from the browser’s sharing indicator or stop the meeting in Nojoin to end capture.