Installing OBS Studio on a fresh Ubuntu box looks trivial until the first recording comes out as a black rectangle. Or the virtual camera never shows up in the browser. Or the encoder list is missing the one option that mattered. The install command is the easy part. What decides whether the setup survives a three-hour stream is how OBS was installed, which graphics stack it sits on, and how the machine is tuned around it.
Ubuntu 26.04 LTS, codenamed Resolute Raccoon, shipped on April 23, 2026, and Canonical’s release notes list standard security maintenance until April 2031. The 26.04.1 point release followed in August, which is the moment many cautious admins treat as the green light for production desktops and capture workstations. That makes now a good time to standardize a streaming or recording setup on this release.
There are three realistic ways to get OBS onto 26.04: the Ubuntu archive package, the official OBS Project PPA, and the Flatpak from Flathub. They behave differently. The OBS Project itself describes Flatpak and the PPA as its officially distributed Linux options. Each has trade-offs in update speed, plugin support, sandboxing, and hardware access, and those trade-offs bite hardest on a machine you can’t afford to rebuild mid-project.
This guide walks through all three, explains why you’d pick one, and then covers the work that happens after the install: encoder choice, Wayland capture, permissions, resource tuning, and a troubleshooting section built around the failures that come up repeatedly.
What to Check Before Installing
A few minutes of checking saves an hour of confusion later. Start with the basics.
Confirm the OS release and architecture
lsb_release -a
uname -mYou want Ubuntu 26.04 and x86_64. The Flathub listing for OBS Studio shows x86_64 as the available architecture, so ARM machines should check upstream notes before assuming the Flatpak path will work.
Update the system first
sudo apt update
sudo apt full-upgrade -y
sudo rebootRebooting matters more than people admit. If a kernel or Mesa update lands during the upgrade and you launch OBS before rebooting, the running kernel can mismatch the userspace graphics libraries. That produces strange capture or encoder failures that vanish after a restart.
Identify your GPU and driver
Hardware encoding is the biggest quality-of-life factor in OBS, so know what you have:
lspci -nnk | grep -A3 -Ei 'vga|3d|display'NVIDIA users should note one detail from recent OBS notes. The 32.2.2 release updated to NVIDIA SDK 13, which raises the minimum supported driver version to 570. If you run an older proprietary driver, NVENC may quietly disappear from the encoder list. Check your driver with:
nvidia-smiCheck your session type
echo $XDG_SESSION_TYPEThe answer, wayland or x11, determines which capture source you’ll use for screen recording. Wayland sessions use PipeWire portals instead of the old Xorg capture. More on that below.
Which Installation Method Should You Pick?
Pick on purpose. Don’t just paste the first command you find.
| Method | Update speed | Plugin support | Sandboxed | Best for |
|---|---|---|---|---|
Ubuntu archive (apt) |
Slowest, frozen per release | Good (native paths) | No | Stable workstations, managed fleets |
| OBS Project PPA | Fast, tracks upstream stable | Good (native paths) | No | Creators who want current features through APT |
| Flatpak (Flathub) | Fast, independent of the OS | Limited, plugins need Flatpak builds | Yes | Clean separation, easy rollback |
The OBS download page recommends the PPA command set for Ubuntu 24.04 and newer, and points to Flathub as the other official route. One third-party guide that covers 26.04 suggests starting with the Ubuntu repository for most users on that release, and notes that the PPA tracked the 32.1.x branch at the time of writing. Package versions move, so confirm what your mirror serves rather than trusting a blog post, this one included.
A rule of thumb from running capture machines: the more plugins you depend on, the more you want a native install. Flatpak sandboxing is excellent for security and miserable for plugins that expect to drop files into system paths. An OBS forum answer on this exact problem recommends removing the sandboxed version and installing natively from the official repository when plugins can’t be added to Flatpak.
Method 1: Install OBS Studio from the Ubuntu Repository
This is the least exciting route, and sometimes the right one. Packages in the archive are tested against the rest of the release, they get security attention through normal channels, and apt handles everything.
First see what version you’d get:
apt policy obs-studioIf the candidate version is acceptable, install it:
sudo apt install obs-studioThe package lives in the universe component, which is enabled on a default Ubuntu desktop. If apt claims it can’t find the package, enable the component:
sudo apt install software-properties-common
sudo add-apt-repository universe
sudo apt updateVerify the result:
obs --version
which obsWhy this route is worth considering
Consider a lab of twenty identical capture workstations. Nobody wants twenty machines drifting between OBS versions because someone ran a PPA update on a Tuesday. The archive package keeps the version frozen, so a profile that works today works next quarter. The cost is that new features, encoder fixes, and source improvements arrive late.
Method 2: Install OBS Studio from the Official PPA
For most individual creators, this is the sweet spot. You get upstream stable builds, and updates arrive through the same apt upgrade you already run.
The OBS Project’s published commands are:
sudo add-apt-repository ppa:obsproject/obs-studio
sudo apt update
sudo apt install obs-studioThat’s the sequence shown on the official download page. A slightly more careful version, which makes sure the dependencies are reachable, looks like this:
sudo apt install software-properties-common
sudo add-apt-repository --yes multiverse
sudo add-apt-repository --yes ppa:obsproject/obs-studio
sudo apt update
apt policy obs-studio
sudo apt install obs-studioThe apt policy step before installing is the habit that separates tidy admins from the rest. It prints which repository the candidate version comes from. If the PPA version is higher than the Ubuntu archive version, apt will prefer it. If you see no PPA line at all, the PPA may not yet publish a build for your release, and you should fall back to another method instead of fighting it.
A note on versions and support windows
OBS Studio 33.0 landed on October 23, 2026, with a major update to the embedded Chromium (CEF) component and improved plugin loading, and it retired support for Ubuntu 24.04 LTS. The latest stable before that, 32.2.2, was released August 14. Because Ubuntu 26.04 is the current LTS, it sits squarely on the supported side of that line. If you manage a mixed fleet with some 24.04 machines, expect those to stay on older builds.
Pinning the PPA package
Sometimes you want the PPA once and then no surprises. Hold the package after install:
sudo apt-mark hold obs-studioRelease the hold when you’re ready to update:
sudo apt-mark unhold obs-studio
sudo apt update && sudo apt install --only-upgrade obs-studioRemoving the PPA cleanly
sudo add-apt-repository --remove ppa:obsproject/obs-studio
sudo apt install ppa-purge
sudo ppa-purge ppa:obsproject/obs-studioppa-purge downgrades packages to the archive versions, which prevents the half-upgraded state that causes dependency headaches. If ppa-purge isn’t available for your release, a manual apt install obs-studio=<archive-version> with the specific version from apt policy does the same job.
Method 3: Install OBS Studio with Flatpak
Flatpak decouples OBS from the operating system. Ubuntu can upgrade underneath it while OBS keeps its own runtime. That’s a real benefit on a rolling-feature workflow.
Ubuntu doesn’t ship Flatpak enabled by default, so install it and add Flathub:
sudo apt install flatpak
sudo flatpak remote-add --if-not-exists flathub https://dl.flathub.org/repo/flathub.flatpakrepo
flatpak remotesInstall OBS Studio from the Flathub listing:
flatpak install flathub com.obsproject.StudioLaunch it:
flatpak run com.obsproject.StudioUpdate only OBS, leaving other Flatpaks alone:
flatpak update com.obsproject.StudioSandbox permissions you’ll want to know about
The Flatpak sandbox limits what OBS can see. That’s good for security and occasionally annoying for workflow. Inspect the current permissions:
flatpak info --show-permissions com.obsproject.StudioIf you record to a secondary drive, grant access explicitly rather than opening the whole filesystem:
flatpak override --user --filesystem=/mnt/recordings com.obsproject.StudioPrefer a narrow path over --filesystem=host. Handing a sandboxed app the entire disk defeats the point of choosing Flatpak.
The plugin catch
Plugins are the usual regret. Many third-party OBS plugins ship as source or .deb files that assume a native install. Under Flatpak, plugins must be packaged as Flatpak extensions or placed in the app’s user data directory in a compatible layout. If your workflow depends on a specific plugin, check how it distributes for Flatpak before committing to the sandbox.
First Launch: Configure It Properly
Run the Auto-Configuration Wizard once, but treat its output as a starting point. It tests your hardware and suggests settings, but it knows nothing about your upload quality or your disk.
Pick the right encoder
Open Settings > Output and switch Output Mode to Advanced. Then choose by hardware:
- NVIDIA GPUs: NVENC (the hardware H.264 or HEVC/AV1 options where your card supports them) offloads encoding from the CPU.
- AMD and Intel GPUs: VA-API based encoders, which rely on working Mesa drivers.
- No usable GPU encoder: x264 on the CPU, with a faster preset to protect frame pacing.
Software x264 gives excellent quality per bit, but it eats cores. On a machine that is also running a game, a browser, and a chat client, that matters. Hardware encoding costs a little efficiency in exchange for stable frame times, and for live streaming that’s usually the right bargain.
Recording format
Set the recording format to MKV or Fragmented MP4 instead of plain MP4. A crash or power loss with standard MP4 can leave an unplayable file because the index is written at the end. MKV survives interruptions, and you can remux to MP4 afterward from the File > Remux Recordings menu.
Sensible starting values
For a 1080p60 stream to a typical platform:
- Resolution: 1920×1080 output, base canvas matching the monitor
- Rate control: CBR
- Bitrate: match your upload speed, leaving at least 25 percent headroom
- Keyframe interval: 2 seconds
- Audio: 48 kHz, 160 to 320 kbps
Test your upstream before picking a bitrate:
sudo apt install speedtest-cli
speedtest-cliScreen Capture on Wayland and X11
Screen capture is where Linux installs of OBS most often disappoint new users, so it deserves its own explanation.
On an X11 session, Screen Capture (XSHM) works the way it always has. On a Wayland session, OBS uses the Screen Capture (PipeWire) source, which asks the desktop portal for permission each time you add it. A dialog appears, you choose a monitor or window, and PipeWire hands OBS the frames.
If that dialog never appears, the portal packages are the first suspect:
systemctl --user status pipewire wireplumber xdg-desktop-portalMake sure the portal backend for your desktop is installed. For GNOME:
sudo apt install xdg-desktop-portal xdg-desktop-portal-gnomeFor KDE Plasma, which Kubuntu 26.04 ships as Plasma 6.6:
sudo apt install xdg-desktop-portal xdg-desktop-portal-kdeLog out and back in afterward. Portal services start with the session, and restarting only OBS won’t pick up a freshly installed backend.
Game capture and Vulkan
For games, the Game Capture source is generally the better choice than full-screen capture because it hooks the application rather than the desktop. OBS 33.0 specifically improved detection of full-screen games in Game Capture mode, which should reduce the guesswork on newer builds. Games running through Steam’s Proton need to be launched with the capture layer visible to OBS, and sandboxed Flatpak installs add another layer that can hide the game process.
Audio Setup with PipeWire
Modern Ubuntu uses PipeWire for audio, with PulseAudio compatibility on top. OBS sees your devices through that layer. For a clean mix:
- Add Audio Input Capture for your microphone.
- Add Audio Output Capture for desktop sound, or use Application Audio Capture (PipeWire) to isolate a single program.
- Check the mixer meters while a test sound plays.
Application-level capture is the better habit when streaming. It stops notification dings and a stray video call from leaking into the broadcast. For deeper routing, tools like pavucontrol and qpwgraph let you see the actual graph:
sudo apt install pavucontrol qpwgraphA common mistake is capturing the monitor of a default sink and also capturing a physical microphone that picks up the speakers. The result is an echo. Wear headphones for streaming, or use application capture and keep speakers silent.
Virtual Camera Setup
The virtual camera lets OBS act as a webcam in video calls and browsers. On Linux it depends on the v4l2loopback kernel module.
sudo apt install v4l2loopback-dkms v4l2loopback-utilsLoad the module with labels that browsers recognize:
sudo modprobe v4l2loopback devices=1 video_nr=10 card_label="OBS Virtual Camera" exclusive_caps=1The exclusive_caps=1 option is the one people forget. Without it, Chromium-based browsers and conferencing tools often refuse to list the device. To make the settings persist across reboots:
echo "v4l2loopback" | sudo tee /etc/modules-load.d/v4l2loopback.conf
echo 'options v4l2loopback devices=1 video_nr=10 card_label="OBS Virtual Camera" exclusive_caps=1' | sudo tee /etc/modprobe.d/v4l2loopback.confIf Secure Boot is enabled, DKMS modules must be signed or the kernel will refuse to load them. Ubuntu’s DKMS tooling walks you through enrolling a Machine Owner Key at install time. Skip that prompt and the module will fail to load, and the symptom is a silent absence of the camera. Check with:
mokutil --sb-state
dmesg | grep -i v4l2loopbackTroubleshooting Common OBS Problems on Ubuntu 26.04
Black screen when capturing the display
On Wayland, this typically means the PipeWire portal flow failed or you’re using the wrong source. Use Screen Capture (PipeWire) rather than the X11 source. Confirm portals are running:
systemctl --user status xdg-desktop-portalRestart them if needed:
systemctl --user restart xdg-desktop-portal xdg-desktop-portal-gnome pipewire wireplumberIf you recently changed the screen-share selection, delete the saved permission:
flatpak permission-reset com.obsproject.StudioThat command applies to Flatpak installs only. For native installs, relogging usually clears a stale portal state.
NVENC missing from the encoder list
Check the driver version first. Since the 570 minimum introduced with recent builds, an older driver is the leading cause. Verify:
nvidia-smiUpdate through Ubuntu’s driver tool:
sudo ubuntu-drivers devices
sudo ubuntu-drivers install
sudo rebootOn Flatpak, the NVIDIA GL runtime must match the host driver version. If flatpak install didn’t pull it, list available runtimes with flatpak search nvidia and install the one matching nvidia-smi.
“Failed to open VA-API device” on AMD or Intel
Install the media driver packages:
sudo apt install vainfo mesa-va-drivers intel-media-va-driver-non-free
vainfoIntel users on newer generations may need intel-media-va-driver-non-free, which lives in multiverse. AMD users rely on mesa-va-drivers. If vainfo fails, OBS has no chance.
Virtual camera does not appear
Walk through the checklist: module loaded (lsmod | grep v4l2loopback), exclusive_caps=1 set, Secure Boot signing handled, and the browser restarted after the module loaded. Browsers enumerate devices at launch.
Crackling or out-of-sync audio
Mismatched sample rates between OBS (48 kHz) and a device locked at 44.1 kHz cause drift. Align them in Settings > Audio, and check PipeWire’s config:
pw-metadata -n settings 0Applying an audio sync offset in the advanced audio properties window fixes constant delay. Variable drift usually points to a USB hub or a cheap interface.
Dropped frames and “encoding overloaded”
Work from cheapest to most expensive: lower the preset, move to hardware encoding, reduce resolution or FPS, close browsers with heavy tabs, and check thermal throttling with:
sudo apt install lm-sensors
sensorsLaptops especially throttle after several minutes under load, and that creates a failure that only appears during long sessions.
OBS won’t start from the terminal
Launch it from a terminal and read the output. This single habit solves more problems than any forum thread:
obs 2>&1 | tee ~/obs-debug.logFor Flatpak:
flatpak run com.obsproject.Studio 2>&1 | tee ~/obs-debug.logLog files also live in ~/.config/obs-studio/logs/. Attach the latest one when you ask for help. Upstream developers want logs, not descriptions.
Dependency conflicts after adding the PPA
If apt reports held-back or broken packages, run:
sudo apt update
sudo apt --fix-broken install
apt policy obs-studio ffmpegMixed sources for FFmpeg libraries are a classic culprit. Resolve by purging the PPA as described earlier or switching to Flatpak, which brings its own libraries.
