Stream console gameplay

iPad: compatible UVC capture card

You need a supported iPad/iPadOS version, compatible HDMI-to-USB UVC capture card, HDMI cable, and any required data-capable USB adapter and power. Check the exact hardware and supported capture formats before purchase.

Console HDMI output → compatible HDMI-to-USB UVC capture card → supported iPad → StreamSponsor

1. On the console: choose an HDMI output resolution/frame rate supported by the entire capture chain. Connect HDMI to the capture card.
2. On the capture hardware: connect USB to the supported iPad, supplying required power. If the card has HDMI passthrough, connect it to your TV or gaming monitor.
3. In the mobile app: open Go Live and select the detected capture device as the main video in the documented Camera Source card. On supported iPads, Rescan refreshes the device list; this does not enable USB capture on iPhone.

iPhone or iPad: compatible HDMI network encoder

An HDMI network encoder converts the console's HDMI video into a supported network feed. It is a different product from a USB capture card. A normal USB capture card does not automatically transmit RTMP.

Console HDMI output → compatible HDMI network encoder → supported network feed → StreamSponsor on iPhone or iPad

1. On the console and encoder: connect HDMI and configure a supported output format. Make the encoder and mobile device reachable on the network; a shared local network is the documented setup.
2. In the mobile app: choose the supported network source as the main video. Existing network-camera documentation describes RTMP Receive and Pull modes.
3. For Receive: the app listens for video. Configure the encoder to push to the exact receive address displayed by the app. Do not substitute your outgoing Twitch/YouTube stream destination.
4. For Pull: the app connects to an encoder feed that supports the documented input. Use the encoder's actual supported source address, following its documentation and the app's network guide.

Do not assume an encoder's protocol is supported just because it has HDMI. The existing guide says RTSP-only feeds are not supported directly; this console guide does not promise direct RTSP or SRT input. Read the network-source guide before selecting an encoder or configuring addresses.

Add your overlay, face camera, and audio

1. In the web dashboard: configure sponsor logos, tickers, colors, positions, and other widgets available on your plan. Overlay configuration stays in the dashboard.
2. In the mobile app: choose your account overlay for the broadcast. Keep captured gameplay as the main video and, if the device/source combination supports it, choose a face camera as the PiP inset. Follow the mobile Go Live guide for documented source and PiP controls.
3. On the console/capture hardware and in the app: check HDMI game-audio output, capture audio support, selected app audio source, and your microphone/commentary. Check the mixed output before going live. Headset and party-chat routing varies by console and may require additional configuration or hardware.
4. While playing: use the TV/monitor through HDMI passthrough where available, rather than playing from the delayed app preview.

Compatibility and limits

• iPhone: does not support the app's USB/UVC capture-card route. Use a compatible HDMI network encoder; a USB-C port does not remove this limitation.
• iPad: supported models and app/OS versions can use compatible UVC hardware, or a supported network feed. Not every iPad, card, adapter, or format works.
• Android: console capture is not verified by this guidance. Device, hardware, OS, and app implementation determine compatibility; the website currently lists Android as coming soon.
• Nintendo Switch: requires a model with supported docked HDMI output and a compatible dock/capture chain. Switch Lite does not provide this route.
• Built-in console Twitch/YouTube broadcasting is not a feed into StreamSponsor. Do not assume a console supports entering a custom RTMP destination.
• Screen mirroring and Remote Play are not required. Capturing another app's Remote Play screen is not a documented StreamSponsor input route.
• A computer is not required for a compatible mobile capture-card or network-encoder setup. Verify the entire chain, Go Live eligibility, and available source controls for your app version; this guidance is not a hardware certification.

Troubleshooting

Black gameplay image

Check HDMI connections, selected source, capture format, and console HDCP requirements. For PlayStation, consult model-specific official instructions. Sony's PS4 instructions specify, on the PS4 console, Settings → System → uncheck Enable HDCP for gameplay; changing it closes applications. Do not apply these menu directions to other models or bypass protected streaming-video, Blu-ray, or DVD content.

No game audio

Check console HDMI audio output, whether your capture device carries audio, and the selected app audio source. Check microphone/commentary separately.

Headset or party chat missing

Console/headset routing can exclude chat from HDMI. Consult the console and capture-device documentation; additional routing or hardware may be necessary.

Delayed preview

Play on the TV/monitor using HDMI passthrough where available, not the app preview.

Network feed will not connect

Check the supported protocol, whether the app receives or pulls, the exact source/destination address, network reachability, and encoder configuration. An RTSP-only feed is not a documented direct input.

USB device not appearing on iPhone

This is a platform limitation for this app route, not a reason to keep reconnecting or changing permissions. Use a compatible HDMI network encoder.

Unsupported resolution or frame rate

Select a format supported by the entire console → capture hardware → mobile device → app chain, using those products' documentation.