Streaming Terraria From Your Android Phone Actually Works If You Stop Overcomplicating It
I've been running Terraria streams from my phone for about two years now, mostly because I don't have a dedicated PC anymore. The idea sounds messy at first. Casting a mobile game to OBS or any streaming platform on Android sounds like it should be a nightmare of lag and dropped frames. It isn't, if you pick the right setup and don't fight it. The core problem most people run into is latency between the phone and the streaming app. Terraria runs at 60fps easily on most modern devices, but once you route that feed through a wireless connection or a clunky app layer, you lose responsiveness. That gap matters when you're fighting Eye of Cthulhu and trying to dodge attacks in real time. The approach that works reliably uses a local screen capture method rather than trying to encode directly from the phone to Twitch or YouTube. You run a companion app on your Android, capture the screen, and send that video feed over USB or a tight local network to a PC where OBS or Streamlabs handles the encoding and broadcasting. USB is the cleanest path. A proper USB-C to USB-A cable running scrcpy gives you sub-10ms latency on most devices. Wireless ADB works too but adds 30 to 80ms depending on your router and how crowded the 5GHz band is. Terraria is a 2D game, so the visual data is light. Encoding it doesn't require a high-bitrate encoder. Something in the 4000 to 6000 kbps range keeps it looking fine while leaving your CPU alone. The search term people usually type isn't pointing to one single app. It's a workflow. Here's the basic version. Install scrcpy on your PC from GitHub. Enable USB debugging on your Android under Developer Options. Plug the phone in. Run scrcpy with a command like scrcpy --bit-rate 6M --max-size 1080. The video feed appears on your desktop. In OBS, add a window capture source and grab the scrcpy window. Add your mic. Start streaming. That's the whole pipeline. Takes about four minutes if you've done it before. Eleven minutes if you're doing it for the first time and can't find your USB debugging toggle.
I ran into a specific issue a few weeks ago that almost made me drop the whole setup. My Pixel 7 would screen off after thirty seconds of inactivity, which completely killed the stream whenever I stepped away to grab water or check chat. The obvious fix is keeping the device awake. scrcpy has a built-in flag for this. Running it with --stay-on prevents the phone from sleeping during the cast. I paired that with an Always On Display tweak so the lock screen wouldn't go fully black. The stream stayed live through breaks. Chat never noticed.
What Most People Get Wrong
The biggest mistake I see is trying to stream wirelessly without testing the connection first. People connect over WiFi, start casting, and then realize halfway through a boss fight that their input lag is making the game unplayable. Terraria is tight. There's no forgiveness in melee combat when your sword inputs arrive half a second late. Wireless ADB latency is not negotiable for competitive play. If you're streaming casually and just showing your world to friends who don't need frame-perfect reactions, wireless is fine. If you want actual control while playing, use a cable. It's that simple. Another thing nobody mentions upfront is audio routing. scrcpy captures system audio by default, which means your game sound and any notification pings go into the stream. That's usually unwanted. In OBS you can mute the scrcpy source and route your mic separately, but you also need to decide whether you're playing through phone speakers or headphones. Phone speakers bleed into the game mic capture on some devices. Headphones avoid that entirely. I switched to wired earbuds and the audio problem disappeared overnight.
Get the Full Details
Encoding Settings That Actually Make Sense
QuickNVEnc or x264 inside OBS are both fine for this. Terraria's pixel art doesn't benefit from the slowest presets. Default medium or fast is plenty. The bitrate I settle on is 5000 kbps at 1080p, 60fps. The mobile feed gets downsampled slightly from the phone's native resolution depending on the max-size setting, so you aren't losing quality by capping it there. Bitrate higher than 6000 kbps starts hitting diminishing returns on viewer connections without improving anything you can actually see. Your stream key goes into OBS the normal way. Twitch, YouTube, whatever platform you're using. There's a tradeoff you have to accept. When you cast via USB, the phone charges slowly or not at all depending on the cable and port. Two hour stream sessions will drain your battery noticeably even while plugged into the PC. I keep a powered USB hub between the phone and the computer so the phone gets actual charging current instead of the trickle most PC USB ports provide. Without it, you're looking at maybe ninety minutes of streaming before the battery drops to a level that triggers low power throttling. Throttling is what kills your framerates mid-stream. The phone will drop from 60fps to 30fps and you won't even notice until someone in chat asks why everything looks choppy.
When This Setup Doesn't Work
Older phones with weak SoCs will struggle. A Snapdragon 400 series chip from 2016 is not going to handle Terraria plus screen encoding plus network overhead smoothly. You'll see frame drops on the phone itself before you even start streaming. Check your device's benchmark scores or just try running scrcpy for five minutes at full settings. If the phone heats up and the frame rate stutters, you need to lower the max-size to 720 or drop the bitrate to 3000. Lower resolutions look perfectly acceptable for Terraria since the art style is simple. Pixel art compresses well even at lower bitrates. Another limitation worth noting. Some streaming platforms don't accept OBS desktop captures cleanly if you're trying to do a phone-only stream without a PC at all. Apps like Strream or Launched can encode directly on the phone, but they compress aggressively and add noticeable input lag. If you absolutely cannot use a PC, you're working with worse quality and worse responsiveness. It's functional for casual viewing but not ideal for anything where watching your gameplay in near-real time matters. I've stopped recommending the wireless-only route entirely. The cable method is faster to set up, more stable, and honestly takes less troubleshooting than dealing with WiFi interference. Start with a known-good USB cable. Test the feed. Get the stream running. Then worry about fancy audio setups and chat overlays after you've confirmed the basics work.
