Stream Shift lets supported Streamlabs devices take over an existing broadcast. The checked guide requires Ultra and documents Windows desktop plus iOS/Android mobile, with network and output-setting limitations. Enable it on both devices, rehearse the handoff and verify the same destination continues receiving the programme.
The desktop programme resumes on the intended destination and the phone is no longer the active programme source.
In this guide
Before you start
- Streamlabs Ultra with the intended desktop and mobile apps.
- A supported Windows desktop workflow and the same intended account.
- A short planned test with another device viewing the destination.
Identify the result you need
A handoff is a production transition, not just a login on a second device. Prepare the mobile camera, microphone, orientation and network before starting the desktop broadcast. Otherwise the first live view after the switch can be a setup screen, unusable framing or a different audio environment.
The checked Streamlabs guide says devices may need the same network and lists other integrations as forthcoming. It also asks YouTube users to match desktop and mobile output settings and notes a KICK orientation-switch issue. Treat those constraints as rehearsal requirements instead of assuming every device combination works.
Work through the setup
Prepare matching output
Choose a consistent orientation and compatible output settings on both devices. For YouTube, follow the documented requirement to match the desktop and mobile video configuration.
Look for: The two devices are prepared to continue the same programme without a format surprise.
Enable Stream Shift
Enable Stream Shift on the devices involved. In the mobile app, use its main-menu Stream Shift control. Keep Live Output Editing out of this session.
Look for: Both devices are ready for the supported handoff workflow rather than separate unrelated streams.
Move to the phone
Start the planned desktop test. On mobile, choose Go Live and use the detected-active-stream prompt to switch to the mobile stream.
Look for: The destination changes to the phone's picture and sound while the existing broadcast continues.
Claim the stream back
On desktop, use Claim Stream and confirm the switch to Streamlabs Desktop. Observe the destination until fresh desktop video arrives.
Look for: The desktop programme resumes on the intended destination and the phone is no longer the active programme source.
Check the actual result
Use a different harmless visual marker on each device. A cached player frame can otherwise make it difficult to tell whether the handoff completed. Wait for fresh motion and speech before assuming a prompt's success message proves audience delivery.
Test the path you actually need in production. A successful transfer on home Wi-Fi does not establish that a later transfer onto a mobile network will work. Keep the original device available until you have verified the receiving programme.
Make the next session predictable
Write a short fallback cue: which device remains responsible if the switch fails, what the audience will see and who checks the viewer page. A predictable pause is preferable to repeatedly starting competing sessions.
Recheck support before adding a new device type. The source describes some integrations as future work; a roadmap mention does not mean they can be used in this production. Review the current help article and in-app availability together.
Still stuck?
The app does not detect an active stream
Confirm the intended account, enabled feature, supported device combination and network conditions. Avoid starting a second public session until those checks are clear.
YouTube changes picture unexpectedly after handoff
Compare desktop and mobile video output settings against the documented matching requirement.
You need to edit destinations during the handoff
Stream Shift and Live Output Editing are documented as incompatible. Choose the required workflow before starting the session.
Sources & references
Documentary review of current first-party help pages and indexed first-party excerpts, checked November 4, 2026. The diagnostic sequence and rehearsal examples are original editorial guidance; Foxdip did not operate a private account, run these broadcasts or measure performance. Expected results are checks for the reader to perform, not claimed test results.
- Streamlabs — Stream Shift ↗Checked 2026-11-04
- Streamlabs — Live Output Editing ↗Checked 2026-11-04
Spotted something out of date? Let Alex know.
How we put our guides together ↗