OBS Studio 28 was a major release that added HDR and 10-bit encoding support, native Apple Silicon builds, and a move to Qt 6. It is a historical release, not current upgrade advice: check your operating system and essential plugins, then use OBS’s official download page to find the release that fits your setup.
The right update path depends on how you installed OBS and what your channel needs to keep working. If you run a scheduled or continuous broadcast, test the intended version with your scenes, sources and integrations before changing the machine that is on air.
Why OBS Studio 28 mattered
OBS 28.0 arrived on 1 September 2022, according to the OBS Project release notes. It was a substantial change rather than a small maintenance update. The release brought new production options, changes to the application framework, and builds for Apple Silicon Macs. Those changes made it useful to users with modern hardware, but also raised compatibility questions for older computers and add-ons.
Several additions were aimed at specific workflows. On Windows, OBS added application-specific audio capture for a single process, which can help you capture one programme without routing all desktop audio into the stream. The release also integrated obs-websocket 5.0 as a first-party plugin, introduced automatic recording splits by duration or file size, and added an accessibility section in settings. These additions do not all matter to every channel: a devotional video loop may have little need for per-application capture, while a presenter using several desktop tools may find it useful.
Other changes included an updated AMD encoder implementation on Windows, a separate video mix for the virtual camera, native SRT and RIST outputs, in-app YouTube chat messages, and the Yami default theme. On macOS, OBS added ScreenCaptureKit support on macOS 12.5 and later, and direct audio capture on macOS 13 and later. These are version-specific details, not a promise that every feature works on every device or in every later setup.
The release also introduced new obligations before upgrading. A framework migration can affect plugins, and support for older operating systems changed. If your current setup is stable and depends on a plugin you cannot replace, do not update simply because a new feature sounds useful. First identify what the channel relies on, then decide whether the release you intend to install supports that combination.
HDR and 10-bit encoding: what changed
OBS 28 introduced support for HDR and 10-bit encoding. The distinction matters: HDR describes a wider brightness and colour presentation, while 10-bit encoding allows more tonal gradations than 8-bit video. Neither setting alone makes a stream HDR. The encoder, graphics hardware, capture path, OBS configuration and streaming service all have to support the intended workflow.
The 28.0 release notes specified AV1 or HEVC for HDR and 10-bit encoding. For an HDR setup, OBS recommended the P010 colour format and Rec. 2100 PQ colour space in Advanced settings. The notes limited HDR streaming to YouTube’s HLS service with an HEVC encoder. This should not be read as universal HDR support across services, ingest methods or encoders. Check current YouTube guidance and your encoder’s capabilities before planning a live HDR broadcast.
The release notes gave a narrower qualification for 10-bit HEVC: NVIDIA 10-series, AMD 5000-series, or newer GPUs were specified. Intel QuickSync and Apple VT were not supported for that case in the OBS 28.0 notes. Those are historical version notes, not a reliable description of every current driver or OBS release. If a particular encoder is important to your production, verify it against the documentation for the exact OBS build and hardware you are using.
There were also workflow limits. Some filters were unavailable when a source rendered in HDR, including Apply LUT, Chroma Key, Color Key, Image Mask/Blend, Luma Key and Sharpness. The release notes described Mac and Linux HDR support as limited, with no HDR preview there, and noted that some inputs and encoders still needed updates. A camera or capture device may also be part of a specific HDR capture chain; it is not a general requirement for installing OBS or using ordinary SDR video.
For a channel that publishes a fixed video loop, HDR may add little unless the source footage and viewers’ playback path are prepared for it. A clean, correctly exposed SDR stream can be a better choice than an HDR workflow with uncertain capture, filters or service support. Test a short private or unlisted broadcast, check the resulting playback on a suitable display, and retain your working scene collection and settings before changing production.
Native Apple Silicon builds and Qt 6
OBS 28 offered native Apple Silicon builds, allowing the application to run on supported Apple Silicon Macs without relying on x86 emulation. That can make the application a more natural fit for the computer’s processor architecture, but a native application alone does not guarantee that every plugin or external component has a native build.
The OBS 28 release notes cautioned that many third-party plugins might not yet be available in native Apple Silicon form. If an essential plugin was missing a native build, the notes described using the x86 OBS build as an alternative. That alternative may be useful for a particular legacy workflow, but it is not automatically the best choice: confirm that the plugin and the OBS build you intend to use work together, and consider the performance and maintenance trade-offs of running an emulated application.
The same release moved OBS from Qt 5 to Qt 6, a change to the toolkit used for the application interface. The migration was intended to support newer operating systems and architectures, but it also meant that plugins relying on Qt 5 components could need updates. OBS’s release notes warned plainly that some plugins might not be compatible with OBS 28.
Treat architecture and toolkit compatibility as separate checks. A plugin might support OBS 28 on an Intel Mac but not be available for native Apple Silicon; another might have an Apple Silicon build but need a Qt 6-compatible update. Write down the plugin name, its purpose, its supported OBS versions and its supported operating systems before choosing a build. If you use an automation tool to switch scenes or recover a broadcast, include it in the same check. The practical reliability issues behind that sort of workflow are covered in how to set OBS to restart a meditation stream when the encoder stops.
Check your operating-system compatibility
Qt 6 changed the minimum platform picture for OBS 28. The 28.0 notes said it dropped support for Windows 7 and Windows 8, macOS 10.13 and 10.14, Ubuntu 18.04, and 32-bit operating systems. Do not assume an older computer can run OBS 28 because it ran an earlier OBS release, or assume that a version number published in a forum applies to your current package.
Check the exact OBS release’s system requirements against your computer before downloading. Confirm the operating system version, whether it is 32-bit or 64-bit where relevant, and the processor architecture. For macOS, distinguish an Intel Mac from an Apple Silicon Mac; for Linux, confirm the distribution and package route as well as the version. The download page is the appropriate starting point for platform-specific choices, but read any linked requirements before replacing an existing working installation.
For an always-on channel, make the compatibility check on the computer that actually runs the broadcast, not on a newer editing laptop. A home machine may run a short test but behave differently under a long session, with other applications open or after a system sleep setting takes effect. Review power settings, network stability, audio devices and storage alongside software compatibility. OBS version choice cannot correct an unreliable connection or a computer that goes to sleep overnight.
Keep a fallback plan. Save a copy of your scene collection and note the current OBS version and installation source. If you are changing an operating system as well as OBS, avoid making both changes immediately before a scheduled broadcast. Test the intended combination away from the live channel, and know how you would restore the previous working setup if a source, encoder or plugin fails. If YouTube reports that the live feature itself is unavailable, OBS compatibility is not the only issue; see how to check YouTube live streaming feature restrictions in Studio.
Check plugin readiness before upgrading
Make a list of plugins and integrations that the channel genuinely needs. Include items that are easy to forget, such as audio filters, browser sources, stream controllers, caption tools, scene automation, virtual-camera users and scripts. Mark which are essential to going live and which are merely convenient. An optional tool can be disabled for a test; an essential one should be confirmed before you schedule a version change.
OBS published a plugin compatibility page for OBS 28. It includes a platform-specific matrix for Windows, Intel macOS and Apple Silicon macOS, but it is a dated snapshot from 31 August 2022 and says it is not exhaustive. Use it as historical guidance, not a current guarantee. Check each critical plugin developer’s own compatibility notes for the OBS build, operating system and architecture you plan to use.
A compatibility claim needs to match your actual setup. “Works with OBS 28” may not tell you whether the plugin works on your operating system, whether it has a native Apple Silicon version, or whether it depends on Qt 5 components. Look for a release note or support statement that answers those specifics. If the developer has not documented them, ask before upgrading or test on a separate installation where possible.
Change one variable at a time. If you update OBS, replace several plugins and change an encoder preset together, a failure becomes harder to diagnose. Save the current configuration, update or test the application, and verify each critical source and control in a short recording or private test. Check audio levels, transitions, overlays, chat or automation connections, and the stream’s end-to-end output. A preview that looks correct does not prove that the stream is being sent to YouTube as intended.
If a test fails, return to the last known working combination rather than improvising during a scheduled broadcast. Avoid removing plugin files or changing an installation by guesswork; follow the plugin maintainer’s instructions. For uninterrupted video playback, inspect transitions and loop behaviour as well as plugins: how to loop videos in OBS without showing a gap on YouTube Live explains why a local playback seam can become visible to viewers.
Find the current OBS release and choose an update route
Start at the official OBS download page. It provides platform-specific downloads and links to previous releases. Version 28 is not the current release: the research check of the OBS download page on 3 October 2026 found version 32.2.2 listed. That page changes, so check it yourself immediately before downloading rather than treating that version number as permanent.
The page is also the sensible route if you specifically need a previous release for a documented compatibility reason. Older versions can lack fixes and newer features, so do not choose version 28 merely because an article discusses its changes. If a plugin or operating system constrains your choice, confirm the supported combination with OBS and the plugin developer. If there is no such constraint, assess the current official build against your computer and workflow.
The exact update steps depend on your installation source and operating system. A package installed through a distribution’s package manager may be updated there; a download installed directly from OBS may have a different process. The official materials cited here establish the download page and access to previous releases, but not one universal in-app updater sequence for every platform and package source. Follow the instructions for the method you used, and avoid downloading installers from third-party sites.
Before installing, back up the scene collection and any profiles you rely on, note the current version, and keep a copy of settings needed to restore the broadcast. Then install the chosen build, check that the expected plugins load, and make a test recording or private broadcast. Only move the change into your live schedule after confirming the output, audio, capture sources and recovery process. For channels built around recorded material, it is also worth checking the source file and transition plan; this guide to fixing a YouTube 24/7 stream that goes offline during playlist transitions covers a separate cause of interruptions.
OBS is useful when you want desktop control over scenes, sources and encoding, but a computer-based setup also means the host machine and its software remain part of the broadcast path. If keeping a computer on and maintaining the streaming application is the specific burden you want to remove, StreamNeo turns an uploaded video into a YouTube live stream that can continue with your own computer switched off; it is YouTube-only, so it is not a replacement for an OBS workflow that needs live scene switching or other destinations.
Before committing, compare the operating options on the pricing page. When the file and channel are ready, start free — 24-hour trial, no card.
FAQ
Is OBS Studio 28 the current version?
No. OBS 28 is a historical release, and the official download page should be checked for the current version before you install anything. At the time of the research check on 3 October 2026, it listed OBS Studio 32.2.2; that listing can change.
What were the main OBS 28 changes?
The headline changes were HDR and 10-bit encoding support, native Apple Silicon builds and migration to Qt 6. Other additions included application-specific audio capture on Windows, integrated obs-websocket 5.0, automatic recording splits and an accessibility section. The features have specific platform, hardware and workflow limits, so check the release notes for the one you need.
Will my plugins work after upgrading to OBS 28?
Not necessarily. Some plugins needed updates for Qt 6, and plugin availability also depended on the operating system and processor architecture. Check the OBS compatibility page and each essential plugin developer’s current notes, then test the combination before changing your live setup.
How should I update OBS Studio?
Use the official OBS download page or the update route for the package source you originally used, and confirm that the build supports your operating system. Back up your scenes and settings, verify plugin readiness, then test the complete broadcast path before putting the update on a scheduled channel. Don’t assume one set of updater menu steps applies to every platform or installation method.