OBS Studio 28 was a substantial release from 2022, but it is not the current OBS version. Before considering its HDR, Apple Silicon or interface changes, check whether your operating system and essential plugins could run this historical release.
The version introduced 10-bit and HDR encoding under specific conditions, native Apple Silicon builds and a move from Qt 5 to Qt 6. Those changes could improve a particular workflow, but they also created compatibility questions. Treat OBS 28 as a version to assess against your setup, not as an automatic upgrade target.
OBS Studio 28 in context
OBS 28.0 was released on 1 September 2022. Later OBS releases have followed, so the requirements discussed here apply to version 28 alone; they are not a guide to the requirements of current OBS. The official OBS 28 release notes are the best reference for its platform-specific details and caveats.
The release was notable because several changes affected the foundations of a setup, rather than simply adding buttons. OBS moved its interface to Qt 6, offered a native build for Apple Silicon Macs, and added HDR and 10-bit encoding support for specified formats. Any of these could matter to a creator, but none makes an upgrade worthwhile if a required plugin, capture device or operating system is incompatible.
There were also practical additions: single-application audio capture on Windows, automatic recording splits, native SRT and RIST outputs, accessibility settings, and a first-party integration of obs-websocket 5.0. Some changes were limited to a particular OS or runtime. A feature appearing in the release notes does not establish that it works on every machine or in every streaming workflow.
For a 24/7 channel, start with continuity. A visual improvement or new output format is rarely worth losing a scene collection, a working automation client or a dependable capture path overnight. Record what you rely on, check the exact version-28 caveats below, then test in a copy of your production setup.
The notable changes in version 28
HDR and 10-bit encoding drew attention, but OBS 28 also addressed common production tasks. Windows users gained application audio capture for a single process, which could help keep a browser or player separate from other system audio. Mac users gained ScreenCaptureKit support on macOS 12.5 and later; direct application audio capture without a third-party solution was available on macOS 13 and later. These are distinct platform conditions, not one universal desktop-audio feature.
OBS 28 added recording splits by file size or duration, automatically or with a hotkey. Long recordings can become easier to manage when divided into smaller files, though you still need to check where the files are saved and how your editing or archive workflow handles multiple parts. The release also provided separate video mix selection for the virtual camera, plus native SRT and RIST outputs for workflows that use those protocols.
For Windows, the release notes describe an updated AMD encoder implementation and NVIDIA Background Removal. The latter required the NVIDIA Video Effects SDK Runtime; Room Echo Removal in NVIDIA Noise Suppression required the NVIDIA Audio Effects SDK runtime. Those runtime requirements matter as much as the headline feature. Do not assume a named effect will be available merely because the GPU brand matches.
OBS 28 incorporated obs-websocket 5.0 as a first-party plugin. The OBS Project had announced that version 5 would be included with OBS downloads beginning at 28.0.0 in its websocket announcement. This does not mean every existing control panel, bot or automation client works without adjustment: confirm that the client supports the version and configuration you intend to use.
Smaller workflow changes included the Yami theme as the new default, a UI reset option, accessibility settings to change certain interface colours, a source rotation handle and spacing helpers in the preview. Reconnect behaviour was improved, with the default reconnect delay reduced to two seconds. A shorter delay can make a disconnection less noticeable, but it is not a guarantee of uninterrupted streaming; the network, encoder and YouTube ingest remain part of the chain.
If your aim is an uninterrupted prerecorded loop rather than scene-based production, compare the production method with the requirements in how to stream a prerecorded video on YouTube with StreamYard. That is a different workflow question from whether OBS 28’s new controls suit an existing desktop broadcast.
HDR and 10-bit encoding: conditional support
OBS 28 introduced 10-bit and HDR encoding, but the release notes limited those encodes to AV1 and HEVC. For HDR, OBS recommended the P010 colour format and Rec. 2100 PQ colour space. These settings describe a path to configure, not a promise that an HDR image will travel intact through every encoder, operating system, filter, capture device and destination.
There is a narrower distinction for streaming. In this release, HDR streaming was supported only through YouTube’s HLS service using HEVC. If your intended destination or delivery path does not meet that condition, do not plan on an OBS 28 HDR stream simply because the preview looks correct. Read YouTube’s current live encoder settings guidance before settling on an ingest configuration; service requirements can change after a software release.
The hardware path also matters. For 10-bit HEVC, the OBS 28 notes named NVIDIA 10-series, AMD 5000 series, or newer. They said Intel QuickSync and Apple VT were not yet supported for that path. A machine may support HDR display or capture in another application and still not support the particular OBS encoder route you need.
On macOS and Linux, OBS 28 described HDR support as limited: HDR preview did not work, and several inputs and encoders still needed updates. HDR game sources could be tonemapped to SDR when composing in SDR, which is useful when the output is intentionally standard dynamic range. That is not the same as producing an HDR stream.
Filters are another common source of surprises. The release notes identify Apply LUT, Chroma Key, Color Key, Image Mask/Blend, Luma Key and Sharpness as filters that did not function when a source rendered with HDR. If a key, mask or sharpening step is central to your scene, test that exact source-and-filter combination before moving a live channel to an HDR workflow.
Capture-device HDR depends on the device supporting HDR. OBS cited products such as the EVGA XR1 Pro, Elgato 4K60 Pro Mk.2 and AverMedia Live Gamer 4K as examples, not as a required shopping list or endorsement. Check the capture device’s own documentation and test the actual signal format from the source. For most channels, a stable SDR path may be the more practical choice if any part of the chain is uncertain.
Native Apple Silicon support
OBS 28 offered native Apple Silicon builds, so compatible Macs could run OBS without relying on x86 emulation. That could make the native architecture an attractive starting point for a Mac-based setup, but it does not settle plugin compatibility. A plugin may be unavailable for Apple Silicon even when OBS itself launches and operates normally.
The release notes explicitly retained the x86 build as an option for access to a broader selection of plugins that had not yet been made native. This is a trade-off, not a universal recommendation: native OBS may suit a setup whose plugins are all compatible, while the x86 build may be more practical when a required plugin is not. Confirm the plugin’s supported OBS version and architecture with its maintainer rather than inferring compatibility from the Mac model.
Encoder choices also differed. OBS 28 added CBR, CRF and Simple Mode support for the Apple VT encoder on Apple Silicon, with CBR requiring macOS 13 or later. Those details describe the release’s available options; they do not guarantee a particular quality or bitrate outcome on every source. Test a representative recording and stream configuration before changing a production profile.
If you rely on an automation tool, audio routing extension, transition or capture plugin, include it in the architecture check. A scene collection can open while a missing plugin leaves a source blank or a control unavailable. Keep the previous working setup and installer accessible until the native or x86 choice has passed a real test.
Qt 6 migration and plugin compatibility
OBS 28 replaced Qt 5 with Qt 6 for its interface. For a viewer, this might mainly appear as a changed look and behaviour. For a channel operator, the important question is whether third-party plugins were built or updated for the new toolkit. Some plugins may not have been compatible with OBS 28 at release, and a Qt 5 dependency could require the plugin author to make changes.
Make a list of plugins you actually need: not only visible effects, but also source types, audio filters, browser integrations, transitions and automation components. Check the OBS plugin compatibility page and the plugin’s own release notes or support channel. The compatibility page is a starting point, not proof that your particular version, operating system and CPU architecture have all been tested together.
You can also check whether a scene collection opens and whether each source behaves as expected. A plugin that appears in a menu may still fail when loaded, and an upgrade can reveal problems only when a particular scene is activated. Export or back up scene collections and profiles, note plugin versions, then test the scenes you use most often, including recovery and reconnect scenarios.
For a long-running channel, avoid updating OBS and all plugins at once. If a problem appears after several changes, it is harder to identify which change caused it. Keep a written record of the OBS version, plugin versions and architecture used for the test, so you can make a controlled decision rather than troubleshooting from memory.
Check version-28 operating-system support
The Qt 6 transition also ended version-28 support for some older platforms. OBS 28 no longer supported Windows 7 and 8, macOS 10.13 and 10.14, Ubuntu 18.04, or any 32-bit operating system. These are historical version-28 requirements, not the current OBS compatibility list. If your machine falls into one of those categories, OBS 28 is not a supported upgrade destination for it.
Check the operating system on the computer that actually runs the broadcast, not just the one you use to edit scenes. A spare desktop, older laptop or dedicated control machine can differ from your everyday computer. Also check the CPU architecture, GPU and capture hardware against the feature you want; passing the operating-system check alone does not establish encoder or plugin support.
An unsupported operating system should not be treated as a small inconvenience that can be solved by pressing through an installer warning. For a production machine, an upgrade can affect drivers, plugins and other software as well as OBS. If the machine cannot move to a supported OS, assess a different supported computer or retain a known-working setup while planning a migration. Do not confuse a successful installation with a supported or tested configuration.
For people building a dedicated always-on machine, hardware and operating-system choices belong together. The considerations in budget mini PC options for a 24/7 YouTube live product showcase in India can help frame that broader decision; it is not a guarantee that any listed machine runs a particular OBS version or plugin combination.
Plan and test an upgrade or rollback
Treat a version change as a small production migration. First write down the reason for upgrading: a specific feature, a supported plugin fix, or a needed output. If you cannot name what the upgrade changes for your channel, staying on a stable, supported version may be preferable to changing a working broadcast just because a release has notable features.
Before installing, make recoverable copies of your profiles, scene collections and any scripts or configuration files you depend on. Record the current OBS version and plugin versions, save the installer or installation method for the working version if available, and note any custom encoder and audio settings. Back up media assets separately; a scene collection does not necessarily contain the underlying video, image or audio files.
Then test in a controlled session. Open the scenes that matter, check every source, confirm audio meters and monitoring, and make a local recording using the intended encoder and colour settings. For a channel using a capture card, test its actual input. For HDR, verify the whole chain and destination conditions described above, rather than relying on a desktop preview. For automation, test the real client against the bundled websocket setup.
A short private or unlisted test can help you inspect the stream path without presenting an untested change as the normal channel broadcast. Confirm the correct YouTube account, stream key and visibility before starting any test, and follow YouTube’s current instructions. If the stream uses background music or other third-party material, review the separate rights and platform questions in Can you livestream copyrighted music on YouTube 24/7?; an OBS upgrade does not settle them.
Decide in advance what would trigger rollback: a missing source, audio routing failure, a plugin error, unexpected dropped frames or an encoder setting you cannot reproduce. Keep the earlier configuration intact until the new one has run through a representative period that includes the tasks your channel needs. Do not assume that installing an older application automatically restores all settings or plugins to their former state; use the backups and follow the applicable OBS and plugin guidance.
For a channel whose main job is to repeat a fixed video file around the clock, there is also a workflow decision beyond version selection. A desktop OBS setup gives you scene-based control, but requires a working local computer and a tested local environment. StreamNeo addresses the specific burden of keeping that computer on for a file-based YouTube broadcast: you upload the video, provide your YouTube stream key, and the broadcast can run with your computer switched off, with monitoring and automatic restart if it drops. It is YouTube-only, and does not replace OBS for a scene-driven production that needs live switching or local sources.
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 latest version?
No. OBS 28.0 was released in September 2022 and later OBS releases have followed. Consult the OBS Project’s current download and release information rather than treating version 28’s requirements as current.
Can OBS 28 stream HDR to YouTube?
The release notes limited HDR streaming to YouTube’s HLS service using HEVC. HDR and 10-bit encoding were also constrained by encoder, hardware, operating system and filter support, so check the exact workflow and YouTube’s current guidance before relying on it.
Will my OBS plugins work after upgrading to version 28?
Not necessarily. OBS 28’s Qt 6 migration could affect plugins that depended on Qt 5, and Apple Silicon users also needed to consider whether each plugin supported the native architecture. Check the plugin’s own compatibility information and test a copy of your production scenes.
Should I install the Apple Silicon build or the x86 build?
Choose based on the plugins and tools your setup requires. The native build avoids x86 emulation, while OBS 28’s x86 build could offer access to a wider set of plugins not yet available natively; test the full workflow before changing a live channel.