To screen share in a meeting, click the Share button in your meeting app (Teams, Zoom, Google Meet, Discord or Slack), choose a single window or your entire screen, and turn on the sound option if others need to hear audio from your computer. Click Stop sharing when you're done.
Showing your screen on a TV or projector is a different job called casting. On Windows, press Windows key + K to connect to a Miracast display. On a Mac or iPhone, open Control Center and choose Screen Mirroring to send your screen to an Apple TV or AirPlay-compatible TV. On Android, use the Cast or Screen Cast tile in Quick Settings.
A third thing often gets lumped in with these: remote control, where someone else operates your computer. That's what Quick Assist, macOS Screen Sharing and Teams' "Give control" are for. Knowing which of the three you need saves a lot of fumbling with the wrong menu.
The Share button in each app
Every meeting app puts sharing in roughly the same place, but the audio option is where they differ:
App | Where to click | Share audio |
Microsoft Teams | Share (Ctrl+Shift+E on Windows) | Include sound toggle |
Zoom | Share | Share sound checkbox (bottom-left of the share window) |
Google Meet | Share screen icon | Tab audio by default. System audio toggle for windows or full screen in supported setups |
Discord | Share Your Screen in a voice channel | Supported on Windows and macOS apps, Chrome and mobile |
Slack | Share screen icon in a huddle | Desktop app |
Microsoft Teams
- Join the meeting and click Share in the meeting controls, or press Ctrl+Shift+E.
- Choose Screen to share everything, or Window to share one app.
- Turn on Include sound if you'll play a video or audio.
- A red border shows what others can see. Click Stop sharing to finish.
For slide decks, use PowerPoint Live instead. It shares the deck itself rather than your screen, so attendees can move through the slides at their own pace while you present.
Zoom
- In the meeting, click Share in the toolbar.
- Pick a screen, an app window or a whiteboard.
- Tick Share sound in the bottom-left corner to include computer audio. The arrow next to it switches between mono and stereo (high fidelity).
- Click Share, and use Stop Share at the top of the screen when you're done.
Share sound is off by default, so you have to tick it every time. If you can't share at all, the host may have limited screen sharing to the host only.
Google Meet
- In the call, click the Share screen icon in the bottom toolbar.
- Choose a Chrome tab, a Window or your Entire screen.
- Click Share.
A shared Chrome tab includes that tab's audio by default. Since late 2025, Meet can also share system audio when you present a window or your entire screen, if you turn on Also share system audio. According to Google's Meet help page, that needs Chrome 142 or newer on Windows 11 or macOS 14.2 or newer. The toggle is off by default, so if you're playing a video, sharing the Chrome tab is still the most reliable choice.
Discord
- Join a voice channel or start a call.
- Click Share Your Screen (the monitor icon).
- Choose Screens or Applications, set the quality, and click Go Live.
Every Discord user can stream at up to 720p and 30fps; higher resolutions and frame rates need Nitro. Audio capture works in the Windows and macOS desktop apps, in Chrome and on mobile, but not in other browsers or on Linux. If you want a game's or app's sound to come through, share that application rather than the whole screen.
Slack
Start or join a huddle, click the share screen icon and pick a screen or window. In the desktop apps, others can click the pencil icon to draw on what you're sharing. Slack's help pages say huddles on the free plan allow at most two participants, and up to two people can share their screens at the same time.
Windows: casting and remote help
Windows has its own sharing features outside any meeting app. Windows key + K, or Cast in Quick Settings, connects to a Miracast TV, projector or wireless display adapter, and Windows key + P switches between Duplicate and Extend once you're connected. If Windows key + K finds no devices, both the PC and the display need Miracast support, according to Microsoft's troubleshooting guidance. A cheap Miracast adapter in the TV's HDMI port fixes that for most TVs.
For remote help, search for Quick Assist in the Start menu. It lets a helper see your screen, or take control with your permission, using a one-time code. And during a Teams call on Windows 11, hovering over an open app on the taskbar can show a Share this window button.
Mac: permissions first
macOS blocks screen capture until you allow it, so this is the first thing to check when sharing fails on a Mac. The first time an app tries to share you'll see a prompt. If you missed it, go to System Settings → Privacy & Security → Screen & System Audio Recording (called Screen Recording on older versions), turn the app on, then quit and reopen it. The permission only takes effect after the app restarts, which is why the Share button can appear to do nothing.
Since macOS Sequoia, macOS periodically asks you to re-confirm screen recording permission for some apps, so the occasional prompt is normal.
To send your Mac's screen to a TV, open Control Center from the menu bar, click Screen Mirroring and pick your Apple TV or AirPlay-compatible smart TV. You can mirror the display or use the TV as a separate one. To see and control another Mac, turn on System Settings → General → Sharing → Screen Sharing on that Mac, then connect to it with the Screen Sharing app.
iPhone, iPad and Android
On iPhone and iPad, tap Share in a FaceTime call and choose Share My Screen; only one person can share at a time. In iOS 18 and later, one-to-one FaceTime calls can also let the other person request control of your screen, which is handy when you're helping family with their phone. In Teams, Zoom or Meet, tap Share (or the three dots) to start a screen broadcast, and iOS shows a red indicator while your screen is being captured. For a TV, open Control Center, tap Screen Mirroring and choose an Apple TV or AirPlay TV.
On Android, swipe down twice and tap Cast or Screen Cast (Samsung calls it Smart View) to reach a TV. For Chromecast and Google TV devices you can also use the Google Home app. Meeting apps use their own share option, which triggers Android's screen capture permission. Since Android 14 QPR2, you can share or record a single app instead of the whole screen, as long as the sharing app supports it.
Getting your screen onto a TV
Here's how the four options compare:
Method | Works from | Works to | Notes |
HDMI cable | Any laptop | Any TV or projector | Lowest lag and most reliable |
Miracast | Windows, many Android phones | Miracast TVs and adapters | Windows key + K |
AirPlay | Mac, iPhone, iPad | Apple TV, AirPlay TVs | Control Center → Screen Mirroring |
Google Cast | Chrome browser, Android | Chromecast, Google TV, Cast-enabled TVs | Chrome menu → Cast, save and share → Cast |
Wireless casting always adds some delay. For gaming or fast-moving video, use a cable.
One window or the whole screen?
Share a window by default. Others see only that app, so your other windows, chat pop-ups and notifications stay private. The trade-off is that menus and dialogs belonging to other apps may not appear for viewers.
Share the whole screen when the demo genuinely moves between several apps. Everything then appears exactly as you see it, which includes every notification and every app you switch to. If you go that way, turn on Do not disturb (Windows) or a Focus mode (macOS, iOS) first, and close the email, chat and browser tabs you don't need.
Whatever you share, don't open a password manager or reveal API keys and connection strings on screen. Viewers can record or screenshot anything you show. The major meeting apps encrypt screen sharing in transit, and WebRTC encrypts media with SRTP by design, so the real risk is showing something by accident. Watch the coloured border that marks what's being shared, and stop sharing as soon as you've finished, before you go back to other work.
When screen sharing goes wrong
Others see a black screen
If you're sharing a streaming service, that's probably by design: they often block capture of copyrighted video. Otherwise there are three common causes. When sharing from a browser, turn off hardware acceleration in the browser's settings and restart it. On a laptop with two GPUs, make the meeting app and the app you're sharing use the same graphics processor, which you set on Windows under Settings → System → Display → Graphics. And an app running as administrator may not be capturable by a meeting app running normally, so run both the same way.
The Share button does nothing on a Mac
Check Privacy & Security → Screen & System Audio Recording, turn the app on, then quit and reopen it.
Nobody can hear the audio
Check that you ticked the app's sound option: Include sound in Teams, Share sound in Zoom, or a Chrome tab in Meet. In Discord, share the application instead of the whole screen. In any browser, sharing a tab is the safest way to include its audio.
The share is choppy or blurry
Close bandwidth-heavy apps, switch to a wired connection, and lower the frame rate or resolution if the app lets you. On a slow connection, turning your camera off while you share frees up bandwidth for the screen.
How screen sharing works in the browser
Every screen sharing app runs the same pipeline: capture frames, encode them as video, send them over the network, then decode and display them on the other side.
Capture screen frames (OS capture API)
↓
Encode as video (VP8, VP9, H.264 or AV1)
↓
Send over the network (WebRTC: SRTP over UDP)
↓
Receiver decodes and renders the video
In the browser, capture is the Screen Capture API's job. You call navigator.mediaDevices.getDisplayMedia(), the browser shows its own picker, and you get back a MediaStream you can preview, record or send through a WebRTC RTCPeerConnection. MDN's getDisplayMedia() reference spells out the rules. The page must be served over HTTPS, as a secure context. The call has to come from a user action such as a button click. The user approves every time, because permission is never remembered. And the user chooses what to share, so the options you pass are hints, not commands.
A minimal page needs a button and a video element:
<button id="start">Share screen</button>
<video id="preview" autoplay playsinline muted></video>
const startButton = document.querySelector("#start");
const preview = document.querySelector("#preview");
startButton.addEventListener("click", async () => {
try {
const stream = await navigator.mediaDevices.getDisplayMedia({
video: { frameRate: { ideal: 30 } },
audio: true, // tab or system audio, where the browser supports it
selfBrowserSurface: "exclude", // hide this tab from the picker (Chromium hint)
surfaceSwitching: "include", // let the user switch tabs while sharing
});
preview.srcObject = stream;
const [videoTrack] = stream.getVideoTracks();
console.log("Sharing:", videoTrack.getSettings().displaySurface); // "monitor", "window" or "browser"
// Fires when the user clicks the browser's own "Stop sharing" button
videoTrack.addEventListener("ended", () => {
preview.srcObject = null;
});
// In a WebRTC call, send the screen to the other peer:
// stream.getTracks().forEach(track => peerConnection.addTrack(track, stream));
} catch (err) {
// NotAllowedError: the user cancelled the picker, or a policy blocked capture
console.error("Screen share failed:", err.name, err.message);
}
});
To switch an existing call from camera to screen without renegotiating the connection, replace the video track on the sender:
const sender = peerConnection.getSenders().find(s => s.track?.kind === "video");
await sender.replaceTrack(screenStream.getVideoTracks()[0]);
Audio support varies by browser and operating system, and a stream may have no audio track even when you ask for one. Check stream.getAudioTracks().length before your code relies on it.
WebRTC is peer-to-peer and built for low latency, which is why it suits screen sharing so well. If you're deciding how the .NET side of a real-time app should work, our comparison of SignalR and WebRTC for real-time communication in C# lays out the trade-offs. For a hands-on experiment that streams frames through a server instead, try ScreencastR, a screen sharing app built on SignalR streaming, or build a simple screen sharing application in C# from scratch.
Join the conversation! Your thoughts help the community grow.