You don’t need any extra hardware to save what SysDVR streams. There are three good routes: the SysDVR-Client’s own built-in capture, which saves clips and screenshots while you play; OBS, which records the stream with your overlays and layout; and mpv, which can write the raw RTSP feed straight to a file. All three record the same source, so choose by workflow — not by quality.
The ceiling every method shares
SysDVR streams the console’s built-in recording feed: 720p30 H.264 video with 16-bit PCM 48 kHz audio. Recording captures that feed as it arrives — no method on this page can add detail the console never sent, and nothing upscales it into real 1080p. Within that ceiling, though, recordings are clean, and 720p is a perfectly serviceable format for clips, Discord shares and most video platforms.
Update first if you’re on an old client. Version 6.3 specifically improved recordings: clips captured by the client now use AAC audio, so they play on Windows with no conversion step. On older versions, recorded clips could need converting before Windows would play them. See how to update SysDVR.
Method 1 — The client’s built-in capture (quickest)
Since version 6.0, the SysDVR-Client GUI can capture video clips and screenshots in real time while the stream is running — press the capture controls in the client window when something worth keeping happens, and the clip or still is saved without any other software in the chain. Because it works inside the client, it works the same over USB, TCP Bridge and on the Android app.
There’s a command-line equivalent too: v6.3 reintroduced the --file option, which records clips from the terminal — handy for scripted or repeatable captures. Run SysDVR-Client --help for its exact syntax on your build.
Best for: spontaneous clips while playing — a boss kill, a glitch, a goal — with zero setup.
Method 2 — OBS recording (best if you also stream)
- Add the stream to OBS: either a Window Capture of the SysDVR-Client, or a Media Source pointed at
rtsp://<console IP>:6666/in Simple Network mode (untick “Local File”). The media source adds some buffering, which is fine for recording even if it’s not ideal for live play. - Make sure OBS is hearing the game — check the audio meter moves with the game’s sound.
- Press Record. Your overlays, webcam and scene layout are baked into the file, ready to upload.
- For a still, use OBS’s screenshot of the preview/source — or grab the frame with the client’s own screenshot capture instead.
This is the route to build on if recording is a habit: one OBS setup serves both this and streaming to Twitch and YouTube.
Method 3 — mpv stream recording (no client at all)
In Simple Network mode you can skip the client entirely. Play the feed in mpv with the usual low-latency flags, and add mpv’s stream-record option to save it at the same time:
mpv rtsp://<console IP>:6666/ --profile=low-latency --stream-record=clip.mkvTwo honest warnings from mpv’s own manual: stream recording remuxes without re-encoding, and mpv calls the feature fragile and experimental — files can occasionally come out broken. Use the .mkv container, and test with a short clip before trusting it with a long session. (On older mpv builds the same option was named --record-file.) Our RTSP mode guide has the full low-latency flag set and the TCP/UDP transport choice.
A note on screenshots
Whichever tool takes them, screenshots are frames of a 720p video feed. They’re great for sharing moments, thumbnails and bug reports — just expect video-frame quality rather than crisp UI stills, especially with small text.
Quick picker
| Goal | Use |
|---|---|
| Grab a clip mid-game, zero setup | Client built-in capture |
| Record with overlays / also stream | OBS recording |
| Save the raw feed, no client window | mpv stream recording |
| One still image | Client screenshot or OBS screenshot |
Set up once for clean captures
- Record through the client modes when you can. The built-in capture works in the client itself, so USB or TCP Bridge gives you clip capture with the least machinery between the game and the file. The RTSP routes work too, but they add a player and its buffering into the chain.
- Do a 20-second test clip and play it back before the real session — on the machine you’ll edit or share from. You’re checking two things: picture, and that the audio plays natively (on v6.3’s AAC clips it will; on older clients this test is exactly where a conversion surprise shows up).
- Keep versions matched. Capture features arrived and changed across 6.x — the GUI capture in 6.0, the AAC improvement and
--file‘s return in 6.3. A console and client on the same current release is what makes this page’s instructions true. Updating both sides takes five minutes. - Clip has no sound or won’t play on Windows? You’re almost certainly on a pre-6.3 client. Update, re-record the test clip, and the AAC change should make it play as-is.
Short clips or full sessions?
Pick by session shape as well as by tool. The client’s built-in capture is built around moments — something happens, you grab the clip. For recording an entire play session start to finish, OBS or mpv are the natural fit: they write one continuous file for as long as you play, OBS with your full layout on top. Plenty of creators run both at once — OBS recording the session, the client capture ready for the highlight that deserves its own file.
Next steps
- Stream to Twitch & YouTube with OBS + SysDVR — the same OBS setup, live.
- Simple Network (RTSP) mode — the feed behind methods 2 and 3.
- Make sure you’re current: files and release notes are on the SysDVR download page.