To share your screen in Talk Studio, open Share, choose a screen, window, tab or supported media source, then select Show on stream to put it in the audience-facing broadcast. Talk Studio’s sharing guide says mobile devices do not support screen sharing; on a Mac, you may need to grant the browser Screen Recording permission and relaunch it.
The destination list is a separate question from what you can share on screen. Talk Studio documents built-in sharing controls, while a custom RTMP destination requires an ingest URL and stream key supplied by that destination; examples such as Instagram or Rumble should not be mistaken for native Talk Studio integrations.
Choose a sharing source in Talk Studio
Talk Studio’s browser studio lets you select a source, preview it in the studio, and decide when it becomes visible to viewers. The source list in the official screen-sharing guide includes an entire screen, a browser window or tab, slides or images, presentations, MP4 video, and MP3 or WAV background audio. Which option suits you depends on what the audience needs to see and whether sound must accompany it.
For a walkthrough of a desktop application, sharing the entire screen is straightforward, but it also exposes anything else that appears on that display. A window share limits the view to a particular application. A tab share is useful for a browser-based presentation or demonstration and can offer a separate tab-audio control. Before sharing, close private windows and notifications that could appear in the capture.
If your material is a slide deck, the presentation option can be more convenient than opening it in another app and sharing that window. Streamlabs’ guide lists PDF, PPT and PPTX files, with a maximum file size of 50 MB and a maximum of 200 pages. Those limits apply to presentation uploads described in that guide, not to the duration or quality of a live broadcast. Leave time for a large file to upload and convert before you plan to go live.
For a prepared video, choose an MP4 source; for background audio, the guide lists MP3 and WAV. A prerecorded source is not the same as sharing a desktop player: choose the option that gives you the controls you need, then check how it appears in the studio before showing it to viewers. If the segment is central to a class, devotional session or product demonstration, test the file and audio before the audience arrives.
Put the selected source on the audience canvas
Open the Talk Studio browser studio and find Share. Streamlabs’ how-to guide points to the up-arrow beside Share for sharing settings and also lists Shift+S as a shortcut. Select the type of source you want, then choose the screen, window, tab or file in the browser’s sharing prompt. Browser and operating-system prompts can differ, so read the prompt before confirming what will be captured.
After selection, look for the source in the studio’s left panel. It may be present there without yet appearing in the broadcast layout. Click Show on stream beside that source to place it on the audience-facing canvas. The essential distinction is between selecting a share source for the studio and explicitly showing it to viewers.
Once it is on the canvas, check the framing from the studio preview. The shared content may need to be made more prominent than your camera feed, especially if viewers need to read text. Streamlabs documents a Spotlight control, shown as a double-arrow icon, and says you can also double-click the window to emphasise it. Its guide describes this layout as allowing the presenter’s microphone to remain audible while the shared content is fullscreen.
Do a short check before the live segment: confirm that the right screen or window is visible, text can be read, and the microphone is still at the level you expect. If you use the spotlighted layout, make sure it suits the whole segment rather than obscuring another source you need. A rehearsal is particularly useful when switching between slides, a camera and a media file, because each transition changes what viewers see.
Include tab or system audio where available
A screen share does not automatically mean viewers will hear the sound from the content you share. When the selected source offers it, enable Share tab audio for a browser tab, or choose system audio or tab audio as appropriate. Streamlabs notes that audio availability depends on both the operating system and the type of source selected, so the control may not be offered in every combination.
For example, if you are showing a browser tab that contains a video clip, choose the tab-audio option where it appears. If you are presenting a desktop application, look for the system-audio choice if the share flow offers one. Keep your microphone test separate from the shared-content test: hearing yourself does not establish that viewers will hear the tab or application sound.
If an audio option is absent, check the selected source and the operating system’s restrictions rather than assuming Talk Studio can capture every sound path. Try a different share type only if it is appropriate for the material, and test it before the live section. This is a practical limitation to plan around: a silent screen share may be acceptable for slides, but not for a video whose dialogue or music carries the point.
Check device permissions and limits before going live
The official Talk Studio screen-sharing guide says mobile devices do not support screen sharing because of operating-system limitations. If you need to share a phone screen, do not plan on the mobile Talk Studio workflow doing it; prepare another suitable presentation route and test that route in advance. The source guidance does not make this a general statement about every way a phone might be incorporated into a production.
On a Mac, the browser may need permission to record the screen. Open System Settings > Privacy & Security > Screen Recording, allow the browser you intend to use, and relaunch it if macOS or the browser prompts you to do so. Streamlabs’ guest setup guide recommends completing that permission step before joining if a guest intends to share. Host and guest workflows can differ, so use the relevant Talk Studio prompt for the role you have.
Streamlabs recommends Chrome on PC, Mac and Android, and Safari on iOS, specifically in its guidance for joining as a guest. Treat that as guest advice rather than a complete compatibility chart for every host setup. Browser behaviour and interface labels can change; if a control is missing, consult the current help page and check the browser and operating-system permission prompts rather than relying on an old screenshot.
Presentation limits, file types and plan features can also change. The screen-sharing how-to page was last updated on 25 April 2025 and says 1080p screen sharing is available to Pro users, but plan entitlements are volatile. Check the current product and official help before depending on a particular resolution or auto-add control. Do not assume that a setting shown in an older guide will appear in your account.
Native destinations Talk Studio lists
When you are choosing where to broadcast, distinguish the native destination choices shown inside Talk Studio from sharing a screen within a broadcast. Screen sharing controls what the audience sees; destination selection controls where the live programme is sent. The current destination list is the list visible in Talk Studio’s own studio or current official documentation. Check there when you set up, because integrations and interface labels may change.
Do not infer a native integration from a platform being mentioned in a tutorial, from a third-party setup guide, or from the fact that it accepts live video. In particular, Instagram and Rumble are not to be described as native Talk Studio destinations on the basis of the research for this article. If a destination is not listed as a built-in choice, treat it as a separate custom-destination question and verify the required connection details with that platform.
For a YouTube audience, the workflow is a different matter from a desktop screen share: YouTube’s own live streaming overview explains the platform’s live-streaming setup. A screen share can be one visual element in a Talk Studio programme; it does not by itself establish that your selected destination is connected, that a stream is live, or that viewers can hear all intended audio.
If you are planning a channel that runs continuously from prepared media rather than a presenter-led session, the operational problem is different again. Our guide to whether a 24/7 YouTube music stream needs an encoder running explains why a short browser-based screen share and an always-on broadcast should not be treated as the same workflow. Likewise, the live streaming checklist is useful for checking what the audience will actually receive before you begin.
What a custom RTMP destination means
RTMP is a method used to send a live video feed to a platform or service that accepts an incoming stream. A custom RTMP destination is not the same thing as a named, built-in Talk Studio integration. It is a manually configured connection: the receiving platform provides an ingest URL, sometimes called a server URL, and a stream key that identifies the live stream or channel receiving the feed.
Both pieces matter. The ingest URL tells the streaming software where to send the broadcast; the stream key tells the destination which stream or account it belongs to. If either is missing, invalid or entered in the wrong field, the connection cannot be configured as intended. Treat the key as private, because someone who obtains it may be able to send a broadcast to the associated destination. Use the platform’s own instructions to locate, rotate or revoke a key when needed.
A platform accepting RTMP does not make it a native Talk Studio destination, nor does it mean every Talk Studio account or workflow will support the same custom setup. Confirm that Talk Studio currently exposes a custom RTMP option, and check the receiving platform’s current documentation for its exact URL and key. Do not rely on an old copied key or a guessed URL.
This distinction is useful when a platform is not in the native list. The Facebook stream key and RTMPS setup guide covers the general idea of destination credentials in that context, but its instructions are not interchangeable with another platform’s settings. Follow the intended destination’s own documentation, and do not treat an example as evidence of a built-in Talk Studio integration.
Connect and test a custom RTMP destination
Start by opening the platform or account where you want the stream to arrive. Find that platform’s current live-stream setup and copy its ingest URL and stream key. Check whether it specifies RTMP or RTMPS and whether it imposes account, channel or event requirements. This article does not assert that every destination exposes the same protocol or offers custom ingest to every account.
In Talk Studio, look for the custom RTMP destination controls rather than selecting a similarly named native integration. Enter the ingest URL and stream key in their corresponding fields, taking care not to include extra spaces or swap them. If the interface presents a protocol or other connection setting, use the value specified by the receiving platform. Save or connect using the current Talk Studio flow, then confirm that the studio reports a connection before starting the audience-facing programme.
Test with a brief, low-risk broadcast or private/unlisted arrangement if the destination provides one and it suits your needs. Confirm picture, sound, orientation and the receiving platform’s preview. A successful connection indicator in the sending studio is not the same as confirming the viewer-side result. When the test is complete, end it cleanly and verify that the intended public event or channel is the one you will use.
Keep credentials out of screenshots, public notes and messages to people who do not need them. If you accidentally expose a key, use the receiving platform’s current controls to replace it and update Talk Studio with the new value. This is ordinary access hygiene, not a guarantee against misuse. For a programme made from prerecorded material and intended to run around the clock, compare the different operating demands in our cloud services for 24/7 prerecorded YouTube streams guide; custom RTMP configuration alone does not make a session continuous.
Native integration or custom RTMP: which should you use?
A native destination is usually the simpler route when the platform appears in Talk Studio’s current destination picker and your account can connect it. The integration presents a workflow designed for that destination, so you may have fewer details to copy manually. You still need to check the channel, audience visibility and audio before going live.
Custom RTMP is relevant when the destination is not listed natively but both Talk Studio’s current interface and the destination support the required manual connection. It gives you a way to enter the destination’s credentials, but it also means you must obtain and protect the URL and key, match the protocol settings, and test the receiving side. If there is no ingest URL and stream key, you do not have the details required for this setup.
| Question | Native destination | Custom RTMP |
|---|---|---|
| Where do you start? | Choose a destination shown in Talk Studio | Choose the custom RTMP route if currently available |
| What connection details are needed? | Follow the built-in account connection flow | Obtain the destination’s ingest URL and stream key |
| What should you verify? | Account, channel and audience settings | URL, key, protocol, connection and destination preview |
| Main trade-off | Fewer manual connection details | More manual setup and credential handling |
If reliability and maintenance matter more than switching between destinations, choose the workflow you can test and monitor consistently. A presenter-led event that ends after a session has different needs from a channel expected to stay on overnight. Our comparison of OBS and a cloud streaming service looks at that operating distinction; it is not a substitute for Talk Studio’s current destination documentation. StreamNeo is relevant when the specific headache is keeping a prepared video broadcasting after you switch off your own computer: you upload the file and provide your YouTube stream key, rather than keeping a local screen-share session open.
Recheck the current list before relying on it
Destination lists, operating-system permissions and interface controls are all liable to change. Before a planned stream, open Talk Studio and inspect the available destinations in the account you will use. If the destination is absent, do not label it a native integration; check whether Talk Studio currently offers a custom RTMP route and whether the destination provides the required ingest URL and stream key.
Use primary documentation for volatile details. The Streamlabs screen-sharing guide covers source sharing, permissions and the documented presentation limits. Its screen-share setup article provides the how-to workflow. Consult the destination platform’s own live setup page for its URL, key and account requirements; never fill gaps with a guess or another service’s credentials.
Then test the whole path that matters: select the screen source, place it on the canvas, verify that the expected sound is present, and confirm the destination’s viewer-side preview. A successful screen capture alone does not prove the destination is right, and a connected destination alone does not prove viewers can see the intended source. If you are presenting live, keep a simple fallback ready, such as a slide or spoken explanation, in case a permission prompt or audio limitation interrupts the planned material.
Before committing, compare the operating options on the pricing page. When the file and channel are ready, start free — 24-hour trial, no card.
FAQ
How do I share my screen in Talk Studio?
Open Share, select an entire screen, window, tab or supported media source, then click Show on stream beside it in the studio. Check the preview and confirm that you are sharing the intended source before continuing.
How do I share tab audio?
When the selected tab-share option offers it, enable Share tab audio in the browser’s sharing prompt. Audio availability depends on the operating system and share type, so test the sound before the live segment.
Can I share my screen from a mobile device?
Streamlabs’ official screen-sharing guide says mobile devices do not support screen sharing. If you need to present phone content, plan and test another route rather than relying on the mobile sharing workflow.
Is Instagram or Rumble a native Talk Studio destination?
Do not assume either is native based on a tutorial or a platform’s ability to accept live video. Check Talk Studio’s current destination picker; if a platform is not listed, investigate custom RTMP separately and only proceed if you have the destination’s ingest URL and stream key.