Jitsi on a Slow Connection: Video Quality and Audio-Only Mode

Who this guide is for

Use this guide when you can join a meeting but video freezes or speech becomes difficult to follow. It covers participant choices in the desktop web client. Private deployments can change controls, and native mobile apps may differ. A missing camera permission or a call that disconnects needs its own diagnosis.

The quality controls were reviewed against Jitsi Meet 11248 source on 2 November 2026. The steps below are suggested comparisons, not results from a measured slow-network call. No bandwidth savings or minimum connection speed was measured.

1. Choose what the meeting needs

Before changing anything, ask whether you need to see slides, sign language, captions or a demonstration. Agree on a fallback with the organizer, such as an accessible copy of the slides. Do not give up essential visual information simply to keep the call connected.

Write down the starting symptom: is it your outgoing voice, another person’s voice, camera motion or a presentation? Ask another attendee whether they experience the same problem. This gives you a comparison when you change settings.

2. Lower video quality first

Open the meeting’s video quality control. The official desktop shortcut is A, when keyboard shortcuts are active and focus is outside a text field. If it does nothing, look in the meeting menu for the quality control. [S1]

Choose a lower available video quality, then compare the same short conversation. In the reviewed client, Low and Standard map to preferred frame heights of 180 and 360 respectively. These are quality preferences, not guaranteed delivered resolution or fixed data rates. [S2][S3]

Ask the other attendee whether your voice is easier to follow and whether the picture remains useful. Keep the lower setting only if the tradeoff suits the meeting. If text in a presentation becomes unreadable, request the original document rather than repeatedly increasing quality without checking the result.

3. Compare camera mute with audio-only mode

These controls answer different needs:

The configuration reference distinguishes starting with a muted camera from starting in audio-only mode. Do not assume that muting your microphone saves incoming video traffic. [S4]

The reviewed quality slider includes a low-bandwidth option. Select it if available and compare speech again. To return, choose a video quality level; the reviewed slider disables low-bandwidth mode when you do so. Recheck the camera and presentation afterwards. Do not assume that every deployment uses identical labels. [S2]

4. If the comparison does not help

Use the result to choose the next check:

• Local sound is wrong even outside the meeting: check the headset and audio route.
• Your microphone preview fails: check device permissions.
• The failure starts when a third person joins: use the three-participant media diagnosis, rather than assuming every failure is a slow connection.
• Only one side hears speech: follow the one-way audio checks.

If you can, compare another permitted network and pause an optional large transfer you control. Keep the device, meeting and quality setting the same. Record what changed. An improved call is a diagnostic clue, not proof that a particular router, provider or Jitsi component is faulty.

Give the organizer or administrator the browser/version, approximate failure time, affected participants, selected quality and comparison results. Omit private meeting links, passwords and authentication tokens from public reports.

Developer note: embedded meetings

The documented IFrame API provides setVideoQuality and setAudioOnly. For an already initialized API instance, an explicit audio-only choice can use:

api.executeCommand('setAudioOnly', true);
// When the participant chooses to restore video:
api.executeCommand('setAudioOnly', false);

Verify the resulting meeting state and media on your deployment. Command submission alone is not a successful call test. Use the embedding guide for initialization and lifecycle handling. [S5]

Sources and review plan

• [S1] Official keyboard shortcuts, reviewed 2 November 2026.
• [S2] Pinned quality slider implementation.
• [S3] Pinned quality actions and quality constants.
• [S4] Official configuration reference, especially startAudioOnly and startWithVideoMuted, reviewed 2 November 2026.
• [S5] Official IFrame API commands, reviewed 2 November 2026.

Recheck control labels, audio-only behavior and API support when updating the reviewed client version. A future revision should include a controlled multi-participant network comparison before reporting measured savings.