OBS Background Removal Without a Green Screen

OBS Studio has no background removal built in — what people mean by "OBS background removal" is one of two add-ons: a community plugin that runs a segmentation model on your CPU or GPU, or NVIDIA Broadcast feeding OBS an already-processed camera. Both work in real time on a live stream. Both also have a hard quality ceiling that no setting gets you past, and it's worth knowing where that ceiling sits before you spend an evening on sliders.

Real-time and post-production are different problems

Real-time removal has one video frame and about 16 milliseconds to decide which pixels are you. Offline matting can look at the whole clip and spend seconds per frame. That budget difference — not the model quality — is why a live virtual green screen looks softer around hair than a rendered cutout.

Keeping the two apart saves a lot of frustration:

If you're streaming, the plugin below is the right tool and this guide will get it set up properly. If you're recording footage to edit later, you are not solving a real-time problem at all — record clean and matte it afterwards, where our video background eraser can produce a transparent clip instead of a pre-composited one.

How to install the OBS Background Removal plugin

The community plugin is obs-backgroundremoval, maintained by Roy Shilkrot. It runs a portrait segmentation neural network on each frame and turns the result into a transparency mask on your camera source — a virtual green screen with no green screen.

Installation depends on your platform:

• Windows — download the release build, then place the obs-backgroundremoval folder into C:/ProgramData/obs-studio/plugins. Restart OBS Studio; the filter will not appear until you do.
• Linux (Flathub) — run flatpak install com.obsproject.Studio.Plugin.BackgroundRemoval, then restart OBS.
• macOS — install the signed release package for your architecture and restart OBS.

The current release line is 1.4.x. If the filter doesn't show up after a restart, the folder almost always landed one level too deep or too shallow inside the plugins directory — that's the single most common install failure, ahead of anything version-related.

Once it's installed, add it as a filter rather than a source:

1. Right-click your camera source in the Sources list.
2. Choose Filters.
3. Under Effect Filters, click + and select Background Removal.
4. Pick a segmentation model — the smaller models cost less CPU and give a rougher edge.
5. Pick a backend: CPU runs through ONNX Runtime and works everywhere; GPU (CUDA) offloads the work to an NVIDIA card and is dramatically lighter on your processor.

How to tune the plugin for a clean edge

Raise the threshold until the background clears completely, then back it off one notch before it starts eating your shoulders. Everything else — feathering, smoothing — exists to hide the fact that a per-frame decision has no memory of the frame before it.

The controls that matter, in the order to touch them:

• Threshold — how confident the model must be that a pixel is you. Too low leaves background haze; too high carves into your outline. Set this first, in your real lighting.
• Feather / edge blur — softens the boundary so it doesn't look cut out with scissors. A small amount reads as natural; a large amount reads as a halo.
• Temporal smoothing — blends the mask across consecutive frames. This is the setting that stops the edge shimmering when you sit still, and it is the one most people never find.
• Model selection — if your edge is unfixably rough, you're on a small model. Move up one and watch your CPU.

Lighting does more than every slider combined. The model separates you from what's behind you, so contrast between your shirt and your wall is the actual input. A dark hoodie against a dark room is the hardest case there is, and no threshold value solves it. Adding a light behind you — even a cheap one, pointed at your shoulders and hair — will improve the mask more than any setting in the filter.

NVIDIA Broadcast and the other real-time options

NVIDIA Broadcast does the same job outside OBS: it creates a processed virtual camera that OBS then captures as an ordinary source. The catch is hardware — it requires an RTX card, and it will not run on a GTX.

The published requirements are specific enough to check before you download:

If you have the card, Broadcast is the smoother route: it runs on dedicated hardware, leaves your CPU free for encoding, and OBS just sees a camera. If you don't, the plugin's CUDA backend gets you most of the way on any NVIDIA GPU, and its CPU backend runs on anything at all.

A third option worth naming: an actual green screen. Fabric plus OBS's built-in Chroma Key filter beats every AI segmentation method on edge quality, costs less than a GPU upgrade, and uses almost no CPU. If your setup is permanent and you care about the edge, this is still the best-looking answer — and OBS has supported it natively for years, no plugin required.

How to remove a green screen in OBS with Chroma Key

If you do have a green screen, OBS removes it natively — right-click your source, choose Filters, add the Chroma Key effect filter, and set Key Color Type to Green. No plugin, no GPU requirement, and a cleaner edge than any segmentation model.

The four controls and what each one is for:

• Similarity — how close a pixel must be to the key colour to be removed. Raise it until the backdrop clears; lower it if your subject starts disappearing.
• Smoothness — softens the transition at the boundary. A little goes a long way; too much produces a visible halo.
• Key Color Spill Reduction — pulls the green cast off your hair and shoulders. This is the control that decides whether the shot reads as "keyed" or "composited".
• Opacity / Contrast / Brightness / Gamma — leave these alone until the first three are settled.

Two practical notes that fix most bad OBS keys. First, light the screen separately from yourself — an evenly lit backdrop is worth more than any Similarity value, and the single most common problem is a bright hotspot in the middle with dark corners. Second, get distance between you and the fabric, ideally a metre or more, so the green light bouncing off it does not land on your shoulders in the first place.

The same keying principles apply once you leave the stream and start editing recorded green screen footage — our guide to removing a green screen from video covers the offline side, where you get spill controls, matte refinement, and a transparent export that OBS's live filter cannot produce.

If you want to hide a green screen that is only partly in frame — a small backdrop that does not cover your whole camera view — add a Crop/Pad filter before the Chroma Key in the filter stack, or use the source's transform to cut the frame down to just the covered area. Chroma Key alone cannot help with the wall visible past the edge of your screen, because that wall is not green.

Where real-time removal hits its ceiling

Every real-time method decides each frame on its own, with no knowledge of the frames around it. That is why hair strands flicker, why glasses frames wobble, and why a raised hand sometimes half-disappears — the model isn't wrong, it's rushed.

The failures you should expect, and stop trying to fix with settings:

• Flickering hair edges — per-frame decisions on ambiguous pixels. Temporal smoothing reduces it; nothing removes it.
• Halo when you move quickly — motion blur makes edge pixels genuinely ambiguous within a single frame.
• Hands vanishing near your face — the model reads them as part of the background when they overlap your outline.
• Headphone and glasses edges — thin, hard-edged objects are the classic segmentation weak point.
• Frame drops after enabling the filter — a hardware limit, not a tuning problem. Switch backends or drop to a smaller model.
• The mask lags behind fast movement — the filter adds a frame or two of latency, which shows up as your outline trailing your actual position when you gesture quickly.

None of this is a reason to skip real-time removal for streaming. On a live stream, viewers are watching you talk, not auditing your hair. It is a reason not to use a live-composited recording as source footage you'll edit later — you've baked in every one of those artefacts permanently.

What to do with recorded footage that needs a real alpha channel

Record with the filter off, then matte the clip afterwards. An offline matting model has seconds per frame instead of milliseconds, and it outputs a real alpha channel rather than a background already burned into the picture.

The difference is not subtle when the footage has a second life:

• Live composite gives you a finished frame. The background choice is permanent, the edge artefacts are permanent, and you cannot change either later.
• Offline matte gives you a transparent clip. You can drop it on any background, in any editor, as many times as you like.

Our video background remover runs the Bria v3 matting model with no green screen needed and exports a transparent WebM with a real alpha channel that drops into OBS as a media source or into any editor as a layer. Short clips are free with no watermark and no sign-up; only longer videos draw on credits. The transparent video page covers what alpha output means, and the transparent export guide has a section on using transparent clips as OBS overlays specifically.

To be direct about the boundary: we do not do real-time removal. Nothing we make replaces the plugin during a live stream. What we do is the other half — the recorded clip, the overlay asset, the intro you'll reuse for a year — where a real alpha channel and per-strand edges are worth waiting a few seconds for. Streamers who care about both usually run the plugin live and matte their recorded assets separately.

Frequently asked questions

Does OBS have background removal built in?

Not for cameras without a green screen. OBS ships a Chroma Key filter that needs an actual green or blue backdrop. Removal without one requires the obs-backgroundremoval plugin or an external processor such as NVIDIA Broadcast.

Why is the Background Removal filter not showing up in OBS?

The plugin folder is almost always in the wrong place, or OBS was not restarted. On Windows the obs-backgroundremoval folder belongs in C:/ProgramData/obs-studio/plugins — one level too deep and OBS will not find it.

Do I need an NVIDIA GPU for OBS background removal?

No. The plugin's CPU backend runs through ONNX Runtime on any machine. An NVIDIA GPU with the CUDA backend simply moves the work off your processor, which matters a lot when you're also encoding a stream.

Does NVIDIA Broadcast work on a GTX card?

No. NVIDIA Broadcast requires an RTX-class GPU — RTX 2060, Quadro RTX 3000, TITAN RTX or higher — on Windows 10 64-bit or Windows 11 with driver 570 or newer. GTX cards are not supported.

Why does my OBS background removal flicker around the hair?

Real-time segmentation decides every frame independently, so genuinely ambiguous pixels like flyaway hair get classified differently from frame to frame. Temporal smoothing reduces the flicker by blending the mask across frames, but it cannot eliminate it.

Is a green screen still better than AI background removal in OBS?

For edge quality, yes. OBS's built-in Chroma Key on real green fabric produces cleaner edges than any real-time segmentation model and costs almost no CPU. AI removal wins on convenience and on setups where a backdrop isn't practical.

Can I get a transparent video file out of OBS?

Not from a live composite — OBS records the finished frame with the background already replaced. To get a file with a real alpha channel, record normally and matte the clip afterwards with a tool that exports transparency.