OBS Studio 30.2.3 — the first minute without a single click

How we tested: a clean Debian 13 in a disposable container; source — package obs-studio 30.2.3+dfsg-3 from the Debian repository. Run as a regular user on a virtual screen, 60 seconds, nothing clicked. 17.10.2026. Every network request and every file written was recorded; the code was not decompiled. The container was deleted afterwards.

Program website: https://obsproject.com

Package SHA-256: 25c24a956f35db063d847dc5797c79ce50eb7931842d6b8201f22b9cfe16d2ee

Summary

What we checkedResult
Built-in telemetry, crash reporting, analytics, ad SDKsnone
Network requests in the first minute2 server names, plus 3 unnamed
Known trackers among the serversnone
Files written in the first minute110
The program ran the whole timeyes — process alive at the end

The program’s screen at the end of the test

What is built in

1183 files (22 MB) were checked.

No code of known telemetry, crash reporting, analytics or ad SDKs was found.

Addresses of known trackers in the program’s files — addresses in code, not requests:

TrackerAddressesMentions
Googledevelopers.google.com, support.google.com202
YouTubestudio.youtube.com, www.youtube.com, vr.youtube.com, a.upload.youtube.com145
Facebookwww.facebook.com2
Twitter/Xstudio.twitter.com1

Where it connected

ServerHowFrom secondTimesKnown tracker
ingest.twitch.tvconnection2.11—
obsproject.comconnection1.91—
[2001:41d0:26c:6f00:913e:6226:cfb3:680e]:443connection without a name (TCP)1.81—
63.184.175.226:443connection without a name (UDP)2.01—
3.73.61.61:443connection without a name (UDP)2.01—

A DNS lookup is not yet a connection: the program looked up the server’s address. But the lookup itself is visible to the ISP and the DNS server.

What it wrote to disk

Folders the program wrote files to during the minute:

FolderFiles
~/.cache/mesa_shader_cache_db102
~/.config/obs-studio8

How to read this card