Cloud OBS VPS Setup: Run OBS Studio Remotely for Streaming

Published on | Updated

Run OBS Studio on a Linux VPS for 24/7 and remote streams: XFCE, TigerVNC behind an SSH tunnel, OBS from its PPA or Flatpak, relays, auto-start and monitoring.

cloud obs vps streaming setup 2026

Quick answer: "OBS cloud" means OBS Studio running on a remote server. OBS Studio is desktop software for Windows, macOS and Linux, and the OBS Project offers no hosted version, so you run the normal app on a VPS inside a virtual desktop. Install XFCE and TigerVNC, install OBS from its official PPA on Ubuntu 26.04 (or the Flatpak from Flathub on Ubuntu 24.04 and Debian 12), and reach the desktop through an SSH tunnel, because TigerVNC listens only on localhost by default. A regular VPS has no GPU, so OBS renders and encodes on the CPU: how many vCores you need depends on your resolution, frame rate, x264 preset and scenes, so test with your own stream before you settle on a plan.


OBS Cloud: What It Means

OBS Studio is a desktop program. The OBS download page lets you pick Windows (10 and 11), Mac (macOS 13.0 and newer) or Linux (the Flatpak on Flathub and a PPA for Ubuntu 26.04 and newer), all on version 33.0.1, released on 29 October 2026. The page lists no browser or hosted edition. So when people search for "OBS cloud", "cloud OBS" or an "OBS cloud server", they mean one of two setups:

  • OBS on a VPS you set up yourself. You rent a Linux server, give it a virtual desktop and control OBS from your own computer. The rest of this guide covers that, step by step.
  • A streaming machine with OBS already on it. Someone else installs the desktop and OBS, and you get a remote screen to work on.

Either way it is the same OBS. Your scenes, sources, stream key and plugins live on the remote machine instead of on your PC, and that machine keeps the stream going after you switch your PC off.

Managed Option

If you would rather not set up VNC and SSH yourself, our streaming VPS comes with OBS preinstalled and opens in your web browser. Unlike the regular VPS in this guide, those machines have graphics, but most plans share them with other customers and the hardware differs per machine, as the plan page explains. A graphics card of your own is only available on request through a support ticket.


Why Run OBS on a VPS?

Running OBS locally has limitations:

  • Eats your CPU/GPU while gaming
  • Requires your PC running for 24/7 streams
  • Home internet can be unreliable
  • Electricity costs add up for a PC that is on day and night

Cloud OBS solves these:

  • Encoding on the server instead of on your gaming PC
  • Data center uplink instead of your home upload
  • Access from anywhere through an SSH tunnel (laptop, tablet, or a phone with an SSH app)
  • Datacenter power and cooling instead of your living room
  • No hardware to buy up front, just a monthly fee

Use Cases for Cloud OBS

Use CaseDescriptionWhy Cloud OBS
24/7 Radio/TVLo-fi streams, ambient channelsRuns without your home PC
Remote productionStream from anywhereAccess OBS via phone/laptop
Gaming streamsSend one feed from your PC, re-encode on the VPSOverlays and outputs run on the VPS
Multi-cam eventsChurch, conferencesCentral production hub
Backup streamingFailover if home failsRedundancy for important streams
Team streamingMultiple operatorsEveryone can access same OBS

How Big a VPS You Need

OBS on Linux needs OpenGL 3.3 or later. A regular VPS has no GPU, so inside a VNC desktop OpenGL runs through Mesa's llvmpipe, a software rasterizer that draws on the CPU cores. OBS's own performance guide explains that OBS composites and renders scenes on the GPU because GPUs are far more efficient at it than CPUs; on a VPS, scene rendering and x264 encoding both come out of your vCores. Once the desktop runs (Step 4), glxinfo | grep "OpenGL" in a terminal there shows which OpenGL version you get (glxinfo is in the mesa-utils package).

What raises the CPU load:

  • a higher output resolution and frame rate
  • a slower x264 CPU Usage Preset (faster presets are less demanding)
  • heavy scenes: browser sources, large media files and filters

OBS's guide suggests lowering the output resolution, going from 60 to 30 fps and building simpler scenes when OBS cannot keep up. So size the VPS by testing rather than from a table: run your real scenes at the resolution you want for an hour, open View → Stats, and watch CPU Usage, "Skipped frames due to encoding lag" and "Frames missed due to rendering lag". If those frame counters keep climbing, switch to a faster preset, a lower resolution or frame rate, or a plan with more vCores. Leave RAM for XFCE, the VNC server and any browser sources next to OBS.


Step 1: Choose Your VPS

Order a VPS with:

  • Ubuntu 26.04 LTS. OBS's download page names two official Linux builds: the Flatpak on Flathub and a PPA for Ubuntu 26.04 and newer. OBS 33.0 (23 October 2026) removed support for Ubuntu 24.04, so the PPA's last build for 24.04 is OBS 32.2.0, and for 22.04 it is 30.2.3 from August 2024. On Ubuntu 24.04 or Debian 12, install the Flatpak in Step 6.
  • Enough RAM for OBS, the desktop and your sources (see above)
  • Location close to your audience (or streaming platform servers)

Space-Node VPS plans are KVM servers with full root access and a 1 Gbps port, on AMD EPYC 7452 (Standard) or Ryzen 9 9950X (Premium), in an EU data center: a central location if most of your viewers are in Europe.


Step 2: Initial Server Setup

SSH into your VPS:

ssh root@YOUR_VPS_IP

Update the system:

apt update && apt upgrade -y

Create a non-root user (recommended):

adduser streamer
usermod -aG sudo streamer

Step 3: Install Desktop Environment

XFCE is lightweight and works great for remote OBS:

apt install xfce4 xfce4-goodies dbus-x11 -y

For a slightly more modern look, you can use XFCE with arc-theme:

apt install arc-theme papirus-icon-theme -y

Step 4: Install VNC Server

TigerVNC gives you a virtual desktop:

apt install tigervnc-standalone-server tigervnc-tools -y

tigervnc-tools contains vncpasswd; the server package only recommends it.

Switch to your user and set a VNC password:

su - streamer
vncpasswd

The password needs at least six characters, and only the first eight count. When vncpasswd asks whether you want a view-only password, answer n for now (see Multi-User Access below).

Create the VNC startup file. TigerVNC 1.15 on Ubuntu 26.04 reads it from ~/.config/tigervnc/xstartup; on Ubuntu 24.04 and Debian 12 the folder is ~/.vnc instead:

mkdir -p ~/.config/tigervnc
nano ~/.config/tigervnc/xstartup

Add this content:

#!/bin/bash
unset SESSION_MANAGER
unset DBUS_SESSION_BUS_ADDRESS
exec startxfce4

Make it executable:

chmod +x ~/.config/tigervnc/xstartup

Start VNC server:

vncserver :1 -geometry 1920x1080 -depth 24

Display :1 listens on port 5901 (5900 plus the display number). Because you did not pass -localhost no and the default security type is VncAuth, tigervncserver listens on localhost only: nobody can reach port 5901 from the internet, and neither can you directly. Step 5 connects through SSH.


Step 5: Connect Through an SSH Tunnel

TigerVNC's own service file warns against running VNC on an untrusted network and recommends limiting it to localhost and tunnelling over SSH. VncAuth protects the password with a challenge and response, but it is not one of TigerVNC's TLS security types, so the desktop itself is not encrypted.

On your local machine:

ssh -L 5901:localhost:5901 streamer@YOUR_VPS_IP

Leave that session open and point your VNC client at localhost:5901. The VNC traffic now runs inside the encrypted SSH connection, and port 5901 never has to be opened in the VPS firewall.


Step 6: Install OBS Studio

On Ubuntu 26.04 or newer, use the official PPA with the commands from OBS's download page:

sudo add-apt-repository ppa:obsproject/obs-studio
sudo apt update
sudo apt install obs-studio -y

On 4 November 2026 the PPA still had OBS 33.0.0 for Ubuntu 26.04, although the download page already lists 33.0.1.

On Ubuntu 24.04 or Debian 12, install the Flatpak from Flathub instead (it had OBS 33.0.1 on 4 November 2026):

sudo apt install flatpak -y
sudo flatpak remote-add --if-not-exists flathub https://dl.flathub.org/repo/flathub.flatpakrepo
sudo flatpak install flathub com.obsproject.Studio

Flathub's setup page asks you to restart once after adding the repository. This build starts with flatpak run com.obsproject.Studio; use that wherever this guide runs obs. The scripts below are written for the PPA build.

Also install these helpers:

# VLC for video sources
sudo apt install vlc -y

# FFmpeg for recording/streaming
sudo apt install ffmpeg -y

# PulseAudio for audio management
sudo apt install pulseaudio pavucontrol -y

Step 7: Connect and Configure OBS

Connect via VNC Client

Open the SSH tunnel from Step 5, then connect your VNC client to localhost:5901. A direct connection to YOUR_VPS_IP:5901 is refused, because the server only listens on localhost.

VNC clients:

  • Windows: RealVNC Viewer, TightVNC
  • Mac: Screen Sharing, RealVNC
  • Linux: Remmina, TigerVNC Viewer
  • Mobile: VNC Viewer (iOS/Android), together with an SSH app that can forward the port

First OBS Launch

Open terminal in VNC session and start OBS:

obs

Run through the auto-configuration wizard:

  1. Select "Optimize for streaming"
  2. Choose your resolution (720p or 1080p)
  3. Let OBS test your system

Configure Stream Settings

Go to Settings → Stream:

For YouTube:

  • Service: YouTube - RTMPS
  • Server: Primary YouTube ingest server
  • Stream Key: (from YouTube Studio → Go Live → Stream)

For Twitch:

  • Service: Twitch
  • Server: the Auto entry at the top of the list (or the closest EU server)
  • Stream Key: (from Twitch Dashboard → Settings → Stream)

For Kick:

  • Service: Custom...
  • Server: the Stream URL from your Kick creator dashboard (Channel → Stream URL and Key)
  • Stream Key: (from the same page)

Configure Output Settings

Settings → Output → Streaming:

Encoder: x264
Rate Control: CBR
Bitrate: within your platform's limit (see below)
Keyframe Interval: 2
CPU Usage Preset: veryfast
Profile: main

Platform limits on 31 October 2026: OBS's built-in Twitch entry allows up to 6000 Kbps of video with a 2 second keyframe interval. Kick recommends 1,000 to 8,000 Kbps CBR with the veryfast preset and the main profile, and supports at most 8,000 Kbps, 1080p and 60 fps, in H.264 only. YouTube recommends a 2 second keyframe interval and, for H.264 at 1080p, at least 5 Mbps at 30 fps (14 Mbps recommended) or 6 Mbps at 60 fps (17 Mbps recommended).

Settings → Video:

Base Resolution: 1920x1080
Output Resolution: 1920x1080 (or 1280x720)
FPS: 30 or 60

Step 8: Add Your Content Sources

For 24/7 Video Loops

Add a VLC Video source:

  1. Sources → Add → VLC Video
  2. Add your video files or folder
  3. Tick "Loop Playlist"

For Live Camera/Capture

You'll need to send your local video to the VPS. Step 10 shows two ways: an RTMP relay through nginx, and SRT for unstable connections. On the VPS, OBS picks the feed up with a Media Source.

For Browser Sources

Works the same as local OBS:

  1. Sources → Add → Browser
  2. Enter URL (StreamElements, Streamlabs overlays, etc.)

A Browser source can also load a local HTML file. Our OBS countdown guide uses one to count down to a set time and switch to your live scene at zero.


Step 9: Auto-Start OBS on Boot

Create systemd service for VNC:

sudo nano /etc/systemd/system/vncserver@.service
[Unit]
Description=VNC Server for display %i
After=network.target

[Service]
Type=forking
User=streamer
Group=streamer
WorkingDirectory=/home/streamer

ExecStartPre=/bin/sh -c '/usr/bin/vncserver -kill :%i > /dev/null 2>&1 || :'
ExecStart=/usr/bin/vncserver :%i -geometry 1920x1080 -depth 24
ExecStop=/usr/bin/vncserver -kill :%i

[Install]
WantedBy=multi-user.target

Enable it:

sudo systemctl daemon-reload
sudo systemctl enable vncserver@1
sudo systemctl start vncserver@1

Create OBS auto-start script:

nano /home/streamer/start-obs.sh
#!/bin/bash
export DISPLAY=:1

# Wait for desktop to be ready
sleep 10

# Start OBS and begin streaming
obs --startstreaming --minimize-to-tray &
chmod +x /home/streamer/start-obs.sh

Add to XFCE autostart:

mkdir -p /home/streamer/.config/autostart
nano /home/streamer/.config/autostart/obs.desktop
[Desktop Entry]
Type=Application
Name=OBS Studio
Exec=/home/streamer/start-obs.sh
Hidden=false
NoDisplay=false
X-GNOME-Autostart-enabled=true

If OBS did not shut down cleanly the last time (a crash, a forced kill or a hard reset of the VPS), OBS 33 opens an "OBS Studio Crash Detected" window at the next start and waits until you choose Run in Normal Mode before --startstreaming does anything. After an unplanned restart, connect over VNC once and check.


Step 10: Sending Local Video to Cloud OBS

If you want to stream your gameplay from your home PC but encode on the VPS:

Method 1: RTMP Relay

On VPS, install nginx-rtmp:

sudo apt install nginx libnginx-mod-rtmp -y

Add this block at the end of /etc/nginx/nginx.conf, outside the http { } block, and replace YOUR_HOME_IP with the public IP address you stream from:

rtmp {
    server {
        listen 1935;
        chunk_size 4096;

        application live {
            live on;
            record off;
            allow publish YOUR_HOME_IP;
            allow publish 127.0.0.1;
            deny publish all;
        }
    }
}

The allow publish and deny publish lines stop anyone else from pushing a stream into your relay; 127.0.0.1 is there for the SRT method below.

Restart nginx:

sudo systemctl restart nginx

On your local PC (OBS):

  • Settings → Stream → Custom
  • Server: rtmp://YOUR_VPS_IP/live
  • Stream Key: mystream

On VPS OBS:

  • Add Media Source
  • Uncheck "Local File"
  • Input: rtmp://localhost/live/mystream

Method 2: SRT (Better for unstable internet)

On VPS:

# Install SRT
sudo apt install srt-tools -y

# Start SRT listener
srt-live-transmit 'srt://:9999?mode=listener' file://con | ffmpeg -i - -c copy -f flv rtmp://localhost/live/srt-input &

The srt-live-transmit documentation does not allow its -v option together with file://con as output, because both would write to standard output, so leave it out here.

On local OBS:

  • Settings → Stream → Custom
  • Server: srt://YOUR_VPS_IP:9999
  • Stream Key: (leave empty)

On VPS OBS, add a Media Source with the input rtmp://localhost/live/srt-input, as in Method 1.

Open the Relay Ports for Your IP Only

If you turn on UFW (see Security Best Practices), allow the relay only from the address you stream from. SRT runs over UDP, so its rule names that protocol:

sudo ufw allow from YOUR_HOME_IP to any port 1935
sudo ufw allow proto udp from YOUR_HOME_IP to any port 9999

Alternative: RDP Instead of VNC

Prefer RDP over VNC? Install xrdp:

sudo apt install xrdp -y
sudo systemctl enable xrdp

Configure XFCE for xrdp:

echo "startxfce4" > ~/.xsession

xrdp listens on port 3389 on all interfaces. Keep that port closed in the firewall and tunnel it like VNC, with a different local port so it does not clash with an RDP server on your own computer:

ssh -L 13389:localhost:3389 streamer@YOUR_VPS_IP

Then connect any RDP client to localhost:13389:

  • Windows: Remote Desktop Connection
  • Mac: Microsoft's Windows App
  • Linux: Remmina

Performance Optimization

Reduce CPU Usage

In OBS Settings → Output:

Preset: ultrafast (lowest quality, lowest CPU)
OR
Preset: veryfast (good balance)

Hardware Encoding Only on a GPU Instance

This does not apply to a regular VPS, which has no GPU. Some providers sell separate GPU instances. On one with an NVIDIA card and the NVIDIA driver, OBS 33 lists the encoder as NVIDIA NVENC H.264; on Intel or AMD graphics with VA-API it is FFmpeg VAAPI H.264. Without such hardware, stay on x264.

Optimize X11 Performance

Disable compositor for lower latency:

# In XFCE Settings → Window Manager Tweaks → Compositor
# Uncheck "Enable display compositing"

Or via terminal:

xfconf-query -c xfwm4 -p /general/use_compositing -s false

Monitoring and Alerts

Monitor OBS via Script

nano /home/streamer/monitor-obs.sh
#!/bin/bash
DISCORD_WEBHOOK="https://discord.com/api/webhooks/YOUR_WEBHOOK"

if ! pgrep -x "obs" > /dev/null; then
    curl -H "Content-Type: application/json" \
         -d '{"content": "OBS is not running. Starting it again."}' \
         $DISCORD_WEBHOOK
    
    export DISPLAY=:1
    obs --startstreaming &
    
    sleep 30
    
    if pgrep -x "obs" > /dev/null; then
        curl -H "Content-Type: application/json" \
             -d '{"content": "OBS process restarted. Check the desktop for a crash window."}' \
             $DISCORD_WEBHOOK
    fi
fi

Add to crontab:

crontab -e
*/5 * * * * /home/streamer/monitor-obs.sh

This script only checks that an OBS process exists. It cannot see a stream that is stuck reconnecting, or an OBS that waits at the Crash Detected window after a restart. OBS's own Automatically Reconnect setting covers network drops (see our OBS auto reconnect guide), and our guide to monitoring a 24/7 live stream checks the stream itself, on the VPS and on the platform.

Check Stream Status

# Check if OBS is running
pgrep -x obs && echo "OBS Running" || echo "OBS Not Running"

# Check network output (streaming?)
ss -tulpn | grep obs

Multi-User Access

Let multiple team members control OBS:

Share One Desktop

Everyone connects to the same display :1, each through their own SSH tunnel. Starting a second server with vncserver :2 would give a separate, empty desktop without your OBS on it.

By default, a viewer that does not ask for a shared session disconnects whoever is already connected. Either have everyone turn on the Shared option in their viewer, or restart the server with -AlwaysShared (and add the same option to the ExecStart line from Step 9):

vncserver -kill :1
vncserver :1 -geometry 1920x1080 -depth 24 -AlwaysShared

For someone who should only watch, run vncpasswd again (it asks for the full password first), answer y when it asks for a view-only password, and give them that password. Our stream key guide covers giving helpers access without showing them your key.

Browser Access With noVNC

noVNC shows the desktop in a web browser:

sudo apt install novnc websockify -y

# Serve noVNC on localhost only
websockify --web=/usr/share/novnc 127.0.0.1:6080 localhost:5901 &

Binding to 127.0.0.1 keeps port 6080 off the internet. On your own computer, tunnel it the same way as VNC:

ssh -L 6080:localhost:6080 streamer@YOUR_VPS_IP

Then open http://localhost:6080/vnc.html, click Connect and enter the VNC password. The page is plain HTTP, but it only travels inside the SSH tunnel.


Security Best Practices

Firewall Configuration

# Install UFW
sudo apt install ufw -y

# Allow SSH
sudo ufw allow 22

# Enable firewall
sudo ufw enable

UFW's default policy denies incoming connections, so VNC (5901), noVNC (6080) and xrdp (3389) stay closed and you reach them through SSH. Open 1935 and 9999 only if you use the relay from Step 10, and only for your home IP.

Use SSH Keys

# On your local machine
ssh-keygen -t ed25519

# Copy to server
ssh-copy-id streamer@YOUR_VPS_IP

# Disable password auth on server
sudo nano /etc/ssh/sshd_config
# Set: PasswordAuthentication no
sudo sshd -t
sudo systemctl restart ssh
sudo sshd -T | grep -i passwordauthentication

On Ubuntu and Debian the SSH service is called ssh. sshd -t checks the file before the restart, and sshd -T prints the value sshd really uses. If it still says yes, a file in /etc/ssh/sshd_config.d/ sets it: those files are read first and the first value wins, so change it there too.

VNC Security

  • Keep VNC and noVNC on localhost and use the SSH tunnel
  • Use a VNC password of at least six characters; only the first eight count
  • Give people who only watch the view-only password

Stream Key and Restarts

  • Keep the stream key out of sight on a shared desktop. The Stream Key field in Settings → Stream is masked; don't click Show while someone else is connected or while a display capture sends the screen to your stream.
  • Never put a key in a Browser source URL. The URL field in a Browser source's properties is a plain text field, so anyone who opens that source can read it. Our stream key guide shows where OBS stores the key on Linux and how to reset it.
  • Plan reboots. Ubuntu installs security updates on its own through unattended-upgrades, which is installed by default. It does not reboot unless you set Unattended-Upgrade::Automatic-Reboot "true"; in /etc/apt/apt.conf.d/50unattended-upgrades, and if you do, set Unattended-Upgrade::Automatic-Reboot-Time to an hour when you are not live. A file at /var/run/reboot-required means an update is waiting for a reboot: do it between streams.
  • Plan service restarts. Since Ubuntu 24.04, needrestart restarts services that use updated libraries automatically, apart from a built-in list such as the display manager. The VNC service from Step 9 is not on that list, and if needrestart restarts it, the desktop closes and OBS with it. Exclude it, and restart it yourself when you are offline:
sudo tee /etc/needrestart/conf.d/vncserver.conf <<'EOF'
$nrconf{override_rc}->{qr(^vncserver@\d+\.service)} = 0;
EOF

sudo needrestart -r l then lists what still waits for a restart. A stream can still drop for other reasons, so let our guide to monitoring a 24/7 live stream tell you when it does.


Cost Analysis

VPS Streaming vs Local PC

FactorHome PC 24/7VPS
HardwareYou buy it and replace itPart of the monthly price
ElectricityOn your own bill, 24 hours a dayIncluded
UploadShared with everyone in your houseThe provider's uplink (check the port speed of your plan)
Power cuts and router troubleTake the stream downNot your problem; the hardware and network are the provider's job
Software upkeepYouStill you: a VPS gives you root access, it is not a managed service

What the VPS costs depends on how much CPU OBS needs for your resolution and frame rate, so start from the sizing section at the top of this guide.

VPS vs Managed Streaming

SolutionMonthly CostWhat You Get
RestreamFree plan (2 channels, with Restream branding), Standard $19/monthMultistreaming and a browser studio
StreamYardSee streamyard.com for current plansA live streaming and recording studio in your browser
Cloud OBS (VPS)Whatever your VPS costsFull OBS with your own scenes and Linux plugins
Custom serverWhatever your server costsTotal control

Restream's prices are from restream.io/pricing with monthly billing, and StreamYard's description is from its own site, both checked on 31 October 2026.


Troubleshooting

VNC Connection Refused

Check that your SSH tunnel is open and that you connect to localhost:5901, not to the VPS IP. Then, on the VPS:

# Check if VNC is running
vncserver -list

# Restart VNC
vncserver -kill :1
vncserver :1 -geometry 1920x1080

OBS Won't Start (Display Error)

# Make sure DISPLAY is set
export DISPLAY=:1
obs

OBS Starts but Does Not Stream

If OBS shows an "OBS Studio Crash Detected" window, it waits for a click: choose Run in Normal Mode. Safe Mode disables third-party plugins, scripting and WebSockets. Then check Help → Log Files for the reason the stream did not start.

Audio Issues (No Sound)

# Start PulseAudio
pulseaudio --start

# Or in OBS, set audio to "pulse" device

High Latency/Lag in VNC

  • Lower VNC color depth: -depth 16
  • Use tighter encoding in VNC client
  • Try RDP instead
  • Check network between you and VPS

OBS Streaming But No Video on Platform

  • Verify stream key is correct
  • Check RTMP URL (some platforms change these)
  • Look at OBS → Help → Log Files for errors
  • Ensure the firewall allows outbound traffic: 1935 for RTMP, 443 for RTMPS (UFW allows outgoing connections by default)

FAQ

Is there an official OBS cloud version?

No. The OBS Project's download page offers OBS Studio 33.0.1 (released 29 October 2026) for Windows 10 and 11, macOS 13.0 and newer, and Linux as a Flatpak or through the Ubuntu PPA. It lists no hosted or browser version, so "OBS cloud" in practice means the normal desktop app on a remote machine: a VPS you set up as in this guide, or a streaming machine that comes with OBS installed.

Can I stream games this way?

Yes, but with extra steps. Your game runs locally, you capture it, send it to the VPS over SRT or an RTMP relay (Step 10), and the VPS re-encodes and streams to Twitch/YouTube.

Does VPS OBS support all plugins?

Most plugins that offer a Linux build work. Plugins made only for Windows or macOS do not load on Linux, so check the plugin's download page first.

Is there input lag for live shows?

The VNC connection adds some lag, depending on your connection and the distance to the VPS. For pre-recorded/24/7 content, this doesn't matter. For live shows, you'd send your feed over SRT or an RTMP relay and just control OBS remotely.

Can I use NVENC on VPS?

Only on a GPU instance from a provider that sells one, with an NVIDIA card in your VM and the NVIDIA driver installed. A regular VPS is CPU-only, so you use x264 encoding.

What's the maximum stream quality?

It depends on the vCores and your scenes, so test as described under How Big a VPS You Need. The platforms set their own ceilings: Kick accepts up to 1080p at 60 fps, and YouTube lists bitrates for up to 4K (2160p) at 60 fps.


Conclusion

Running OBS on a VPS takes your home PC and connection out of the stream:

  1. The stream runs on data center power and network, not on your home internet
  2. Your PC can be off while a 24/7 stream keeps going
  3. You reach OBS from anywhere through an SSH tunnel, with VNC, noVNC or RDP
  4. It suits 24/7 streams and automated content

Watch the stream itself as well as the server: OBS's reconnect setting handles network drops, and monitoring tells you about the rest.


Related guides:

Sources

Opened on 4 November 2026:

Opened on 31 October 2026: