Fix Jitsi Meet Screen Sharing on macOS Sonoma: Permission and Browser Checks

If Jitsi Meet will not start screen sharing on macOS Sonoma, first allow screen capture for the browser you are actually using, then fully quit and reopen that browser. In Sonoma, open Apple menu > System Settings > Privacy & Security > Screen Recording, switch on the entry for Safari, Chrome, Firefox, or your other Jitsi browser, and try sharing again. Jitsi runs inside the browser, so granting permission to a different app will not fix the browser’s capture request.

This is the best first fix when clicking Jitsi’s screen-share control does nothing, the browser cannot open a source picker, or macOS reports that screen recording is not permitted. If the browser already has permission and a screen picker opens, use the later checks below instead of repeatedly changing unrelated camera or microphone settings.

Illustrated macOS Privacy and Security Screen Recording pane with Google Chrome enabled and other apps listed
Illustrative settings view: the Screen Recording list shows Google Chrome enabled; choose the browser that is running your Jitsi meeting.

1. Enable Screen Recording for the correct browser

Join the meeting in the browser where the failure happens. For example, if the Jitsi tab is open in Chrome, enable Chrome—not Safari, Firefox, or the Jitsi Meet app on another device. The permission belongs to the application that requests screen capture. Apple explains how to review and change screen and system-audio access in its Mac privacy settings guide.

  1. On your Mac, open the Apple menu and select System Settings.
  2. Select Privacy & Security in the sidebar. Scroll down if needed.
  3. Open Screen Recording. Depending on the macOS release, the setting may be labeled Screen & System Audio Recording.
  4. Turn on the switch beside the browser you use for Jitsi. If the browser is not listed, return to the meeting, click Jitsi’s screen-share button once to trigger the permission request, then check this panel again. On versions that show an add button, you can use it to select the browser from Applications.
  5. Quit the browser completely with its application menu > Quit or press Command-Q. Reopen it, rejoin the meeting, and request screen sharing again.

Closing a browser window is not always the same as quitting the application. Relaunching is a useful check because a browser may need to refresh its access after the macOS setting changes. Do not grant screen access to an app you do not recognize; this permission can expose what is visible on the screen.

Illustrated Google Chrome application menu on macOS with Quit Google Chrome selected
Illustrative Chrome menu: choose Quit Google Chrome or press Command-Q, then reopen the browser before testing Jitsi again.

2. Start a fresh share request in Jitsi

After reopening the browser, enter the meeting and select the monitor-shaped Share your screen control in the call toolbar. Jitsi’s meeting guide covers joining a meeting in a browser, and its keyboard shortcut reference lists D for switching between camera and screen sharing on supported meeting interfaces. The toolbar button is easier to verify when troubleshooting.

When a source picker appears, choose a display, window, or browser tab that matches what you intend to show, then confirm with the picker’s share button. The exact choices and wording vary by browser and version. If you select a single window, keep that window open; if you select a browser tab, make sure it is the tab containing the content to present.

Illustrated Jitsi Meet call with the monitor-shaped screen-sharing control highlighted in the bottom toolbar
Illustrative Jitsi meeting toolbar: use the monitor-shaped control to request a screen or window source.
Illustrative browser screen-source picker with Entire Screen, Window, and Chrome Tab choices
Illustrative browser source picker: select the display, window, or tab you mean to present, then confirm sharing.

3. Diagnose the point where sharing stops

What you seeWhat to check next
Clicking Share your screen produces no picker or system promptVerify that Screen Recording is enabled for the active browser; quit and reopen that browser.
A macOS permission alert appearsAllow access only if you intended to share through that browser, then follow any prompt to open System Settings.
The browser picker opens but sharing does not beginSelect a source and confirm it. If the picker immediately closes, retry with a different source such as a window or entire display.
Your selection appears to start, but other participants see nothingAsk a participant to confirm what they see. Check for a stopped share or meeting-specific restrictions before resetting macOS permissions.

These symptoms help separate a macOS permission block from a browser or meeting problem. If the picker opens, macOS has allowed the browser far enough to offer a source; the cause may instead be a canceled selection, browser issue, or a restriction on the particular Jitsi service.

4. Check browser and site-level issues

Update the browser through its official update mechanism, then test Jitsi in a normal browser window without extensions that modify page behavior. A private window can be a limited comparison, but it may disable extensions or have different site settings, so a successful test there does not by itself prove that macOS permissions were the cause.

Illustrated Google Chrome About page showing an up-to-date status without a specific version number
Illustrative Chrome About page: check your own browser’s update status in its About section; the message shown here is an example.

Camera and microphone permissions are separate from macOS Screen Recording. If video or audio also fails, check the browser’s permissions for the meeting site; Chrome’s site settings documentation explains where website permissions are managed. Changing camera or microphone access alone will not authorize screen capture.

Illustrated Chrome site permissions for meet.jit.si, with separate Camera and Microphone settings set to Ask
Illustrative site settings show camera and microphone controls for meet.jit.si; these controls are separate from macOS Screen Recording access.

Only compare with another supported desktop browser if your meeting host or service allows it. If screen sharing works in a second browser, check the first browser’s version, extensions, and application-level macOS permission. If no browser can share, check whether the Jitsi administrator has disabled screen sharing or whether an organization-managed Mac policy controls privacy permissions.

5. When toggling permission does not help

If the correct browser is enabled but the problem persists, turn its Screen Recording switch off and back on, quit the browser, and test once more. Avoid resetting all macOS privacy permissions or deleting browser data as an early step: those actions affect other apps or sites and may not address a capture problem.

If Sonoma itself has pending compatible updates, check System Settings > General > Software Update and review Apple’s macOS update instructions. An update can address broader system issues, but it is not a guaranteed fix for a Jitsi screen-share permission problem; save your work and plan for any restart before installing.

Illustrated macOS System Settings General Software Update pane checking for updates
Illustrative Software Update pane: check whether a compatible macOS update is available, but do not treat an update as a guaranteed sharing fix.

For a work-managed Mac, a setting that is locked or reverts may be controlled by your organization. Contact its IT administrator rather than trying to bypass device policy. If only one self-hosted Jitsi deployment fails, give its administrator the browser name and version, macOS version, whether the source picker appeared, and whether another meeting service can share. Do not include private meeting links or screen contents in a public support request.

How to tell whether the fix worked

Illustrated Jitsi Meet call showing a shared screen tile and the screen-share toolbar control active
Illustrative active-share view: confirm with another participant that the selected content is visible, then stop sharing when the test is complete.

The practical success check is that Jitsi opens a source picker, you select the intended display or window, and another participant confirms that they can see the shared content. Stop sharing after the test. If the permission is enabled but that sequence still fails, the macOS toggle is no longer the only likely cause; move on to the browser, organization policy, or Jitsi service checks above. Interface labels can vary across macOS and browser releases, so use Apple’s current guide if your Sonoma settings panel differs.

Official references

Interface illustrations in this guide are examples, not screenshots from a live test; labels and source-picker options can differ by browser and macOS version.

Leave a Comment

7 Best WSUS Tools for Update Management and Troubleshooting

7 Best WSUS Tools for Update Management and Troubleshooting

Compare seven tools that support or complement WSUS, from Microsoft’s native console and diagnostics to third-party patch publishing and remote deployment.

Best Windows System Monitoring Tools: 6 Picks for Server Visibility

Best Windows System Monitoring Tools: 6 Picks for Server Visibility

Compare six Windows system monitoring tools for server health, application visibility, and alerting, with current notes on deployment and licensing.

7 Wake-on-LAN Tools: What’s Still Available From the 2021 List

7 Wake-on-LAN Tools: What’s Still Available From the 2021 List

Compare seven Wake-on-LAN tools by features and availability, including free utilities, network-admin suites, and 2021 picks that have since been retired.

9 Best Ping Tools for Testing Latency and Scanning a Network

9 Best Ping Tools for Testing Latency and Scanning a Network

Compare nine ping tools for quick reachability checks, subnet discovery, TCP tests, and latency monitoring, with guidance on which one fits your network task.

Best TFTP Servers for Windows, Linux, and macOS

Best TFTP Servers for Windows, Linux, and macOS

Compare the best TFTP servers for Windows, Linux, and macOS, including SolarWinds, Tftpd64, tftpd-hpa, atftpd, haneWIN, and dnsmasq.

5 Best Microsoft Access Alternatives for Desktop and Web Databases

5 Best Microsoft Access Alternatives for Desktop and Web Databases

Compare five Microsoft Access alternatives for desktop, SQLite, no-code, and browser-based database work, with strengths, limits, and best-fit use cases.

Open-Source vs. Closed-Source Monitoring Tools Compared

Open-Source vs. Closed-Source Monitoring Tools Compared

Compare open-source and closed-source monitoring tools by cost, support, customization, security, and current options including Zabbix, Nagios, PRTG, and more.

Ingress vs. Egress: What’s the Difference in Networking?

Ingress vs. Egress: What’s the Difference in Networking?

Understand how ingress and egress describe incoming and outgoing traffic, why direction depends on the network boundary, and how to monitor bandwidth and spot risky data transfers.

6 Best Free Syslog Servers to Try for Centralized Logging

6 Best Free Syslog Servers to Try for Centralized Logging

Compare six free syslog servers and collectors for Windows and Linux, including GUI tools, open-source options, search, alerting, and secure transport.

What Is IIS? Microsoft’s Windows Web Server and Alternatives

What Is IIS? Microsoft’s Windows Web Server and Alternatives

See what Microsoft IIS does, how its request pipeline and application pools work, and when Apache, NGINX, or Caddy may fit your web server needs better.