Yes — SysDVR works on the Switch OLED and every other Mariko-based Switch (the revised V2 model and the Switch Lite), as long as the console is running custom firmware. SysDVR is a sysmodule that runs under CFW, and it doesn’t distinguish between hardware revisions: if Atmosphère boots, SysDVR can run.
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
- Download the full SysDVR.zip from the download page and extract it to the root of your microSD card (sysmodule folder:
atmosphere/contents/00FF0000A53BB665). - Reboot the console into Atmosphère and wait roughly 20 seconds for the sysmodule to start.
- 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).
- Install the matching-version client on your PC, Mac, Linux machine or Android device and connect.
- 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
| Model | Hardware family | Typical CFW path | SysDVR once on CFW |
|---|---|---|---|
| Switch (2017 launch, unpatched) | V1 (Erista) | Bootrom exploit, no chip | Fully supported |
| Switch V2 (2019 revision) | Mariko | Modchip required | Fully supported |
| Switch OLED | Mariko | Modchip required | Fully supported |
| Switch Lite | Mariko | Modchip required | Fully supported — see the Lite guide |
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.