“But I saw a SysDVR overlay mentioned…”

Overlay menus (usually built on the Tesla framework) exist for several popular sysmodules, which is why people search for a SysDVR one. To be precise about what we verified: we checked the official SysDVR wiki and the project repository before writing this page, and there is no overlay component, no Tesla menu and no overlay hotkey in the official project. Anything offered elsewhere as a “SysDVR overlay” is not part of the official release — judge it accordingly, and never download SysDVR components from random packs when the real thing is free on the author’s GitHub (linked from our download page).

What you use instead: the SysDVR Settings app included with the full build switches streaming modes (Simple Network, TCP Bridge, USB, offline). Since v6.2.1 the sysmodule can also be started and stopped without a reboot via the Settings app / toolbox mechanism — that’s the closest thing to overlay-style control that officially exists. The USB-Only build has no Settings app at all, by design.

Why memory is the real topic

Sysmodules are background services that share a small pool of memory the system reserves for them — they don’t get the memory games use. Every sysmodule you install (FTP servers, overclocking tools, controllers, SysDVR) draws from that same limited pool, and if the stack doesn’t fit, the console can fail to boot after you add one more. Firmware 20.0+ reduced the memory available to sysmodules, so a combination that worked before a firmware update can stop fitting afterwards.

SysDVR’s footprint

Symptoms that you’re out of sysmodule memory

• Atmosphère won’t boot after copying a new sysmodule over. The official troubleshooting page names exactly this cause: too many sysmodules, or particularly heavy ones (it calls out sys-ftpd as an example).
• Boot fails started right after a firmware update — the FW 20.0+ memory reduction shrank the pool under an existing stack.
• One sysmodule silently not running while others work — check whether the Settings app reports SysDVR as started (and give it ~20 seconds after boot before concluding anything).

Our dedicated guide to the boot failure itself is Atmosphère won’t boot after installing SysDVR.

Managing a stack of sysmodules, safely

1. Know your folders. Each sysmodule lives in its own folder under atmosphere/contents/, named by title ID. SysDVR’s is 00FF0000A53BB665. Keep a note of which folder belongs to which tool before you need it.
2. Prefer USB-Only when stacking. If you run several sysmodules and mainly stream over USB, the ~500 KB build halves SysDVR’s footprint.
3. Remove before you add. Deleting a sysmodule = deleting its folder (deleting 00FF0000A53BB665 uninstalls SysDVR). If you’re unsure which folder is which, the official advice is blunt: remove the lot and reinstall a fresh Atmosphère plus only what you need.
4. Change one thing at a time, then reboot. Sysmodules load at boot, so every change needs a reboot to take effect — and changing one at a time tells you exactly which addition broke the stack.
5. Use start/stop instead of uninstalling. Since v6.2.1, SysDVR (full build) can be stopped from the Settings app — handy for the known conflict where SysDVR’s USB mode blocks USB homebrew like Goldleaf and nxmtp: stop or switch SysDVR’s mode instead of deleting anything (see that conflict explained).
6. After a firmware update, re-check the stack. Between the reduced memory pool and firmware-matched extras like dvr-patches, updates are when stacks break.

The bottom line

Skip the hunt for a SysDVR overlay — officially, there isn’t one, and the Settings app covers mode switching. Spend the effort on the sysmodule stack instead: keep it lean, reach for the USB-Only build when memory is tight, and your console will boot cleanly with SysDVR in the mix.

Where “sysmodule managers” fit in

The tooling around this is deliberately simple. Atmosphère itself provides a toolbox mechanism (sysmodules can ship a toolbox.json describing them), and since v6.2.1 SysDVR uses it: the full build can be started and stopped from its Settings app / toolbox integration instead of only at boot. That’s the supported management surface — start, stop, switch mode — and for most people it’s enough. Beyond that, “managing” sysmodules is file management: folders under atmosphere/contents/, added or removed deliberately, one reboot per change. Homebrew gallery apps may present those folders more prettily, but they don’t change the underlying memory math, so judge any of them as conveniences, not fixes.

Diagnosing a boot failure, step by step

1. Remove the folder of the sysmodule you added most recently (for SysDVR: atmosphere/contents/00FF0000A53BB665) and reboot. Nine times out of ten, the console boots — you’ve found the overflow point, not necessarily a faulty tool.
2. If it still won’t boot, remove the heaviest remaining sysmodules (the official troubleshooting page names sys-ftpd as the classic heavyweight) and retry.
3. Decide what you actually need running simultaneously. A stack of five always-on tools is a choice; most people need two.
4. Rebuild lean: add SysDVR back — as the USB-Only build if memory is the constraint — then re-add the others one reboot at a time.
5. If folder-hunting isn’t converging, the official fallback is to delete the whole atmosphere folder, install a fresh Atmosphère, and rebuild the stack from zero. Drastic, but deterministic.

And keep the 20-second rule in mind before diagnosing anything: SysDVR takes about that long to start after boot, and the USB-Only build has no Settings app to check — an apparently missing sysmodule is often just an impatient check. The “settings says not running” guide covers that false alarm.

Next steps

Full requirements for every platform are in SysDVR system requirements; files are on the download page; and the platforms hub ties the whole cluster together.

The full matrix

Console requirements in detail

SysDVR is a sysmodule loaded by CFW at boot. It runs on all Switch 1 revisions — launch models, V2, OLED and Lite — as long as the console runs Atmosphère (the author recommends the latest release). Mariko models (V2, OLED, Lite) reach CFW by a different route than launch models; the Mariko guide and Lite guide explain their prerequisites. Firmware 20.0 and later reduced the memory available to sysmodules, which is worth knowing if you run many of them. Console and client versions must match, and you should reboot the console after installing or updating.

Receiver requirements in detail

Windows

64-bit only. The standard client needs just the latest Microsoft Visual C++ redistributables — a persistent myth says you need .NET; you don’t, for the standard build. Only the cross-platform dotnet build requires .NET 8+ (plus SDL2 and ffmpeg’s libavcodec 5.1.x), and that’s a manual install aimed at unsupported architectures. For USB mode on Windows, the driver is installed from inside the client — see the Windows client setup guide.

macOS

Separate builds for Intel and Apple Silicon — download the one matching your Mac. The app is unsigned, so macOS may ask for a signature exception or require self-signing the libraries; the macOS setup guide walks through it. No driver setup is needed for USB mode on macOS.

Linux

The official build is a Flatpak for x64 (flatpak run com.github.exelix11.sysdvr); ARM machines like a Raspberry Pi use the manual dotnet build. USB mode needs libusb and the udev rule — and don’t run the client as root, which breaks audio. Details in the Linux setup guide.

Android

Android 10 or later on a 64-bit device is the safe requirement; v6.2 added 32-bit support for older hardware. The client is only distributed via GitHub — any store listing is unofficial. Older and smart-TV devices may not install it; the Android TV guide covers that case and the RTSP alternative. Note there is no iOS client — iPhone/iPad viewing works via RTSP players only.

What you do NOT need

• A capture card — that’s the alternative, not a requirement (see the comparison).
• .NET, for the standard Windows/macOS/Linux builds.
• A fast internet connection — network streaming is local-only.
• A powerful receiver — decoding a 720p30 H.264 stream is light work for any recent device.

The version-matching rule

One requirement cuts across every row of the matrix: the console sysmodule and the client must be the same SysDVR version. A v6.3 console build won’t talk properly to a v6.1 client. Update both sides together, reboot the console afterwards (sysmodules load at boot), and most “it suddenly stopped working” reports never happen. The update guide has the safe sequence.

Quick self-check: console side

• Switch 1 (launch, V2, OLED or Lite) — not Switch 2.
• Boots into Atmosphère (latest recommended).
• microSD with a few MB free for SysDVR’s files.
• If you run other sysmodules, headroom in the stack — full SysDVR is under 1 MB, USB-Only about 500 KB.
• For blocked games: dvr-patches matching your exact firmware.

Quick self-check: receiver side

• One of: 64-bit Windows (MSVC redistributables), Intel/Apple-Silicon Mac, Linux with Flatpak, or Android 10+ 64-bit phone/tablet.
• Same local network as the console for network modes — no AP isolation, no guest SSID.
• For the lowest latency: a USB-A→C cable and an undocked console, or a wired/5 GHz network path.
• Client version identical to the console’s SysDVR version.
• That’s all — no capture card, no account, no subscription; SysDVR is free and open source.

If you take one line from this page, take this one: the console side is where compatibility is decided, and the receiver side almost never is. Get a Switch 1 onto Atmosphère with matched versions, and nearly any computer or Android device you already own completes the setup — that’s the whole trick of SysDVR’s requirements.

Next steps

Check your console against the matrix, then get the matching files from the download page and follow the install guide. More per-device detail lives in the platforms hub.

The 10-second test

1. Launch the game on your hacked Switch and get into actual gameplay.
2. Long-press the capture button.
3. If the console saves a video clip, the game supports recording — and SysDVR will stream it.
4. If you get a message that recording isn’t supported (or nothing happens), the game blocks recording — see the dvr-patches section below.

That’s the whole compatibility check. There is no list to look up first: the test works on your own copy, on your firmware, in ten seconds. Do it before troubleshooting a black screen — our black screen fix guide starts from the same test.

The in-between cases

• Some games only stream in certain sections. A title may allow recording during gameplay but block it in cutscenes or specific modes, because the block-recording function is invoked per section. If a stream drops to black for a scene and returns after, you’ve met this case — it isn’t a connection fault.
• System software never streams. The Home menu, settings and other system UI are not captured; the feed covers supported gameplay, so expect black/blank output outside games.
• Homebrew needs a workaround. Homebrew launched through an album/applet path isn’t captured. Launching homebrew via title takeover (hold R while starting a compatible game) is the documented route to stream it.

What dvr-patches change

For games that block recording, the SysDVR author publishes dvr-patches — a set of exefs patches to the system module (am) that:

• Make games that don’t support recording behave as if auto-recording is enabled.
• Stub the function games use to block recording in certain sections, which also fixes the section-by-section dropouts above.
• Enable screenshots in games that had them disabled.

Three honest caveats, straight from the author: the patches are experimental; they are firmware-matched — each release targets specific Switch firmware, and you’ll usually need a fresh set after a firmware update; and a few games remain unsupported even with patches. The author maintains per-game fix/unsupported lists in the dvr-patches GitHub issues, which is the right place to check a specific stubborn title. Our dvr-patches install guide covers selection and installation.

Why there’s no giant compatibility table here

You may have seen per-game “works / doesn’t work” tables on other sites. We don’t publish one, deliberately: whether a game streams depends on the game, your firmware, and whether the current dvr-patches cover it — a static table goes stale and invents certainty nobody has. The capture-button test is definitive for your setup, and the dvr-patches issue lists are the maintained source for problem titles.

Testing a stack of games quickly

1. Boot each game and long-press capture in real gameplay — a saved clip means default support.
2. If recording is blocked, note the game and move on; you’ll handle all of them in one dvr-patches session afterwards.
3. For games that pass, also check a cutscene-heavy or menu-heavy section if you plan to stream story content — per-section blocks hide there.
4. After installing dvr-patches, re-test the blocked list on the spot; the patches take effect after a reboot.
5. Keep a short personal list. Your firmware + your patches + your library is a combination no website’s table can speak for — your own test results are the ground truth.

Worked yesterday, broken today: what changed?

Compatibility isn’t a property of the game alone — it’s game × firmware × patches. A Switch firmware update can break streaming for patched games until a firmware-matched dvr-patches release lands (the author updates them per firmware, sometimes a little after the firmware itself). A SysDVR update without a matching client update breaks the connection layer instead — console and client versions must always match. When something that worked stops working, ask which side changed: firmware, SysDVR, client, or the game itself, before reinstalling anything. Our update guide keeps the version-matching side painless.

Screenshots are a separate switch

Worth knowing if you mostly want stills: games control screenshots and video recording separately. A game can allow screenshots while blocking video (so it still won’t stream), and the dvr-patches set explicitly enables screenshots in games that had them disabled, alongside its recording changes. If your goal is screenshots for a guide or a thumbnail, you may already be covered even in games that refuse to stream — take the shot natively on the console.

A final practical tip: test the games you actually intend to stream before a session, not during it. Five minutes with the capture button across your current rotation tells you exactly where you stand — which titles are good to go, which need patches, and which sections to avoid — and turns “will it work?” from a worry into a known list.

Next steps

Run the capture-button test on your games, install dvr-patches for the stubborn ones, and check the full requirements if you’re starting from zero. The platforms hub covers every console and receiver combination.

Why the cap exists: where the video actually comes from

SysDVR doesn’t read your console’s screen or its HDMI output. It taps into the Switch’s built-in video recording service — the same system feature that records a clip when you long-press the capture button. That service was designed by Nintendo for short shareable clips, and it encodes at 720p, 30fps. SysDVR redirects that feed to your PC or phone in real time, but it cannot improve the feed: the recording service is the source, and 720p30 H.264 (with 16-bit 48kHz PCM audio) is all it ever produces.

That’s also why SysDVR only works with games that support native clip recording — it’s borrowing their recording pipeline, not capturing the display.

Nothing changes it — including the patches

• No client setting raises it. The client receives an already-encoded 720p30 stream; there is nothing higher-resolution to unlock on the receiving side. Upscaling the window or the OBS canvas stretches the picture — it doesn’t add detail.
• dvr-patches do not raise resolution or framerate. The author’s dvr-patches exist to let recording-blocked games stream at all (they make unsupported games behave as if recording is enabled and stub the function games use to block recording). Quality is untouched — a patched game streams at the same 720p30.
• No other SysDVR build or fork setting changes it, because the limit lives in the console’s recording service, not in SysDVR’s code.
• Docking doesn’t change it. A docked Switch outputs up to 1080p to a TV, but SysDVR never sees the dock’s output — its feed comes from the recording service, docked or not.

If you genuinely need 1080p60: a capture card

The only way to capture Switch gameplay at 1080p60 is to capture the dock’s video output with a capture card — dedicated hardware between the dock and your PC. It costs money and requires a dockable console (so no Switch Lite), but it’s a different category of capture: full dock resolution and framerate, works with every game, and doesn’t need CFW. Our SysDVR vs capture card comparison and capture card recommendations exist precisely for readers who hit this ceiling.

When 720p30 is genuinely fine

Plenty of real uses never hit the ceiling: streaming to Discord or friends, casual Twitch/YouTube broadcasts (platforms re-encode anyway), recording gameplay clips for guides, or putting a Switch Lite session on a monitor it could never otherwise reach. SysDVR is free, adds no hardware, and at 720p30 the picture is clean — it is simply not, and can never be, a high-framerate capture solution. (One quality-adjacent note: since v6.3, clips recorded in the client use AAC audio, so recordings play back on Windows without conversion — the audio side did improve, the video cap didn’t move.)

“But the game itself runs at 60fps…”

It may well — and it doesn’t matter. A game can render internally at 1080p and 60fps while docked, but SysDVR never sees the rendered frames. It sees the recording service’s output, and that service samples and encodes at 720p30 regardless of what the game is doing. Think of it as a fixed-format side channel: the game’s own performance lives on the other side of a wall, and the only thing coming through the wall is the recording feed. This is also why a more powerful receiver, a faster network or a better cable changes nothing — every link after the recording service can only carry what the service produced.

The settings people try — and why each fails

• Client quality options: the client can change decoders and playback behaviour, not the incoming resolution — the stream arrives as 720p30 H.264 and that’s what gets decoded.
• OBS output scaling to 1080p: produces a 1080p file containing a 720p picture. Platforms accept it; viewers get upscale softness, not detail.
• dvr-patches: they unlock recording in blocked games. Resolution and framerate are not patchable properties of the recording service — patches change whether a game streams, never how well.
• “Just dock it”: docking raises the TV output, not the recording feed. SysDVR’s stream is identical docked and undocked.
• A faster Switch: there is no faster Switch 1 variant for this — every model shares the same recording service, OLED included.

One thing that isn’t capped: audio

The 720p30 cap is about video. The audio side of the stream is uncompressed 16-bit PCM at 48kHz — full quality, no codec squeezed it. If your content is commentary- or music-driven, the sound your audience hears from a SysDVR setup is genuinely good; it’s the picture that lives within the recording service’s limits.

Next steps

If 720p30 fits your use, get started on the download page and check which games work. If it doesn’t, head to the capture card comparison — and browse the platforms hub for the full picture.

Option A: sideload the official Android client

The SysDVR Android client requires Android 10 or later on a 64-bit device (32-bit support was added in v6.2), and it is distributed only via the author’s GitHub — never through the Play Store or TV app stores. On an Android TV box that meets those requirements, sideloading the APK can work, and it gives you the client-based modes rather than just RTSP.

In practice, results vary a lot by device. Many TV boxes run 32-bit or older Android builds that fail the requirements, the interface is designed around touch rather than a TV remote, and performance depends entirely on your box’s hardware. Treat this route as a bonus if it happens to work on your hardware — not the plan. There is no official compatibility list of TV devices, and we won’t invent one.

Option B: an RTSP player on the TV (the reliable route)

1. On the console, open the SysDVR Settings app and set the streaming mode to Simple Network (the default mode). Use the full SysDVR build — USB-Only has no network modes.
2. Note the Switch’s IP address (console Settings → Internet, or your router’s device list).
3. On the TV or TV box, install an RTSP-capable player — VLC is available for Android TV and handles RTSP streams.
4. Open the player’s network-stream option and enter rtsp://<Switch IP>:6666/.
5. Start a recording-supported game on the console; the picture follows within a few seconds.

This works because Simple Network mode doesn’t need the SysDVR client at all — any player on any platform can receive it, which is also how iPhone and iPad viewing works. The RTSP mode guide has the full detail.

What to expect on the TV

• 720p30, like everywhere else. The stream is the console’s recording-service feed; a 4K TV won’t change that. See why 1080p/60fps isn’t possible.
• Some delay. Player buffering means the TV picture trails the console. Watching gameplay, spectating a family member, or putting a handheld session on the big screen: great. Playing fast games by looking at the TV: you’ll feel the lag.
• Network quality decides smoothness. The ranking from the official troubleshooting guidance: wired LAN is best, then console and receiver on the same router, then a nearby 5 GHz Wi-Fi connection. Internet speed is irrelevant — this is all local traffic.
• The console must be on the same network, and AP isolation / guest networks will block discovery.

Which route should you choose?

Our recommendation: try the RTSP player route first — it takes two minutes and asks nothing of your TV hardware beyond a player app. Only chase the sideloaded client if your box comfortably meets the Android 10+ 64-bit requirement and you specifically want the client modes on the TV.

Before you sideload: the 60-second box check

1. Open the TV box’s Settings → About and find the Android version. The client needs Android 10 or newer.
2. Check whether the system is 64-bit. The safe requirement is Android 10+ on a 64-bit device; many cheap TV boxes run 32-bit builds (32-bit client support exists since v6.2), and boxes on Android older than 10 are out either way.
3. Decide how you’ll control it. The client interface is built for touch; if your box ships only a basic remote, navigation may be the thing that stops you — another point for the RTSP route, which only needs a player you already control.
4. Confirm the box and the Switch can be on the same network, and if the TV can take a wired Ethernet connection, use it — wired is the top of the official connection-quality ranking, and a TV is the easiest device in the house to wire.

If neither TV route works well

Don’t force it. The strongest SysDVR receivers are the ones with official clients: an Android phone or tablet (APK setup guide), or a PC/Mac/Linux machine where the client gives you TCP Bridge and USB modes, fullscreen playback and recording. Many people run the client on a laptop connected to the TV by HDMI and get a better result than any TV-box workaround — the TV becomes just a display, and all the SysDVR parts run where they’re officially supported. The laptop-as-screen guide covers that pattern.

One last expectation to set: whichever route you choose, the TV shows the same feed every SysDVR receiver gets — there is no TV-specific quality boost, and no app to buy. If a listing or video promises a special “SysDVR TV edition” with higher resolution, it isn’t from the official project; the real client and the real requirements are exactly the ones on this page.

Next steps

Get SysDVR itself from the download page, set up Simple Network mode via the RTSP guide, and browse the platforms hub for other receivers.

That doesn’t leave iOS owners with nothing. SysDVR’s Simple Network mode broadcasts a standard RTSP stream that any compatible player can open — including players on iPhone and iPad. It works well for watching gameplay on a second screen, with a couple of honest limitations explained below.

How the workaround works

SysDVR has three streaming modes. Two of them — TCP Bridge and USB — require the official SysDVR client, which exists for Windows, macOS, Linux and Android only. The third, Simple Network mode, is the default mode and needs no client at all: the console serves an RTSP stream on your local network, and anything that can play an RTSP address can receive it. That includes VLC for iOS and other RTSP-capable player apps.

Setup, step by step

1. On the console, open the SysDVR Settings app and make sure the streaming mode is Simple Network (it’s the default). The full SysDVR build is required — the USB-Only build has no network modes and no Settings app.
2. Find your Switch’s IP address (console Settings → Internet shows it, or check your router’s device list).
3. Connect your iPhone or iPad to the same Wi-Fi network as the Switch.
4. In your RTSP player app (VLC for iOS works), open a network stream and enter: rtsp://<Switch IP>:6666/ — for example rtsp://192.168.1.50:6666/.
5. Launch a game that supports clip recording on the console. The picture appears in the player within a few seconds — the stream sends a keyframe roughly every 2 seconds, so give it a moment and move the in-game camera if the screen stays black briefly.

The same recipe works for any RTSP player on any device; our Simple Network (RTSP) mode guide covers the mode in depth, including using it with OBS on a computer.

The honest limitations

• Simple Network mode only. The lower-latency TCP Bridge mode and USB mode both need the official client, which doesn’t exist for iOS.
• Expect more delay than the official client. General-purpose players buffer the stream to keep playback smooth, so the picture can trail the console noticeably. Fine for spectating, replays and casual viewing; frustrating if you try to play through the iPhone screen.
• Same-network only. The stream lives on your local network — router AP isolation or a guest Wi-Fi network will break it, and it isn’t reachable over the internet.
• Quality is still 720p30. The feed is the console’s recording-service output, like every SysDVR mode — see the 1080p/60fps question. Audio is included in the stream.

How Android compares

Android is the only mobile platform with an official client: the SysDVR Android app supports the client-based modes and lower-latency playback, and it’s distributed only through the author’s GitHub — never app stores. If you have both an iPhone and an Android device, the Android device is simply the better SysDVR receiver. On iOS, the RTSP workaround above is the whole story, and for watching gameplay it genuinely does the job.

Getting the smoothest picture on iOS

• Use 5 GHz Wi-Fi, close to the router. The official guidance ranks connections: wired LAN best, then console and receiver on the same router, then a nearby 5 GHz signal. The iPhone can’t be wired, so proximity and band are your levers.
• Reduce player buffering if your app allows it. Some RTSP players expose a network-caching/buffer setting; lowering it trades a little smoothness for noticeably less delay — worth it if you interact with the game rather than just watch.
• Keep the console’s network clean. AP isolation or a guest network will hide the Switch from the iPhone entirely; both devices belong on the same regular home network.
• Record with iOS screen recording. If you mainly want clips on your phone, iOS’s built-in screen recording can capture the player window while the RTSP stream plays — a pragmatic workaround, at the stream’s 720p30 quality and with its delay baked in.

Troubleshooting the iOS RTSP connection

• Player can’t connect at all: double-check the console is in Simple Network mode (TCP Bridge mode does not serve an RTSP address), the IP is correct, and the iPhone is on the same network — not cellular, not a guest SSID.
• It worked on my computer but not the iPhone: check whether your router isolates wireless clients from each other (AP/client isolation), a setting that often treats phones differently from wired PCs.
• Black screen, then picture: normal at first — the stream sends a keyframe about every 2 seconds; moving the in-game camera helps the picture lock in.
• No picture in a specific game: the game blocks recording. Test with long-press capture; dvr-patches are the fix on the console side, not anything on the phone.
• Stutter: it’s the local network, not your internet plan — see the connection ranking above, and our lag and desync guide.

Next steps

Set the console to Simple Network mode with help from the Settings app guide, grab the files from the download page, and see the platforms hub for every other receiver option.

If you arrived here hoping to stream Switch 2 gameplay to your PC without buying hardware, the honest answer is that the free route doesn’t exist for this console yet. Below is why, and what actually works instead.

Why SysDVR can’t run on Switch 2

SysDVR works by living in the background of a hacked Switch 1: it’s a sysmodule loaded by custom firmware (Atmosphère) that intercepts the console’s built-in video recording service and forwards the feed to a PC or phone. Every part of that chain depends on CFW.

• No Switch 2 build exists. The official project (by exelix11, on GitHub) targets Switch 1 consoles running Atmosphère.
• There is no public CFW for Switch 2, so sysmodules — SysDVR or any other — cannot be loaded.
• Backward compatibility doesn’t help. Switch 2 can play Switch 1 games, but those games run in Nintendo’s own environment; that doesn’t give homebrew code background access to the system, which is what a sysmodule needs.

Be wary of any site offering a “SysDVR for Switch 2” download. There is no official one — at best it’s the Switch 1 build that won’t run, at worst it’s bundled junk. SysDVR releases come only from the author’s GitHub, the same source linked on our download page.

What actually works for Switch 2 streaming and capture

1. A capture card (the full solution)

The Switch 2 dock outputs video to a TV just like the original dock, so a USB capture card between the dock and your PC captures gameplay at the dock’s output quality — beyond anything SysDVR’s 720p30 feed ever offered. This is currently the only way to stream or record Switch 2 gameplay on a computer, and it’s the setup streamers use. Our SysDVR vs capture card comparison and capture card picks cover what to look for.

2. The console’s built-in capture (the free, limited option)

Like the original Switch, Switch 2 has a capture button that saves screenshots and short video clips you can share from the console itself. That covers “post a clip” needs, but it’s not a live stream to your PC and it won’t feed OBS or Discord.

3. Your Switch 1 library, with SysDVR

If you still own a hacked Switch 1, SysDVR remains completely free for that library — 720p30 streaming to PC, Mac, Linux or Android with no capture hardware. The install guide gets you running in minutes.

Will SysDVR ever come to Switch 2?

Nobody can honestly promise that. It would require a public way to run custom firmware on Switch 2 first, and then work by the SysDVR author or other developers. As of October 2026 neither exists, and this page will be updated if that changes. Until then, plan around the capture card route.

Questions people ask next

“My Switch 1 capture setup — will it work on Switch 2?”

Yes, on the hardware side. A capture card connects to the dock’s HDMI output, and the Switch 2 dock behaves like a normal video source: plug the card in the same way and your OBS scenes, overlays and recording settings carry over. This is also why the capture-card route is future-proof in a way a CFW tool can’t be — it never depended on hacking the console.

“What about Switch 1 games played on Switch 2?”

Still no SysDVR. Backward compatibility runs the game, but SysDVR isn’t part of the game — it’s a background service that has to be loaded by custom firmware on the console itself. Playing a Switch 1 cartridge on Switch 2 gives you the game, not the sysmodule environment, so there is nothing for SysDVR to attach to.

“Doesn’t Switch 2 share its screen with friends?”

Switch 2 does have built-in screen sharing with friends through its social features — handy for showing friends what you’re playing. But it shares to other Switch 2 users inside Nintendo’s system; it does not send a video feed to your PC, OBS or Discord, and it isn’t a recording pipeline. For a computer, the capture card remains the answer.

How to spot a fake “SysDVR for Switch 2” download

• The real SysDVR is only released on the author’s GitHub (exelix11/SysDVR), free, for Switch 1 CFW. A “Switch 2 version” offered anywhere contradicts the project’s own releases.
• SysDVR is never a Windows .exe you install to “enable” a console feature, and there is no official mobile-store app — console-side, it’s files copied to a microSD card, nothing else.
• Any page asking you to pay for SysDVR is a scam; the project is free and open source (GPL-2.0).
• If a download bundles “extra” installers or asks you to disable security software, close the tab.

Next steps

For Switch 2, start with the capture card comparison. For a hacked Switch 1, see the platforms hub and the download page.

The catch is entirely in that prerequisite. Mariko consoles cannot be hacked the way early launch-model Switches were, and that shapes what you need before any of the normal setup applies.

The honest prerequisite: a hacked console

Every SysDVR setup — on any model — starts with a console running CFW, with the latest Atmosphère recommended. On unpatched launch-model (V1) Switches, CFW is loaded through a well-known bootrom exploit. Mariko units (V2, OLED and Lite) patched that exploit, so in practice a Mariko console needs a modchip installed before it can run CFW at all.

This site doesn’t publish modchip installation guides, and we won’t pretend the step doesn’t exist: if your OLED is stock, SysDVR is not an option until the console runs CFW. If your OLED or V2 already boots Atmosphère, you’re in exactly the same position as a launch-model owner — everything below is identical.

Setup on OLED and Mariko: the standard process

1. Download the full SysDVR.zip from the download page and extract it to the root of your microSD card (sysmodule folder: atmosphere/contents/00FF0000A53BB665).
2. Reboot the console into Atmosphère and wait roughly 20 seconds for the sysmodule to start.
3. Open the SysDVR Settings app and choose a mode: Simple Network (RTSP, the default), TCP Bridge (recommended over network) or USB (lowest latency, undocked only).
4. Install the matching-version client on your PC, Mac, Linux machine or Android device and connect.
5. Launch a game that supports clip recording (long-press capture) to confirm the stream works.

Our full install guide walks through every step, and the Settings app guide explains each mode. Console and client versions must always match, and after updating either side, reboot the console.

Does the OLED screen change anything?

No — and this surprises people. SysDVR doesn’t capture your screen; it uses the console’s built-in video recording service, which produces a 720p, 30fps H.264 feed on every model. The OLED panel looks better in your hands, but the stream a receiver gets is the same 720p30 feed a launch Switch produces. If you want to understand the cap, see why SysDVR can’t do 1080p or 60fps.

One OLED-specific alternative is worth knowing: unlike the Switch Lite, the OLED docks and outputs up to 1080p to a TV, so a capture card is a genuine alternative on this model. Our SysDVR vs capture card comparison lays out when each makes sense.

Switch revisions at a glance

Good to know

• SysDVR uses very little memory — under 1 MB for the full build, about 500 KB for the USB-Only build — which matters if you run several sysmodules; see managing SysDVR alongside other sysmodules.
• Only games supporting native recording stream out of the box; dvr-patches extend that to many more titles.
• The Home menu and system screens are never captured — the feed covers supported gameplay only.
• Community reports say SysDVR itself does not seem to cause bans, but that is never a guarantee, and CFW carries its own risks.

If your Mariko console isn’t hacked yet

Then this is your decision point, and it’s worth being clear-eyed about it. Running CFW on a Mariko console means a hardware modification performed on the console itself — it’s not something software alone can do, and it’s not reversible in the way deleting an app is. Modifying a console can affect its warranty and how Nintendo treats it. This site’s position is simple: we document what SysDVR needs (a console already running Atmosphère) and how to use it well; the modding step itself belongs to dedicated hardware communities, and you should understand it fully before committing a console to it.

What we can promise is the other side of the decision: once a Mariko console runs Atmosphère, nothing about SysDVR is second-class. You get the same builds, the same clients, the same support in every guide on this site — the hardware revision stops mattering the moment CFW boots.

Day-to-day on a hacked OLED or V2

• Keep console and client versions matched. Mismatched versions are the most common cause of “it just stopped working” — after updating either side, reboot the console.
• Mind the sysmodule stack. Mariko consoles on modern firmware have a smaller sysmodule memory pool (firmware 20.0+ reduced it). SysDVR’s full build is under 1 MB, but if you run several background tools, the sysmodule management guide shows how to keep the stack lean — and the ~500 KB USB-Only build exists for exactly this.
• The dock is your alternative. OLED and V2 models dock (the Lite doesn’t), so a capture card remains an option for 1080p60 capture on these models — the one thing SysDVR can never do.
• Online play: community reports say SysDVR itself does not seem to cause bans, but that is a report, not a guarantee — and it says nothing about CFW in general. Treat any hacked console’s online use as your own risk decision.

Next steps

If your console already runs Atmosphère, head to the download page and the install guide. For the full compatibility picture, browse the platforms hub.

If your Lite already boots into Atmosphère, setup takes a few minutes and is identical to the standard process. If it doesn’t run CFW yet, that — not SysDVR — is the hurdle, and it’s worth understanding why the Lite actually benefits from SysDVR more than any other Switch model.

Why SysDVR matters more on the Lite

The Switch Lite has no dock support and no video output of any kind. It cannot be connected to a TV or a capture card — the hardware simply doesn’t route video out. That means every other way of getting Switch gameplay onto a bigger screen is closed to Lite owners.

SysDVR sidesteps the missing video output entirely, because it doesn’t use a video port at all. It taps into the console’s built-in video recording service and sends that feed over USB or your local network to a PC, Mac, Linux machine or Android device. For a Lite, streaming isn’t a convenience — it’s the only way to play on a monitor, record gameplay or share your screen with friends.

What you need

• A Switch Lite running CFW — the latest Atmosphère is recommended; other CFWs are unsupported.
• A microSD card with enough room for the SysDVR files (the full download is only about 3 MB).
• A receiver: a Windows PC, Mac, Linux machine or Android phone/tablet running the SysDVR client, or any device with an RTSP player for Simple Network mode.
• The current release from the SysDVR download page — console and client versions must match.

One honest note about the prerequisite: the Lite belongs to Nintendo’s revised (Mariko) hardware family, and getting CFW onto Mariko consoles is a different story from early launch models. This page doesn’t cover hardware modding — if your Lite already runs Atmosphère you’re ready; if it doesn’t, sort that out first. Our SysDVR on Switch OLED & Mariko guide explains the hardware-family side.

Setup: identical to a regular Switch

1. Download SysDVR.zip (the full build) and extract it to the root of your microSD card. The sysmodule lands in atmosphere/contents/00FF0000A53BB665.
2. Put the card back in the Lite and reboot into Atmosphère. Give SysDVR about 20 seconds after boot — the sysmodule takes a moment to start, so the Settings app may report it as not running at first.
3. Open the SysDVR Settings app and pick a streaming mode: Simple Network (RTSP) is the default, TCP Bridge is the recommended low-latency network mode, and USB gives the lowest latency of all.
4. Connect from your receiver — launch the SysDVR client, or point an RTSP player at rtsp://<your Lite's IP>:6666/ in Simple Network mode.
5. Test with a game: if long-pressing the capture button in that game records a clip, the game will stream.

The full walkthrough with screenshots of each client lives in our step-by-step SysDVR install guide, and mode-by-mode detail is in the TCP Bridge and USB streaming guides — everything there applies to the Lite unchanged.

Lite vs. regular Switch for SysDVR

Limits to know before you start

• 720p30 is a hard cap. The feed comes from the console’s built-in recording service, so no setting raises it — see why SysDVR can’t do 1080p or 60fps.
• Only games that support native clip recording stream out of the box. The author’s dvr-patches widen support for many others.
• The Home menu and system UI are never captured — the stream starts with supported gameplay.
• Community reports say SysDVR itself does not seem to cause bans, but that is not a guarantee, and CFW always carries its own risks.

Which mode suits a Lite best?

All three modes work on the Lite, but they fit different Lite lifestyles:

• USB — the lowest-latency connection, and the natural pick at a desk: the Lite sits next to your laptop anyway. Use a USB-A to USB-C cable; USB-C↔C cables are a known source of problems. The Lite never docks, so the “no USB while docked” restriction simply never applies to you.
• TCP Bridge — the recommended network mode, with automatic discovery in the client and lower latency than plain RTSP playback. Best for couch play where a cable is a nuisance.
• Simple Network (RTSP) — the flexible option: any player on any device can receive it, including TVs and iPads that have no SysDVR client. Expect more delay from player buffering.

If something doesn’t work: Lite quick hits

• Settings app says SysDVR isn’t running: wait. The sysmodule starts roughly 20 seconds after boot; check again before reinstalling anything.
• Client can’t find the console: console and client versions must match exactly, and both sides must be on the same network for network modes. After any update, reboot the console — sysmodules only reload at boot.
• Black screen in one game but not others: that game (or that section of it) blocks recording. Run the capture-button test and consider dvr-patches; our black screen guide works through the rest.
• Stutter on Wi-Fi: connection quality ranking is wired LAN first, then console and receiver on the same router, then a nearby 5 GHz signal. Internet speed has nothing to do with it — everything is local.

Next steps

Grab the files from the download page, follow the install guide, and browse the platforms hub for the receiver you plan to use.