Stream Android to OBS without a capture card (2026 guide)

April 27, 2026 · ~7 min read

Why people reach for a capture card in the first place

The "real" streaming setup popularized by console creators looks like this: HDMI out from the console → capture card → PC. For Android, the equivalent is a USB-C-to-HDMI adapter feeding a capture card. Two reasons people copy that pattern even when it doesn't fit:

1. Mental model carry-over. If you already stream PS5 or Switch, capture cards are familiar. Hitting "do the same thing for the phone" is the path of least thinking.
2. The audio problem is invisible until you try. Capture cards encode picture + game audio together, so the audio question never surfaces. Skip the capture card and audio is suddenly your problem.

The trap: a USB-C-to-HDMI adapter draws current from the phone instead of charging it, and most phones don't keep a stable HDMI signal under streaming load. So that "professional" path costs ~$200 (adapter + capture card), still drains the battery, and you're back to needing a way to hear yourself talk.

The capture-card-free path, in three steps

This works on any USB-debugging-capable Android phone. Cable can be your everyday charging cable.

1. Enable USB debugging

On your Android phone:

1. Open Settings → About phone.
2. Tap Build number seven times until you see "You are now a developer."
3. Go to Settings → System → Developer options and turn USB debugging on.
4. Plug the cable into your PC and tap Allow on the prompt.

2. Run scrcpy

scrcpy (Genymobile, Apache 2.0) is the open-source workhorse. It opens a window on your PC showing your Android screen in real time over USB. Install via the project's releases or your package manager:

# Windows (winget)
winget install Genymobile.scrcpy

# macOS
brew install scrcpy

# Linux (Debian/Ubuntu)
sudo apt install scrcpy

Then run with reasonable streaming defaults:

scrcpy --max-size=1920 --max-fps=60 --video-bit-rate=8M

3. Add a Window Capture in OBS

1. In OBS, click + under Sources → Window Capture.
2. Pick the scrcpy window from the dropdown.
3. Crop and resize. Done — your phone screen is now an OBS source.

That gets you video. If you also want game audio and your own voice in the stream, keep reading.

Audio: the part nobody warns you about

Plain scrcpy does not always carry game audio. There are three workable approaches in 2026, ranked by how forgiving they are:

Option A — scrcpy native audio forwarding (Android 11+)

Since version 2.0, scrcpy can forward audio from the device:

scrcpy --audio-source=output --audio-codec=aac

Caveats:

• Requires Android 11 or later. Older devices fall back silently to no audio.
• Some apps mark their audio as "protected" (DRM-flagged streaming apps especially) and won't forward.
• You still need to route the scrcpy audio output into OBS — see OBS Audio Output Capture on Windows or a virtual cable on macOS/Linux.

Option B — Mix on the Android side

If your game has its own streaming hooks (e.g. via Discord screen share, or RTMP plugins), you let the phone do the mixing and only use OBS as the broadcast layer. This works but adds latency and another moving part.

Option C — Bundled tools that handle it for you

This is where ChargeCast lives. Full disclosure — we make the tool — but the honest pitch is: it bundles scrcpy with a 3-channel audio mixer (game audio, PC audio, your mic) and a one-click GUI, so all three reach OBS as a single Window Capture source. It is Windows-only and not free ($4.99/month or $19.99 lifetime, with a 7-day free trial), so it's not the right call if you have time and patience to wire up Option A or B yourself.

Charging while streaming

One reason the capture-card-via-HDMI path is painful: the adapter draws power, the phone overheats, and the battery dies mid-stream. The USB path inverts this — your charging cable is the data cable. Plug it into a USB 3.x port (5 V, 1 A is fine; faster is better) and the phone trickle-charges through the same line that carries the screen.

Long sessions of scrcpy-based streaming can run 4–6 hours without thermal throttling on most modern phones. That is not true with the USB-C-to-HDMI-adapter path.

Latency and quality, ballparked

End-to-end measurements vary by phone and PC, but the order of magnitude looks like this:

For Twitch and YouTube streaming the human eye does not separate 30 ms from 60 ms. Spiky Wi-Fi mirroring is what audiences actually notice.

When you do still want a capture card

The capture-card-free path is not universal. A capture card is the right answer when:

• Your source is HDMI: Switch, PS5, Xbox, GoPro, DSLR. ADB does not exist there.
• You're streaming an iPhone with no AirPlay receiver on the PC. iOS doesn't expose a USB debugging surface like Android does.
• You compose multiple physical devices in one OBS scene and want each on its own dedicated capture, where the predictable hardware encoder is nicer than juggling several scrcpy windows.

For everyday Android gameplay streaming, none of those apply. USB + scrcpy + OBS is the cheaper, simpler, more reliable path.

Wrap-up

• You do not need a capture card to stream Android.
• The actual hard problem is audio — three options, ranked by friction above.
• USB-first means you also stop fighting the battery.
• Capture cards are still the right answer for HDMI sources and iPhone, just not for everyday Android.