Before you start

• The current release is SysDVR v6.3 — see the version history for what changed in each release.
• Download everything from the SysDVR download page, which links each file to its official GitHub release.
• You only replace the program files. Your settings in /config/sysdvr/ stay in place — don’t delete that folder.
• Updating is also the fix for most “worked yesterday” problems, especially right after a console firmware update or an Atmosphère update.

Step 1 — Download the new release (both halves)

Grab SysDVR.zip (the full console build) — or SysDVR-USB-Only.zip if that’s the build you run — and the SysDVR-Client build for your operating system, both from the same release. Downloading only one half is the classic mistake; the versions have to match on the number, not just be “recent”.

Step 2 — Replace the sysmodule on the SD card

1. Delete the old folder /atmosphere/contents/00FF0000A53BB665 from the SD card. Deleting first guarantees no stale files from the old version linger.
2. Extract the new SysDVR.zip to the root of the SD card, merging folders. This restores the sysmodule folder, the /config/sysdvr/ files and the Settings app (switch/SysDVR-conf.nro) in one pass.
3. USB-Only users: extract the USB-Only zip instead. Never mix the two builds — pick the one you run and use only its files.

Step 3 — Update the client to the same version

On your PC or Mac, extract the new client build into a fresh folder (or over the old one) so the whole client is the new version, not a blend. On Android, install the new APK over the existing app. The rule is symmetric: console v6.3 wants client v6.3, on every device you stream to.

Step 4 — Reboot the console

Sysmodules load only when the console boots. Until you reboot, the old version is still the one running, no matter what files are on the card — this is why the Settings app reports a freshly updated install as “outdated”. Reboot, then give the full build its usual ~20 seconds to start.

Step 5 — Verify both sides

1. Open the SysDVR Settings app on the console: it should display the new version with no “outdated” warning. (What every item in that app means is covered in SysDVR Settings app explained.)
2. Connect with the updated client in your usual mode and confirm the picture and audio arrive.
3. If the client can’t find the console, check discovery and network basics in our client can’t find your console fixes before changing anything else.

The three mistakes that cause “version mismatch”

What about dvr-patches?

Separate project, separate schedule. dvr-patches is keyed to your console firmware, not to the SysDVR version — updating SysDVR never requires new patches, and a firmware update is what triggers a fresh, matching dvr-patches download. The full pairing logic is in our dvr-patches install guide.

Rolling back

Changed your mind? The process is identical in reverse: download the older release from the version history links, replace the console folder, replace the client with the same older version, reboot. Version-matched is version-matched, whichever direction you’re going.

Updating alongside firmware or Atmosphère

SysDVR updates often happen in a pile: Nintendo ships a firmware, Atmosphère follows, and everything homebrew gets shuffled at once. A sane order keeps the pile manageable — firmware and Atmosphère first, SysDVR second, dvr-patches last. Get the console booting cleanly on the new CFW, then do the both-sides SysDVR update from this page, then check whether your firmware jump needs a newly matched dvr-patches build.

One version-history detail worth knowing: from firmware 20.0 onwards, the system reduced the memory available to sysmodules. The full SysDVR build still fits in slightly under 1 MB, but a console crowded with other sysmodules is more likely to hit the ceiling after a big firmware jump — if Atmosphère stops booting after an update pile-up, the Atmosphère won’t boot fixes (including the lighter USB-Only build) are the way back.

How often should you update?

There’s no schedule to keep. Update when a release fixes something you actually hit, when you change firmware or Atmosphère, or when the client and console have drifted onto different versions — and skim the version history first so you know what you’re getting. A matched, working pair beats a newer, mismatched one every time.

Still says “outdated” after the reboot? Then the running sysmodule genuinely isn’t the one you think you installed — usually because the new files landed somewhere other than /atmosphere/contents/00FF0000A53BB665, or the old folder was never actually replaced. Power the console down, pull the card, and check the folder contents against the fresh zip side by side. Nine times out of ten the mismatch is visible the moment you look. The dedicated fix guide covers the remaining cases.

Next steps

• SysDVR version history — what each release changed.
• “Not running / outdated” fixes — if the app still complains after updating.
• The setup guide hub — everything else about running SysDVR well.

One thing to know before you judge it broken: the full build of SysDVR starts about 20 seconds after the console boots. If the Settings app says SysDVR isn’t running immediately after power-on, wait half a minute and open it again — that delay is normal, and it’s the single most common false alarm with this app.

The options at a glance

The three streaming modes

Simple Network — the default

Every fresh install starts in Simple Network mode. The console runs an RTSP server and any compatible video player can connect to rtsp://<console IP>:6666/ — no SysDVR-Client required. It’s the quickest way to get a picture on a phone or TV, at the cost of more buffering. Our Simple Network (RTSP) mode guide covers the low-latency player settings.

TCP Bridge — the recommended network mode

TCP Bridge streams through SysDVR-Client with low latency and automatic console discovery on your local network. If you watch over Wi-Fi or LAN, this is the mode to live in — see the TCP Bridge mode guide for setup and the manual-IP fallback.

USB — the lowest latency

USB mode streams over a cable and is the lowest-latency option, which is why it’s the playing mode of choice for a laptop setup. It does not work while the console is docked, and Windows needs a one-time driver install from inside the client. The USB streaming walkthrough has the full procedure.

Go Offline — pausing SysDVR without removing it

Go Offline stops the sysmodule from streaming while leaving everything installed. Since SysDVR 6.2.1 the sysmodule can be started and stopped from the Settings app without rebooting the console, so this is a quick toggle rather than a teardown. It’s the option to use when you want the console to behave like stock for a while — for example, when another USB homebrew tool needs the USB interface that SysDVR’s USB mode is holding. Switch the mode away from USB, or go offline, and the interface is free again.

Version display — and the “outdated” warning

The Settings app shows the SysDVR version installed on the console. It will also tell you the sysmodule is outdated when the files on the SD card are newer than the version actually running — which almost always means one thing: you copied new files but didn’t reboot. Sysmodules are loaded at boot, so after every update the console must restart before the new version is live. Our guide to updating SysDVR walks through the full both-sides process.

Icon cache cleanup

The housekeeping entry in the list: it clears the cache of game icons the app has stored. If game icons ever look stale or wrong, clearing the cache forces them to be fetched fresh. You won’t need it in normal use — it’s there for when things look off.

No Settings app at all? You’re on the USB-Only build

The lightweight USB-Only build has no Settings app — that’s by design. It streams over USB only, uses roughly half the memory of the full build (~500 KB), and there are no modes to switch. The few toggles that exist for SysDVR live as files in the /config/sysdvr/ folder on the SD card instead — the advanced tips guide explains the no_adv discovery switch that lives there. If you want modes, recording-friendly flexibility and this Settings app, install the full build instead, as covered in the install guide.

When Settings says “not running” or “outdated”

• Just booted? Wait ~20 seconds and reopen the app — the sysmodule is probably still starting.
• Just updated? Reboot the console; the running sysmodule is still the old version until you do.
• USB-Only build? The app will never connect — it isn’t supported on that build at all.
• Still stuck? Work through the dedicated fixes in “SysDVR is not running / outdated” — every fix.

Starting and stopping SysDVR without a reboot

One quieter feature lives in the same app: since SysDVR 6.2.1, the sysmodule can be started and stopped from the Settings app (via its toolbox integration) without rebooting the console. Combined with Go Offline, that means “SysDVR is installed but completely quiet right now” is a state you can reach in seconds — and reverse just as fast when you want to stream again.

If the Settings app itself is missing

The app ships inside SysDVR.zip as switch/SysDVR-conf.nro. If you installed the sysmodule but can’t find the app in the Homebrew Menu, that file almost certainly didn’t make it to the card — re-extract the full zip to the SD root (as in the install guide) and it will appear. And if you’re on the USB-Only build, remember the app isn’t missing — it was never part of that build.

Next steps

• The SysDVR setup guide hub — install, modes and clients in order.
• How to update SysDVR — keep console and client versions matched.
• Advanced SysDVR tips — the file-based switches outside the app.

One clarification, because older guides get this wrong: dvr-patches is not a third-party community project. It is the SysDVR author’s own companion repository (github.com/exelix11/dvr-patches), and it is the patch set the official SysDVR guide itself points to.

First, check whether a game even needs the patches

Plenty of games stream with no patches at all. The test takes ten seconds:

1. Launch the game on your console.
2. Long-press the capture button.
3. If the console records a video clip, the game supports native recording — SysDVR can stream it as-is.
4. If recording is blocked or unavailable, that game needs dvr-patches.

Some games sit in between and only allow recording in certain sections; those games will only stream during those sections unless patched. Our guide to which games work with SysDVR explains the compatibility picture in full.

Step 1 — Note your console firmware version

dvr-patches releases are built per firmware version, and the match matters. On the console, open System Settings → System and note the firmware version shown there (for example, 23.0.1). You’ll pick the dvr-patches release with the same number.

Step 2 — Download the matching release

Go to the releases page of the exelix11/dvr-patches repository on GitHub and download the release that matches your firmware. Releases are named by firmware: the current one is fw-23.0.1 (for firmware 23.0.1), preceded by fw-22.5, fw-22.0 and so on. Resist the urge to just grab the newest — if your console is on an older firmware, you need the release built for your version.

Step 3 — Copy the patches to the SD card

1. Extract the release archive you downloaded.
2. Copy its atmosphere folder to the root of your SD card, merging with the existing folders when asked.
3. Check the result: the patch files (.ips files) should now sit inside /atmosphere/exefs_patches/ on the card.

Merging is the key word — you are adding files to your existing Atmosphère installation, not replacing it. If your file manager asks whether to merge or overwrite folders, choose merge.

Step 4 — Reboot the console

The patches are applied by Atmosphère as the system boots, so nothing changes until you restart the console. Reboot, wait for SysDVR to start (the full build takes about 20 seconds after boot), and you’re ready to test.

Step 5 — Test the game again

1. Launch the game that previously blocked recording.
2. Long-press the capture button — recording should now be available.
3. Start your usual streaming mode (USB, TCP Bridge or Simple Network) and confirm the picture reaches your PC or phone.

What to expect — and the author’s own caveat

dvr-patches makes most recording-blocked games streamable, not literally all of them. The author is explicit about this: a small number of games may still not work properly even with the patches installed. If a game still shows a black screen after patching, work through our SysDVR black screen fixes — and check first that you really installed the build matching your firmware.

Keeping patches and SysDVR straight

• dvr-patches follows your firmware, not SysDVR’s version. Updating SysDVR does not update the patches, and updating the patches is not part of a SysDVR update.
• After a console firmware update, download the newly matching dvr-patches release and repeat steps 3–5.
• To remove the patches, delete the patch files you added under /atmosphere/exefs_patches/ and reboot.

Picking the right release — a quick example

The release name is the firmware version it was built for. If the list doesn’t contain your exact version, that’s a sign your firmware and the available patches haven’t met yet — wait for the matching build rather than forcing a near-match.

A word on safety

Two things can both be true: the wider community reports that SysDVR itself does not seem to cause bans, and running any custom firmware carries its own risks that no patch can remove. dvr-patches changes whether games permit recording; it doesn’t change that equation, and nothing here is a guarantee. Treat ban questions the way the official guide does — as community experience, not a promise — and make your own call about connecting a modified console to online services.

Keep the release you downloaded. If you ever reinstall Atmosphère from scratch — the troubleshooting fix of last resort — the exefs_patches folder goes with the old install, and dvr-patches goes with it. Keeping the firmware-matched release zip in your downloads means the rebuild is a two-minute re-copy instead of a fresh hunt for the right version.

Next steps

• Which games work with SysDVR — the full compatibility picture.
• How to install SysDVR — if the sysmodule itself isn’t set up yet.
• Grab every file from the SysDVR download page, where each build links to its official GitHub release.

Two honest limits before the steps. First, the stream is the console’s built-in recording feed, so it is fixed at 720p and 30fps — that is a hardware limit, not a setting. Second, only games that support the Switch’s own video recording work out of the box (a patch exists for most of the rest — more on that below). If that fits how you play, and for most games it does, here is the setup.

What you need

• A hacked Switch running Atmosphère with SysDVR installed — follow our step-by-step install guide first if you haven’t.
• SysDVR-Client on the laptop — grab the build for your OS from the SysDVR download page.
• For USB: a USB-A to USB-C cable (USB-C-to-C cables are a known weak point for this mode).
• For network play: laptop and console on the same network — wired LAN is best, then the same router, then a nearby 5 GHz Wi-Fi signal.
• A compatible game: long-press the capture button in it. If the console records a clip, the game can stream.

Option A — USB: the lowest-latency way to play

If you will actually play on the laptop screen rather than just watch, USB is the mode to pick. The SysDVR author rates it as the lowest-latency option, and for playing — where every frame of delay sits between your thumb and the screen — that matters more than convenience.

1. Install the client on your laptop (Windows, macOS and Linux builds are all covered in their own setup guides, linked from the setup guide hub).
2. Set the console to USB mode: open the SysDVR Settings app from the Homebrew Menu and switch the streaming mode to USB.
3. Windows, first time only: install the USB driver from the SysDVR-Client’s own USB Driver menu — our USB streaming walkthrough covers this in full. Do not use the old Zadig method; it predates SysDVR 5.5.
4. Connect the console to the laptop with the USB-A to USB-C cable. The console must be undocked — USB streaming does not work while docked.
5. Launch SysDVR-Client and choose USB mode. The picture appears in the client window.
6. Fullscreen the client window and play. Your controller stays paired to the Switch exactly as usual — the laptop is only a screen and speakers.

Option B — Network: no cable, sit anywhere

Network play trades a little latency for freedom: the console can stay in your hands, on the couch, or in its dock across the room while the laptop shows the game.

1. Open SysDVR Settings on the console and switch the streaming mode to TCP Bridge — the recommended network mode, with automatic console discovery.
2. Launch a compatible game on the console.
3. Open SysDVR-Client on the laptop. Your console should appear in the list automatically; if it doesn’t, enter the console’s IP address manually.
4. Fullscreen the client window and play, with game audio coming through the laptop.

Connection quality is everything here, and it is about local signal, not your internet plan: wired LAN beats everything, a shared router comes next, and a strong nearby 5 GHz Wi-Fi signal is the wireless option. A weak signal means stutter no setting can fix.

Making the laptop feel like a real screen

• Go fullscreen. A borderless 720p feed on a laptop display looks clean and hides the fact that it’s a stream.
• Launch the game before you look. The Switch Home menu, settings and other system screens are not streamed — you’ll see black until a game is actually running, so start the game on the console first.
• Use the laptop’s audio. Game sound plays through the client, so laptop speakers or headphones complete the illusion that you’re playing on the laptop itself.
• Keep the console’s screen-off option in mind for long sessions — since SysDVR 6.1 the console screen can stay off while streaming, which saves battery when the laptop is doing the displaying.

The honest latency and picture-quality talk

SysDVR rides on the console’s own video recording service, so the feed is 720p30 H.264 video with 16-bit 48 kHz audio — sharp enough on a laptop screen, and it will never be 1080p or 60fps no matter what you change. Latency follows the connection: USB is the lowest-latency mode, LAN is close behind, and Wi-Fi adds a little depending on signal strength. RPGs, platformers, racing games, story games and most action titles play perfectly well this way. If you play frame-perfect competitive games where a single frame decides a combo, play those on the console’s own screen or a TV — that’s the one case where any stream is the wrong tool.

If the picture stutters or the audio drifts, work through our lag, stutter and audio desync fixes — the connection hierarchy and the client’s A/V sync toggle solve most cases.

When a capture card still wins

A capture card remains the right answer if you need 1080p60, want to play docked on a TV while capturing, or use a stock, unmodified console. Our SysDVR vs capture card comparison lays out exactly where the line sits. For everyone else — a laptop, a CFW Switch, and ten minutes — the card is simply unnecessary.

Next steps

• USB streaming mode — the full walkthrough for the lowest-latency setup.
• TCP Bridge mode for the best wireless experience.
• Install dvr-patches if your game blocks recording.

The address every player needs

Whatever player you use, the stream address is always the same pattern — the console’s local IP on port 6666:

rtsp://<SwitchIP>:6666/

You’ll find the console’s IP in the Switch’s Settings → Internet page (it shows the current connection details) or in your router’s list of connected devices. Simple Network is the default mode, but if you changed modes before, set it back in SysDVR Settings on the console (full build) — USB-Only builds don’t offer network modes at all.

mpv — the recommended player

The official guide recommends mpv, because it can be told to prioritise latency over buffering. Point it at the stream with the author’s low-latency flags:

mpv --profile=low-latency --no-cache --cache-secs=0 --demuxer-readahead-secs=0 --cache-pause=no rtsp://<SwitchIP>:6666/

You can also choose the transport protocol: --rtsp-transport=udp for the lowest latency on a clean network, or TCP if your Wi-Fi is congested and UDP gives you artefacts and dropouts. The flags above disable the caches that otherwise add seconds of delay, which is exactly what you want when you’re actually playing through the stream rather than just watching.

VLC

VLC works too: use Media → Open Network Stream, paste the rtsp://…:6666/ address, and play. Expect noticeably more delay than mpv with the flags above — VLC buffers network streams conservatively and is best here for watching or testing, not for playing action games through the stream.

OBS Studio

OBS can take the RTSP address directly as a Media Source: add the source, untick “Local File”, and paste the stream URL as the input. Know the cost before you build a setup on it — OBS adds buffering delay to media sources, so the preview you play from will lag behind the console. For broadcasting that’s usually acceptable (your commentary setup matters more), but for playing through OBS, a client mode feeding OBS is the better architecture; see streaming to Twitch & YouTube with OBS.

When to choose Simple Network mode

• Devices with no SysDVR client: iPhone and iPad (there is no iOS client — RTSP players are the workaround, covered in SysDVR on iPhone & iPad), smart TVs, and spare laptops.
• Quick checks: verifying the sysmodule works before installing anything else.
• Casual viewing: a second screen for someone watching you play, where a little delay doesn’t matter.

When latency matters — rhythm games, fighters, anything twitchy — switch the console to TCP Bridge mode with the client, or go all the way to USB mode. Simple Network’s job is reach, not speed.

A practical tip regardless of player: because the address is just an IP, save it as a bookmark, playlist entry or OBS scene now, while it works. If it ever stops connecting weeks later, the most likely change is the console’s IP being reassigned by your router — ten seconds to check, and the checklist below covers it.

Player choices compared

What quality to expect

The stream itself is the same one SysDVR always produces: 720p at 30fps, H.264 video with uncompressed 16-bit 48 kHz stereo audio. Simple Network doesn’t lower the resolution — the difference from the client modes is delay and smoothness under load, because a general-purpose player buffers more and optimises for playback rather than interaction. For watching, recording a casual session, or putting gameplay on a TV in another room, most people never notice. For playing a platformer through the stream on a big TV across the house, you’ll feel the extra delay in jumps and parries — that’s your cue to use a client mode on that device instead.

If the player won’t connect

• Check the mode. The console must be in Simple Network mode (Settings app) — a console set to TCP Bridge or USB doesn’t serve RTSP.
• Check the IP. DHCP can reassign the console’s address after a reboot or router restart; re-read it from the console’s Internet settings and update the URL.
• Check the network. Player and console must be on the same local network, and the router must not isolate clients (guest networks and hotspots often do).
• Check the timing. The sysmodule starts about 20 seconds after boot; a connection attempt before that fails for the simplest of reasons.
• Expect a short wait for picture. The stream begins at the next keyframe (roughly every two seconds) — moving the in-game camera helps it lock on.

Next steps

• Install SysDVR on the console — if you haven’t done the console side yet.
• SysDVR Client setup (Windows) — the client unlocks the lower-latency modes.
• Full map of modes and guides: the SysDVR setup guide hub.

How it differs from the other network mode

SysDVR has two network modes. TCP Bridge (this guide) needs the SysDVR-Client app and is built for low latency. Simple Network mode serves a standard RTSP stream that any video player can open with no client, at the cost of higher latency. If you mainly play on the same desk or sofa, TCP Bridge is the one to set up; RTSP is better for casual viewing on phones and TVs — see the Simple Network (RTSP) guide.

Step 1 — Enable TCP Bridge on the console

1. Open the Homebrew Menu and launch SysDVR Settings.
2. Set the streaming mode to TCP Bridge and confirm it as the default if asked.
3. Make sure the console is connected to the same network as your PC or phone. (USB-Only builds can’t do this — they have no network modes and no settings app.)

Step 2 — Connect from the client

Open SysDVR-Client on your computer (Windows, macOS or Linux) or the Android app, and choose the Network connection. The client listens for the console’s discovery broadcast and lists it automatically — select it and the stream starts. From the command line, the equivalent is:

SysDVR-Client.exe bridge

Discovery works because the console advertises itself with a UDP broadcast on your local network. Two things follow from that: your router must let devices on the network see each other, and your firewall must let the client receive the broadcast — on Windows, allow SysDVR-Client when the firewall prompt appears (see the Windows setup guide).

If discovery doesn’t find the console: manual IP

1. Find the console’s local IP address in the Switch’s Internet settings or your router’s device list.
2. In the client, choose the manual connection option and type that IP.
3. The client remembers the last IP you entered manually (a v6.3 addition), so future manual connections are one click.

You can also turn discovery off entirely: placing an empty file at /config/sysdvr/no_adv on the SD card stops the console advertising itself, and you connect by IP only. That’s a deliberate privacy/setup choice for shared networks, not a fix you need at home.

Getting the best quality

Stream quality depends on your local signal strength on both devices — your internet speed is irrelevant, because nothing leaves your network. In practice the ranking is:

• Best: wired LAN for the console (a USB LAN adapter in the dock) and a wired or strong-signal PC.
• Good: console and PC connected to the same router, close by, on 5 GHz Wi-Fi.
• Weak: far from the router, through walls, or on congested 2.4 GHz — expect stutter, and work through the lag and desync fixes, including the client’s Disable A/V sync option.

One environment warning: public hotspots and many guest networks enable AP/client isolation, which blocks devices from seeing each other at all. Discovery and manual IP will both fail there no matter what you change on the console — use your own network.

You only set this up once. After that, day-to-day use is: wake the console, open the client, click your console in the list. Everything below is about making that first connection succeed — and knowing exactly which knob to turn if it doesn’t.

What you need

• The full SysDVR build on the console (USB-Only has no network modes).
• SysDVR-Client on Windows, macOS or Linux, or the Android app — same version as the console.
• Both devices on the same home network; a router that lets local devices see each other.

Playing docked, and other Bridge habits

TCP Bridge is the mode that fits how most people actually play: the console can sit in its dock feeding the TV while the same gameplay streams to the PC for recording or broadcasting — something USB mode can never do, since it stops working while docked. Once discovery works, connecting becomes a habit of two clicks: open the client, pick the console. If you regularly connect from a second room, favour the wired-LAN end of the quality scale — a USB LAN adapter in the dock for the console removes the weakest link for most homes.

When Bridge is not the answer

If your router isolates clients (common on mesh guest networks and ISP-router “guest” SSIDs), discovery broadcasts never arrive and even manual IP connections can be refused — no setting on the console fixes a router that hides devices from each other; move both devices to your main network. If latency still feels wrong on a good network, the lag and desync guide covers the A/V sync toggle and cache tweaks. And for a phone or TV with no client app, that’s what Simple Network mode exists for.

Next steps

• Client can’t find your console — the systematic fix list when discovery fails at home.
• USB streaming setup — even lower latency when you can play next to the PC.
• Stream to Twitch & YouTube with OBS — the next step once local streaming works.

Step 1 — Switch the console to USB mode

On the console, open the Homebrew Menu, launch SysDVR Settings, and set the streaming mode to USB. If you installed the USB-Only build, skip this step — that build is always in USB mode and has no settings app. Remember the sysmodule takes about 20 seconds after boot to start, so give it a moment before troubleshooting a mode change that “didn’t take”.

Step 2 — Install the driver (Windows, one time only)

Since the version 5.5 USB rewrite, the driver is installed from inside the client itself:

1. Launch SysDVR-Client on your PC (see the Windows client setup if you haven’t installed it yet).
2. In the client’s main menu, open the USB Driver option and click Install.
3. Unplug the console for a few seconds after the install finishes.

After installation the console shows up on the PC as an Android-style device — on some systems it appears as a “Google Inc. Nexus/Pixel (fastboot)” device, which is expected and harmless.

On other platforms there is less to do: macOS and Android receivers need no driver setup at all. On Linux, USB works through libusb plus a udev rule (99-sysdvr.rules) — and never run the client as root, which breaks audio; details are in the Linux client setup.

Step 3 — Use the right cable

Connect the console directly to the PC with a USB-A to USB-C cable. USB-C-to-USB-C cables are known to cause problems with SysDVR’s USB mode, so if a C-to-C cable is all you have and nothing connects, swap the cable before changing any software. Also connect the console undocked, in handheld form — the dock’s USB path doesn’t carry this mode.

Step 4 — Connect from the client

In the client’s GUI, choose the USB connection and it will attach to the console automatically. From the command line the equivalent is:

SysDVR-Client.exe usb

If more than one console is attached, specify which one with the --serial option alongside the usb command. Video not appearing instantly is normal for the first moments — the stream waits for a keyframe, produced roughly every two seconds, so move the in-game camera and give it a couple of seconds.

One conflict to know about

While SysDVR is using the USB interface, other USB homebrew tools — Goldleaf, nxmtp, Twili and similar — stop working, because they contend for the same interface. Switch the console back to a network mode in Settings when you need them (full build), or disable the sysmodule and reboot (USB-Only). We walk through it in Goldleaf / nxmtp stopped working. And if Windows doesn’t recognize the device at all, start with USB device not recognized on Windows.

This walkthrough assumes the full build on Windows for the driver section, since that’s where most readers are; the console-side and connection steps are identical on every platform, and platform differences are called out where they exist.

What you need

• SysDVR installed on the console — full build (switchable to USB mode) or the USB-Only build.
• SysDVR-Client on the receiving PC, version-matched to the console.
• A USB-A to USB-C cable that carries data, not a charge-only lead.
• On Windows, five minutes for the one-time driver install below. On macOS, nothing extra; on Linux, the libusb/udev setup from the Linux client guide.

When USB is the right choice

Pick USB when latency is the priority — fighting games, rhythm games, speedrun attempts — or when the Wi-Fi where you’re playing is crowded or weak, because a cable removes the network from the equation entirely. Pick a network mode instead when you want to play docked on the TV, sit away from the PC, or receive on a phone without a cable trailing across the room. Plenty of setups keep both configured: the mode is a Settings-app toggle on the console, so switching takes seconds. What USB will never do is work through the dock, and it locks out other USB homebrew while it owns the interface — plan around those two facts and it’s the most reliable mode SysDVR has.

First-connection checks

• Console awake and in a game (the Home menu is never captured — a black screen there is normal).
• Sysmodule given its ~20 seconds after boot to start.
• Cable swapped once if nothing enumerates — C-to-C cables are the classic culprit.
• Client and console on the same SysDVR version.

Next steps

• TCP Bridge mode — when you’d rather stream wirelessly with low latency.
• Lag, stutter & audio desync fixes — if the stream runs but feels wrong.
• Back to the setup guide hub for the full map of SysDVR guides.

Requirements

• Android 10 or newer on a 64-bit ARM device — that covers most modern phones. (v6.1 lowered the minimum to Android 8 for 64-bit devices, and v6.2 added 32-bit armeabi-v7a support, but Android 10+ 64-bit is the safe assumption.)
• About 106 MB of free space — the APK is 110,988,827 bytes.
• SysDVR installed on the console, the same version as the client (see the console install guide).
• The phone and the Switch on the same Wi-Fi network for network modes, or a USB cable for USB mode.

A caution for TV boxes and older hardware: the author notes that some older devices, such as smart TVs and streaming sticks, may not be supported and the app simply will not install. We cover that specific case in the SysDVR on Android TV guide.

Step 1 — Download the genuine APK

Get SysDVR-Client-Android.apk from our download page, which links the official GitHub release asset — nowhere else. If you want to verify the file before installing (a good habit for any APK), its SHA-256 for v6.3 is:

d9b668306ba604a4c61787cfff8f5909f7f0da32bfbb4ca4a6bbf6440e23b846

Any file with a different name pattern, a different size, or a matching name offered by an app store should be treated as suspect.

Step 2 — Install the APK

1. Open the downloaded APK from your browser’s downloads or a file manager.
2. Android will ask permission to install apps from that source, because the file didn’t come from the Play Store. Allow it for this install.
3. Tap Install. No other setup is needed — the Android client requires no configuration, drivers or accounts.

Step 3 — Connect to your console

Open the client and connect over the network: with the console in TCP Bridge mode, the client discovers it automatically on your local network. USB also works with an appropriate cable for the lowest latency. As on every platform, versions must match — a v6.3 console pairs with the v6.3 app — and the sysmodule needs about 20 seconds after the console boots before it appears.

Stream quality on a phone depends on your local signal, not your internet speed: the console and phone should both have a strong connection to the same router, ideally on 5 GHz Wi-Fi and in the same room.

Why does an official app live outside the Play Store at all? Because since v6.0 the author distributes the Android build exclusively through GitHub releases, alongside the desktop builds. That keeps every platform on the same version and the same release notes — but it also means anything in a store using the SysDVR name arrived there without the author, which is exactly why this guide insists on the GitHub file and its hash.

What the Android client can do

The Android client is a full SysDVR receiver, not a companion app: it connects to the console in the network modes and over USB, and displays the same 720p30 stream with 16-bit 48 kHz stereo audio as the desktop clients. Since v6.1 the client can also keep streaming with the screen off (handy when the phone is just a bridge to headphones or a recorder), and it can be navigated with a gamepad. What it can’t change are the console-side limits — no Android app makes SysDVR output 1080p or 60fps, because the limit is in the console’s recording hardware.

Safety notes for sideloading

• Source is everything. The only genuine source is the project’s GitHub releases (linked from our download page). If a site offers the APK with a downloader, a modded description, or a “pro” version, close the tab.
• Check the hash. The v6.3 SHA-256 is printed above; free hash-checker apps can confirm your file matches before you install it.
• Mind the permissions prompt. Installing from a file manager or browser is a one-app permission you control; you can revoke it right after installing.
• Keep it updated manually. A sideloaded app has no store updates — when you update the console sysmodule, download the matching new APK too.

Getting a smoother stream on your phone

The stream never leaves your local network, so your internet plan is irrelevant; what matters is signal. Put the phone and the console on the same router, prefer 5 GHz Wi-Fi, and stay in reasonable range. If the picture stutters or audio drifts, the fixes are the same as on desktop: try the client’s Disable A/V sync option and work through the lag, stutter and audio desync fixes. A wired USB connection removes Wi-Fi from the equation entirely and gives the lowest latency the Android client can offer.

Next steps

• Use your Android phone as a Switch monitor — the travel setup built on this client.
• TCP Bridge mode guide — how the recommended network mode and auto-discovery work.
• SysDVR on Android TV — big-screen receiving, and which boxes can’t install the client.
• No Android device? iPhone and iPad owners should read SysDVR on iPhone & iPad — there is no iOS app, but there is a working alternative.

Option A — Flatpak install (x64)

The Flatpak build has existed since version 5.5 and is still labelled experimental by the author, but it is the right first choice on any 64-bit Linux desktop. On Ubuntu, with the commands from the official guide:

1. Install Flatpak itself if you don’t have it: sudo apt install flatpak (other distros: use your package manager’s equivalent).
2. Download SysDVR-Client-Linux-x64.flatpak from the download page.
3. Install it as a user package:

flatpak --user install SysDVR-Client-Linux-x64.flatpak

Then launch it any time with:

flatpak run com.github.exelix11.sysdvr

You can create a shell alias for that command if you use it often. Keep the console and client on the same version — v6.3 with v6.3 — and remember the sysmodule takes about 20 seconds after the console boots before it can be discovered.

USB on Linux: libusb and the udev rule

USB streaming on Linux talks to the console through libusb, and your user account needs permission to access the device. The setup uses a udev rule file named 99-sysdvr.rules so the console is accessible without elevated privileges. Follow that rule’s setup rather than working around permissions, because of one specific trap:

The full USB flow, including switching the console to USB mode and cable advice, is in the USB streaming setup guide. Network modes (TCP Bridge and RTSP) need no device permissions at all.

Option B — Manual .NET install (Raspberry Pi & ARM)

Let’s be honest about this path before you start: it is a multi-step, terminal-heavy install with several exact-version dependencies, and the official guide ends its own walkthrough with “hope for the best”. Raspberry Pi 3 and 4 are supported this way; Pi 1 and 2 are not, because .NET doesn’t run on them. In outline, you need:

• .NET 8 or newer installed (mono and older .NET Core will not work).
• SDL2 and SDL2-image development packages: sudo apt install libsdl2-dev libsdl2-image-dev.
• libusb: sudo apt install libusb-1.0-0-dev.
• ffmpeg 5.1.x exactly, i.e. libavcodec59. A different ffmpeg version results in a “module not found” error at launch; if your distro doesn’t ship it, the fallback is building ffmpeg from source.
• The SysDVR-Client-dotnet.zip cross-platform build from the download page, extracted locally.
• A compiled CimguiSDL2Cross library copied into the matching runtimes/<platform>/native folder — or skip the new GUI by launching with the --legacy option, which shows a simple video player instead.

With the dependencies in place you run the client from its folder with dotnet SysDVR-Client.dll. If dynamic libraries fail to load, --debug dynlib helps identify which one. Because every distro differs, treat the official wiki’s manual-install page as the reference for exact steps and use this section as the map of what you’ll need.

A note on expectations before you choose a route: the Flatpak is the author’s packaged build and behaves like the clients on other platforms. The manual route, by contrast, is a community-style assembly of dependencies around the cross-platform build — powerful because it reaches hardware nothing else supports, but every distro quirk along the way is yours to solve. Choose it for the hardware it unlocks, not as a first resort.

Which route should you take?

After installing: connecting

Launch the client and choose a connection mode, exactly as on other platforms. For TCP Bridge, the console advertises itself on the local network and the client lists it automatically; if your Linux firewall is restrictive, remember the discovery is a UDP broadcast, so a default-deny inbound policy can hide the console until you allow local traffic. For USB, the udev rule above is what makes the console visible to your user account. And as everywhere: console and client versions must match, and the sysmodule needs its ~20 seconds after boot before it can be found.

Updating the Flatpak

There is no in-app updater. Updating means downloading the newer .flatpak file from the release and installing it the same way — flatpak --user install replaces the previous version in place, and your launch command stays flatpak run com.github.exelix11.sysdvr. Update the console sysmodule in the same sitting and reboot the console, so both sides land on the same version together.

Next steps

• TCP Bridge mode guide — recommended network streaming with automatic discovery.
• Simple Network (RTSP) mode — no client needed at all; mpv on Linux handles it well.
• Windows client setup and macOS client setup for your other machines.
• Haven’t installed the console side yet? Start with how to install SysDVR on the Switch.

Step 1 — Pick the build for your chip

There are two separate macOS builds, and they are not interchangeable:

Not sure which you have? Open the Apple menu → About This Mac: if the chip line says “Apple M…” you want the arm64 build; if it names an Intel processor, take the x64 build. Both are on the download page, which links the official GitHub release.

Step 2 — Extract and launch

1. Double-click the downloaded zip to extract it.
2. Open the extracted folder and launch the SysDVR-Client file.
3. With SysDVR running on the console, pick your connection mode in the client — Network for TCP Bridge, or USB for a cable connection.

That is the whole setup on most machines. Receiving a USB stream on macOS needs no driver installation (unlike Windows), and network modes need nothing beyond both devices being on the same network.

If macOS blocks the app: add a signature exception

Because the app is not signed with an Apple developer certificate, Gatekeeper may say it cannot be opened or cannot be verified. The official wiki points to Apple’s own documented remedy: open System Settings → Privacy & Security, scroll to the message about the blocked app, and click Open Anyway, then confirm. You only need to do this once. Avoid blog advice telling you to disable Gatekeeper system-wide — the per-app exception is enough and much safer.

If it still won’t run: self-sign the dylib files

On some machines the app is allowed but its bundled libraries are rejected. The official fix is to self-sign the dylib files. Open Terminal inside the runtimes/osx-…/native folder of the extracted client (the folder name starts with osx- and matches your chip — there is only one, so you can’t pick wrong), then run:

codesign --remove-signature -v *.dylib
codesign -s - -v *.dylib

The first command strips the existing signatures, the second applies an ad-hoc signature your own Mac trusts. Relaunch the client afterwards. This is a local signature for your machine only — it doesn’t modify what the app does.

Version matching still applies

As on every platform, the client version must match the sysmodule version on the console — v6.3 with v6.3. If you update the console side, download the matching Mac build too, and reboot the console after updating it. If you haven’t installed the console side yet, start with the SysDVR install guide.

One more reassurance if you’re coming from Windows guides: there is no macOS equivalent of the MSVC redistributables step, and no .NET to install either. The zip you download is the whole application. If it runs, you’re done with installation — everything after that is connection choices, covered in the mode guides linked below.

Connecting once the client runs

With the client open and SysDVR running on the console, choose your mode. Network connects to a console set to TCP Bridge mode and finds it automatically on your local network. USB connects over a cable — and on macOS there is no driver step at all, unlike Windows. If the console list is empty, work through the boring causes first: both devices on the same Wi-Fi, the console booted more than 20 seconds ago (the sysmodule starts slowly), and matching versions on both sides.

macOS firewall prompts

macOS may ask whether SysDVR-Client may accept incoming network connections. Allow it — the client needs to hear the console’s discovery broadcast and receive the stream. If you dismissed the prompt and discovery never works, you can allow the app later under System Settings → Privacy & Security → Firewall. This is separate from the Gatekeeper “unsigned app” prompt in the steps above; a Mac can show you both, once each.

Quick troubleshooting list

• “Cannot be opened because the developer cannot be verified” → the Privacy & Security → Open Anyway exception above.
• App opens, then closes or errors on libraries → self-sign the dylib files with the two codesign commands above.
• Client opens but no console appears → same network, wait past the ~20-second sysmodule start, check version match, allow the firewall prompt.
• Stream connects but stutters → that’s connection quality, not the Mac build; get closer to the router or use 5 GHz, see the lag and desync fixes.

Keeping the Mac client updated

There is no auto-updater and no installer to re-run: updating means downloading the new zip for your chip and replacing the old extracted folder. If Gatekeeper treats the fresh copy as a new unsigned app, it may ask for the Open Anyway exception once more — annoying, but the same one-minute fix. Always update the console sysmodule in the same sitting so the pair stays on the same version.

Next steps

• TCP Bridge mode — the recommended, lowest-hassle network mode.
• USB streaming setup — lowest latency over a cable; remember USB doesn’t work while the console is docked.
• Simple Network (RTSP) mode — stream to a player like mpv with no client at all.
• Using a Linux machine instead? See the Linux client setup.