OBS Recording Settings [2026]: 4 Encoders, 1 Safe Pick
![OBS Recording Settings [2026]: 4 Encoders, 1 Safe Pick](https://ivipid.com/blog/wp-content/uploads/2026/11/obs-recording-settings-nvenc-vs-amf-vs-qsv-vs-x264-2026-gen-1024x585.webp)
Quick answer: which OBS encoder to record with · OBS Studio 33.0: what changed for recording · NVENC vs AMF vs QSV vs x264: specs table · What the sources say: benchmark evidence, checked · NVIDIA NVENC in OBS: the default for GeForce · AMD AMF in OBS: Radeon recording without the CPU hit · Intel Quick Sync (QSV) in OBS: the quiet option · x264 in OBS: the CPU encoder that still earns a slot · Rate control: CQP, CRF, ICQ and VBR in plain terms · Codec and container: H.264, HEVC, AV1, MKV and MP4 · Render settings and what each encoder costs · Use-case recommendations: who should pick what · Streaming and recording at the same time · A repeatable ten-minute encoder test · Five worked setups for real recording jobs · Pros and cons of each encoder · Migration guide: switching encoders or updating to OBS 33 · Verdict: record with your hardware encoder, keep x264 saved · Common questions
The best OBS settings for recording start with one choice: which encoder does the work. OBS Studio 33.0 is the current release line, and it gives you four encoders to pick from: NVIDIA NVENC, AMD AMF, Intel Quick Sync (QSV) and the CPU-based x264. This comparison checks what OBS, NVIDIA, AMD, Intel and VideoLAN publish about each one, as of November 16, 2026.
The short version: if your PC has a recent GPU media engine, record with it and keep x264 as the fallback. The OBS Project knowledge base says it plainly: “For best results, use a GPU with 6th generation NVENC (Turing).” Everything after that sentence is about matching codec, rate control and container to what you do with the file next.
One limit up front. The sources checked for this article contain no dated, head-to-head benchmark of all four encoders on the same clip, so there are no invented frame-time or file-size scores below. What exists is vendor documentation, release notes and 2026 forum reports, and the article says which is which. If you are still deciding whether OBS is the right recorder at all, our OBS, ShadowPlay and Medal comparison covers that first.
Quick answer: which OBS encoder to record with
Match the encoder to the hardware you already own. The table gives a first pick and a fallback for each common setup. Treat it as a starting point, then confirm with a short test recording of your busiest scene.
| Your hardware | First pick in OBS | Fallback | Why |
|---|---|---|---|
| NVIDIA GeForce card, Turing generation or newer | NVENC | x264 | OBS docs name Turing-generation NVENC as the target for best results |
| AMD Radeon RX card | AMD hardware encoder (AMF) | x264 | Dedicated media block keeps the CPU free for the game |
| Intel Core CPU with Quick Sync, or Intel Arc | QSV | x264 | Hardware path on the same PC, but check drivers first |
| Gaming PC with a weak GPU and a strong CPU | x264 | Hardware encoder if frames drop | Software encoding is viable only when CPU headroom is real |
| Laptop with both an Intel iGPU and an NVIDIA GPU | NVENC | QSV | Record on the GPU that is not already saturated by the game |
| Screen tutorial, no game running | Any hardware encoder | x264 | Little load on any option, so pick on codec support and file size |
The rest of the decision is the codec (H.264, HEVC or AV1), the rate-control mode and the container. Those three choices change file size and editor compatibility far more than the encoder brand does. The sections below take each in turn, starting with what changed in OBS itself this autumn.
OBS Studio 33.0: what changed for recording
OBS Studio 33.0 is the newest version listed on obsproject.com as of November 16, 2026. A forum administrator stated on October 26, 2026 that version 33 had shipped, and a release-notes page at OBS-Studio.net dated October 29, 2026 reportedly covers a 33.0.1 point release. Treat the 33.0.1 label as reported by that page, not confirmed on the project’s own download page.
The headline change in 33.0 is the Chromium Embedded Framework update, from version 127 to version 150. That affects browser sources and docks, so it matters most if your recording scene includes chat boxes, alerts or web overlays. It does not change how NVENC, AMF, QSV or x264 encode video. The same release notes say existing third-party plugins keep loading from their legacy locations until OBS Studio 34.0, which gives plugin authors a runway.
The beta announcement listed more items. It described a redesigned plugin-loading architecture, source-snapping improvements, UI cleanup and NVENC support in experimental Arm64 builds. OBS 32.2, released on July 21, 2026 according to the research, was the last release before that. Its notes reportedly moved the NVIDIA SDK to version 13 and raised the minimum NVIDIA driver for NVENC to 570. If your NVENC encoder suddenly vanished after an update, an old driver is the first thing to check.
Known problems in the first weeks of 33.x
OBS forum threads dated October 29 to November 15, 2026 describe blank or failed macOS screen capture on 33.x for some users. Several posters downgraded to 32.2.2 or 32.0.x and reported that capture worked again. One crash report on 33.0.1 advised checking plugin compatibility, and third-party plugin pages dated November 2 to 15 were adding explicit OBS Studio 33 support. These are user reports, not confirmed bugs, but they are a reason to keep the previous installer on disk before a long recording session.
OBS Studio lists macOS 13.0 or newer as its macOS requirement on obsproject.com. This article focuses on Windows and Linux encoders because that is where the knowledge base documents NVENC, AMF and QSV. The Windows-specific recording options, including the Game Bar and Snipping Tool, sit in our Windows 11 screen recording comparison.
NVENC vs AMF vs QSV vs x264: specs table
The table puts the four encoders side by side on twelve points. Values come from the OBS knowledge base, vendor pages and the 2026 reports described in this article. Where the sources do not give a number, the cell says what to check instead of guessing.
| Spec | NVIDIA NVENC | AMD AMF | Intel QSV | x264 |
|---|---|---|---|---|
| Encoder type | Hardware, GPU media engine | Hardware, Radeon GPU | Hardware, Intel CPU or Arc GPU | Software, CPU |
| Vendor interface | NVIDIA Video Codec SDK | Advanced Media Framework SDK | Intel Quick Sync Video | libx264, open source (GPL) |
| OBS platforms (OBS KB) | Windows, Linux | Windows, Linux | Windows, Linux | Included in OBS |
| Codecs in OBS | H.264, HEVC, AV1 depending on GPU generation | H.264, HEVC, AV1 depending on GPU generation | Depends on CPU or Arc generation | H.264 only |
| CPU load while recording | Low | Low | Low | High |
| Hardware requirement | NVIDIA GPU, Turing or newer for best results | Compatible Radeon GPU | Intel CPU with Quick Sync or Arc GPU | None |
| Driver dependence | High, minimum driver can rise with OBS releases | High, Adrenalin 26.9.2 or newer for AMF SDK v1.5.3 | Medium, current Intel graphics driver | None |
| Rate control to prefer | CQP per NVIDIA, VBR as alternative | Constant-quality mode if offered | Constant-quality mode if offered | CRF |
| Release model | Versioned Video Codec SDK | Versioned AMF SDK | Driver releases | Git snapshots, no numbered releases |
| 2026 failure pattern | Errors tied to drivers and OBS version | Errors tied to driver version | Users reported switching to x264 as a workaround in October 2026 | Dropped frames when CPU is saturated |
| Standalone price found | None | None | None | None |
| Best fit | Game capture on GeForce | Game capture on Radeon | Light capture on Intel-only PCs | CPU-rich or GPU-less systems |
Three rows deserve a second look. Driver dependence is the one that breaks recordings in practice, because OBS can raise its minimum driver as vendors update their encoding SDKs. Release model matters if you script or package OBS builds, since x264 has no numbered upstream releases to pin. And the failure-pattern row is the best argument for keeping a second encoder profile saved in OBS, which the migration section covers.
Checked on November 16, 2026 against the OBS knowledge base, NVIDIA’s developer pages, AMD’s AMF repository and release notes, Intel’s support pages and the VideoLAN x264 page. Rows that rest on forum reports say so in the cell. Rows that look like a spec but come from experience, such as CPU load, are labelled as direction rather than measured numbers.
What the sources say: benchmark evidence, checked
Searching for encoder benchmarks in November 2026 turns up plenty of opinion and very little controlled measurement. The table below lists the sources this article relied on, what each one actually supports, and where each one stops. None of them is a lab test of all four encoders on the same footage.
| Source | Date | Type | What it supports | Where it stops |
|---|---|---|---|---|
| OBS Project knowledge base, hardware encoding | Undated | Official docs | Platform support, NVENC generation advice | No quality or size numbers |
| NVIDIA GeForce broadcasting guide | Undated | Vendor guide | CQP as the recommended NVENC recording mode | NVIDIA hardware only |
| NVIDIA Video Codec SDK 13.1 announcement | July 31, 2026 | Vendor blog | AV1 hierarchical reference mode with up to 31 B-frames | SDK feature, OBS exposure is a separate question |
| AMD AMF SDK v1.5.3 post and GitHub page | October 1, 2026 | Vendor release | Driver requirement of Adrenalin 26.9.2 or newer | No encoder quality data |
| Clyper OBS settings guide | October 20, 2026 | Third-party guide | Hardware encoding preferred for recording, example x264 settings | Example values, not universal |
| OBS forum support replies | November 2026 | User forum | AV1 better quality per bit than HEVC, then H.264, with H.264 most compatible | Forum guidance, no dated benchmark |
| w3tutorials NVENC error guide | November 15, 2026 | Third-party guide | Common NVENC error causes, x264 as CPU alternative | Troubleshooting, not performance |
Read across the rows and a pattern appears. Every source that ranks the codecs agrees on the same order for efficiency: AV1 first, HEVC second, H.264 third. Every source that talks about CPU load says hardware encoding is lighter than x264. None of them gives a percentage you can trust for your own machine, because quality per bit depends on the GPU generation, the driver and the content.
How to read the gaps
The honest conclusion is that you have to measure on your own PC. Record the same 60-second stretch of your busiest scene with each encoder you can use, at the same resolution and frame rate, and compare file size and visible artefacts side by side. That test costs ten minutes and settles the question better than any public chart, because it uses your game, your GPU and your driver.
Be wary of any chart that ranks the encoders with a single quality score. A score needs a test clip, a metric, a driver version and an encoder preset, and charts that skip those details cannot be reproduced. The sources here avoid that trap by not publishing scores at all, which is why this article does not either.
NVIDIA NVENC in OBS: the default for GeForce
NVENC is NVIDIA’s hardware encoder, and OBS exposes it for H.264, HEVC and AV1 depending on the card. The OBS Project documentation states, in its own words, “NVIDIA’s NVENC encoder is supported on Windows and Linux.” NVIDIA’s own pages list the GeForce RTX 5090 as the current desktop flagship, but the encoder is not flagship-only. The knowledge base asks for a Turing-generation card or newer.
For rate control, NVIDIA’s GeForce broadcasting guide gives a clear instruction. Its text reads “We recommend CQP, although VBR will also produce good results.” CQP holds quality constant and lets bitrate float, which suits local recording because disk space is cheap compared with a visibly soft shot. VBR targets an average bitrate, which is closer to how a stream behaves.
2026 NVENC developments
NVIDIA’s Video Codec SDK 13.1.15 was reportedly posted on June 10, 2026 and added UHQ iterative encoding, application-allocated CUDA arrays as input surfaces and an AV1 hierarchical B-frame reference mode. The July 31, 2026 technical blog described zero-copy decode-to-encode workflows and AV1 hierarchies of up to 31 B-frames. These are SDK capabilities aimed at developers and transcoders. Whether OBS surfaces a given option is up to the OBS team, so do not expect every SDK feature to appear as a dropdown.
Reports from November 2026 also show NVENC errors in OBS following driver or version mismatches, which is why a third-party troubleshooting guide dated November 15 recommends x264 as the CPU alternative while you fix the driver. The practical rule is simple. After any OBS or driver update, record a 30-second test before a real session.
A corporate footnote for completeness: NVIDIA announced a CEO transition on November 12, 2026. The announcement concerns leadership, and nothing in the sources links it to a change in NVENC or its SDK roadmap. It is context, not a reason to change your encoder.
AMD AMF in OBS: Radeon recording without the CPU hit
AMD’s encoder interface is the Advanced Media Framework. In OBS it shows up as AMD hardware options for H.264 (AVC), HEVC and AV1-related entries, according to November 2026 forum reports. The OBS Project documentation says, in its words, “AMD’s Advanced Media Framework encoder is supported on Windows and Linux.” AMD’s own lineup page lists the Radeon RX 9070 XT as the newest desktop card on sale.
The newest AMF SDK the research found is v1.5.3, posted on October 1, 2026. It added in-pipeline color-matrix conversion and rotation, and it requires AMD Software: Adrenalin Edition 26.9.2 or newer, a driver AMD dated September 29, 2026. For an OBS user the useful takeaway is the driver. If you record on a Radeon card and AMF misbehaves, update Adrenalin before touching any OBS setting.
The Linux caveat
The OBS documentation lists AMF for Linux, but the research could not confirm current Linux support for it, so check your distribution before you build a Linux recording setup around AMF. On Windows, AMF remains the straightforward path. AMF SDK v1.5.3 requires AMD Software: Adrenalin Edition 26.9.2 or newer.
One more point from the same forum reports: AV1 and HEVC are recommended over H.264 on Radeon hardware when the place you send the file supports them. For local recording that you edit yourself, the question is whether your editor decodes them smoothly. The codec section below goes through that trade.
Intel Quick Sync (QSV) in OBS: the quiet option
Quick Sync Video is Intel’s hardware media engine, built into Intel Core processors and available on Intel Arc graphics. OBS documents it as “Intel’s Quick Sync Video encoder is supported on Windows and Linux,” in the OBS Project’s own wording. It is the encoder most people reach for on a PC without a discrete GPU, and on a laptop where the NVIDIA card is already busy running the game.
Intel’s support pages for Arc cards, including the Arc A770 page, reportedly carry troubleshooting entries for OBS frame drops and QSV problems, which confirms that people use QSV in OBS and run into trouble with it. Keeping your Intel graphics driver current is the first thing to try when QSV misbehaves.
The sources do not show a new QSV encoder generation in 2026, and they do not justify calling QSV better or worse than NVENC or AMF. One concrete data point comes from OBS forum posts in October 2026, where users reported fixing QSV failures by switching to x264. That is a workaround, not a verdict on the encoder. If QSV fails, update the Intel graphics driver first, then try x264 for the session.
x264 in OBS: the CPU encoder that still earns a slot
x264 is the software H.264 encoder built into OBS, and VideoLAN’s x264 page is its official home. It runs on the CPU, so it needs no supported GPU. The cost is load: OBS guidance generally recommends the hardware encoders over x264 for gameplay because x264 consumes CPU resources the game also wants.
There is no numbered x264 release to cite. The project is distributed from a Git repository, and the latest verifiable build the research found is 0.165.3223 in a FreeBSD port. For you, that means x264 is stable and mature rather than fast-moving.
When x264 is the right pick
Choose x264 when the PC has no usable hardware encoder, when a hardware encoder keeps failing, or when you are recording something light such as a slide deck or a tutorial with a mostly static screen. A third-party guide dated October 20, 2026 lists example x264 settings of the veryfast preset with CRF values from 16 to 23. Those are example values from one guide, not a universal 2026 recommendation, so start in that range and adjust by eye.
OBS also has a fallback behaviour worth knowing. A pull request reported in the research updates how OBS handles a profile whose hardware encoder is missing, falling back to x264 and saving that choice in the profile. If a recording suddenly comes out as x264 after a hardware change, check which encoder the profile now holds.
Rate control: CQP, CRF, ICQ and VBR in plain terms
Rate control decides how the encoder spends bits. For local recording the two families that matter are constant quality and constant bitrate. Constant-quality modes (CQP on NVIDIA and AMD, ICQ on Intel, CRF on x264) hold the look steady and let file size float. Constant-bitrate modes hold size steady and let the look suffer in busy scenes.
| Mode | Used by | What stays fixed | What moves | Good for |
|---|---|---|---|---|
| CQP | NVENC, AMF | Quality level | File size | Local recordings you will edit |
| ICQ | QSV | Quality level | File size | Local recordings on Intel |
| CRF | x264 | Quality level | File size and CPU time | Software recordings with spare CPU |
| VBR | Hardware encoders | Average bitrate | Quality in busy scenes | Recordings that must fit a size budget |
| CBR | All encoders | Bitrate | Quality in busy scenes | Streaming, not local capture |
The names differ, but the idea is the same. A lower quality number gives better quality and a bigger file. A higher number gives a smaller file with more visible compression. Because each encoder scales differently, a number that looks right on NVENC will not look the same on x264. Do not copy values between encoders. Test each one on your own footage.
Which mode to start with follows from NVIDIA’s wording quoted earlier. CQP first, VBR if you need predictable file sizes. For streams, constant bitrate is the convention, and it is the setting to avoid for a file you plan to color-grade or re-encode later, since a heavily compressed source loses more with every pass.
Codec and container: H.264, HEVC, AV1, MKV and MP4
The encoder produces a codec, and the codec sits inside a container. Forum guidance from November 2026 repeats an ordering of efficiency: AV1 gives better quality per bit than HEVC, which beats H.264. It also repeats the compatibility ordering in reverse. H.264 plays everywhere, HEVC mostly does, and AV1 depends on the editor and the device.
| Codec | Efficiency per bit | Editor and player support | Pick it when |
|---|---|---|---|
| H.264 | Lowest of the three | Broadest | You edit on older machines or hand files to clients |
| HEVC | Middle | Wide, with some licensing friction | You want smaller files and your editor handles it |
| AV1 | Highest of the three | Growing, depends on GPU and editor | You have a modern GPU and a current editor |
For the container, record to MKV and remux to MP4 when needed. MKV survives a crash or power cut better than MP4, which can lose a whole file if OBS stops unexpectedly. OBS has a remux option that rewrites the container without re-encoding, so it takes seconds and does not touch quality. If your editor opens MKV directly, you can skip the step.
The 2026 sources contain no dated size comparison for these codecs inside OBS, so there is no percentage to quote here. The ordering is consistent across the sources, which is enough to choose a direction. If file size is your main problem, move from H.264 to HEVC or AV1 before touching bitrate or quality numbers.
Render settings and what each encoder costs
These are starting values for a gameplay or tutorial recording that you will edit afterwards. They are recommendations from this article’s analysis, not figures taken from a vendor page.
| Render setting | Gameplay | Screen tutorial | Camera plus screen |
|---|---|---|---|
| Resolution | 1920 x 1080 | 1920 x 1080 | 1920 x 1080 |
| Frame rate | 60 fps | 30 fps | 30 or 60 fps |
| Length | Limited by disk, not by OBS | Limited by disk | Limited by disk |
| Recording format | MKV, remux to MP4 | MKV, remux to MP4 | MKV, remux to MP4 |
| Encoder | NVENC, AMF or QSV | Any hardware encoder or x264 | NVENC or AMF |
| Rate control | CQP or constant quality | CQP or CRF | CQP |
Cost is the easiest row to answer. OBS Studio itself is free and open-source software, according to the project’s own materials. None of the four encoders carries a standalone price in the sources checked. NVENC, AMF and QSV come with the hardware, and x264 comes with OBS. The only real spend is the GPU or CPU you already own, plus disk space for constant-quality files.
| Item | What you pay for | Standalone price found | Real cost driver |
|---|---|---|---|
| OBS Studio | Nothing in the app itself | None | Your own hardware |
| NVENC | Included with the NVIDIA GPU | None | GPU generation |
| AMF | Included with the Radeon GPU | None | GPU generation and driver |
| QSV | Included with Intel Core or Arc | None | CPU or Arc generation |
| x264 | Included in OBS | None | CPU headroom |
| Disk space | Local storage for recordings | Not checked | Quality setting and codec |
From the Vipid archive: if your recordings feed a channel intro, the Vipid intro themes list resolution, length and frame rate, so you can match your OBS canvas to the clip before you cut it in.
Use-case recommendations: who should pick what
Six common jobs, each with a pick. These follow from the vendor guidance and 2026 reports above, so each recommendation carries the caveat that your own test clip decides.
- Streamer saving a local copy of each broadcast. Use a hardware encoder for the recording and keep the CPU free for the game and the stream. Set the local file to a constant-quality mode while the stream stays on constant bitrate.
- Gameplay YouTuber who edits heavily. Use NVENC or AMF at 1080p60 with CQP, record to MKV, and pick H.264 or HEVC based on how smoothly your editor scrubs the clips.
- Course or tutorial maker. Record at 30 fps in any hardware encoder. A mostly static screen compresses well, so file size stays low and you can choose a higher quality setting without worry.
- Presenter on a locked-down work laptop. If you cannot update drivers, x264 avoids driver dependence entirely. Keep the preset fast and watch CPU use during a short test.
- Clip creator with limited storage. Move to HEVC or AV1 if your GPU encodes them and your editor opens them. That is a bigger lever on file size than any bitrate number.
- Anyone recording long, unattended sessions. Use MKV, a hardware encoder and a constant-quality mode, and make sure the disk has room for the worst case of the quality setting you chose.
These picks overlap, which is fine. The main split is between people who can update drivers and run a hardware encoder, and people who cannot. For the second group, x264 is a legitimate default, not a downgrade.
Streaming and recording at the same time
Many creators stream and record in the same session. OBS lets the recording reuse the stream’s encoder, or use a separate encoder with its own settings in Advanced output mode. Reusing the stream encoder is the lightest option, but then the local file inherits the stream’s constant bitrate and its compromises. A separate recording encoder costs more GPU or CPU, and gives you a higher-quality file.
If you choose a separate encoder, put the stream on one engine and the recording on another when you can. A common split is NVENC for the stream and x264 or QSV for the file, which spreads load across different silicon. The sources do not measure this split, so treat it as a design idea to test, not a proven gain. Watch the OBS stats dock for dropped frames and encoding lag during a trial stream.
Overlays add to the picture. Browser sources, chat boxes and alerts all load through the Chromium framework that 33.0 updated from version 127 to 150, and they take CPU and GPU time of their own. Overlay design is a separate job from encoder choice. When frames drop, remove overlays one at a time before blaming the encoder.
A repeatable ten-minute encoder test
Since no public benchmark in the sources covers your exact hardware, build your own. Pick the scene that stresses your PC most, such as a fast game with a busy overlay. Record 60 seconds with each candidate encoder, changing only the encoder and its quality value between runs. Copy the log below into a text file and fill one block per run.
Encoder:
Codec (H.264 / HEVC / AV1):
Rate control and value:
Container (MKV / MP4):
Scene tested (60 seconds, busiest scene):
Dropped frames in OBS stats dock:
CPU use during clip:
GPU use during clip:
File size:
Visible artefacts (text edges, fast pans, dark scenes):
Editor opens file cleanly (yes / no):
Compare file sizes first. If two encoders give the same visible quality at different sizes, take the smaller. Then compare dropped frames and CPU use. An encoder that wins on size but drops frames in your busiest scene has lost, because a dropped frame in a recording cannot be fixed later. Keep the log, since a driver or OBS update can change results and the log tells you what to retest.
Check the pause points too. Open the finished file in your editor, scrub through it and look for stutter at the timeline. A file that records cleanly but scrubs badly suggests the codec is the problem, not the encoder, and moving from HEVC or AV1 back to H.264 can cure it.
Five worked setups for real recording jobs
These are scenario builds, assembled from the vendor guidance and 2026 reports above. They are not benchmarks, and none of them was run for this article. Use them as a pattern for your own PC.
Setup 1: GeForce gamer recording 1080p60 gameplay
Choose NVENC, CQP rate control, 1920 x 1080 at 60 fps and MKV. This follows NVIDIA’s CQP recommendation and the OBS knowledge base advice on Turing or newer. Start with H.264 if you edit on an older machine, then try HEVC or AV1 once you confirm your editor reads them. Record a 30-second test after every driver update.
Setup 2: Radeon player on a recent driver
Choose the AMD hardware H.264 option first, in constant-quality mode if OBS offers it, with 1080p60 and MKV. Keep Adrenalin at 26.9.2 or newer so the AMF SDK v1.5.3 requirement is met. Switch to HEVC or AV1 if your editor handles them, since the forum guidance favors those codecs on Radeon hardware.
Setup 3: Intel-only laptop recording a tutorial
Choose QSV at 1080p30 and MKV. A mostly static screen is light work for any encoder, so quality is easy to hold. If QSV drops frames or errors out, update the Intel graphics driver, then fall back to x264 for the session, matching what forum users reported in October 2026.
Setup 4: Old GPU, strong CPU, offline recording
Choose x264 with a fast preset and CRF in the range one October 2026 guide lists as an example. Leave headroom for the game by checking CPU use during a test. If frames drop, move to a faster preset before touching resolution. This is the one case where software encoding makes sense as a first choice.
Setup 5: Mac user on OBS 33.x
OBS lists macOS 13.0 or newer as the minimum. Forum reports from late October and November 2026 describe blank macOS screen capture on 33.x for some users, with downgrades to 32.2.2 or 32.0.x as the workaround. If capture fails on your Mac, keep the older installer handy before you try anything else. The encoder question on macOS is outside what this article’s sources cover.
Pros and cons of each encoder
The lists below compress the sections above. They describe what the documentation and 2026 reports support, not measured performance.
- NVENC pros: low CPU load, CQP recommended by NVIDIA, H.264, HEVC and AV1 on current cards, active SDK work in 2026.
- NVENC cons: depends on a recent driver, and OBS reportedly raised its minimum driver in the 32.2 notes.
- AMF pros: low CPU load on Radeon cards, AV1 and HEVC options, a maintained SDK with v1.5.3 posted on October 1, 2026.
- AMF cons: needs Adrenalin 26.9.2 or newer for the current SDK, and Linux support is in flux.
- QSV pros: works on PCs with no discrete GPU, leaves the GPU free on dual-graphics laptops, supported in OBS on Windows and Linux.
- QSV cons: OBS forum users reported switching to x264 to get past QSV failures in October 2026, and Intel’s support pages reportedly carry OBS frame-drop troubleshooting.
- x264 pros: runs anywhere, no driver dependence, long-established quality baseline.
- x264 cons: uses CPU that the game wants, H.264 only, no numbered upstream releases.
Migration guide: switching encoders or updating to OBS 33
Changing the recording encoder in OBS is a settings change, not a reinstall. The steps below keep a safe way back at every point.
- Back up your profile and scene collection before you change anything. OBS stores them separately, so copy both.
- Keep the previous OBS installer on disk. Forum reports show some users returning to 32.2.2 after a 33.x capture problem.
- Update your GPU driver first. For AMD that means Adrenalin 26.9.2 or newer if you want the current AMF SDK, and for NVIDIA it means a driver that meets the OBS release’s stated minimum.
- Open Settings, switch Output Mode to Advanced, and go to the Recording tab. Pick the new encoder from the dropdown.
- Set the rate-control mode to a constant-quality option (CQP on NVIDIA or AMD, ICQ on Intel, CRF on x264) and enter a starting value.
- Choose MKV as the recording format and enable remuxing if you need MP4 later.
- Record 60 seconds of your busiest scene. Check CPU and GPU use, look for dropped frames in the OBS stats dock, and watch the file for artefacts.
- Adjust the quality number, record again, and compare file sizes. Save the result as a new profile so the old one stays intact.
If you also use OBS for stream overlays, plugins and browser sources are the part most likely to break during an upgrade. The 33.0 notes say third-party plugins keep loading from their old locations until OBS Studio 34.0, so you have a version cycle to update them. Check each plugin’s page for OBS 33 support before the next big session. More OBS workflows sit in the OBS and screen recording section.
Verdict: record with your hardware encoder, keep x264 saved
For most people the best OBS settings for recording in 2026 are the hardware encoder that matches your GPU, a constant-quality rate-control mode, 1080p at 60 fps for games and MKV as the container. NVENC, AMF and QSV all keep the CPU free, and OBS guidance prefers them to x264 for that reason. NVIDIA’s own wording puts CQP first.
Which hardware encoder you use is mostly decided by the card in your PC, not by a quality chart, because the sources checked do not contain one. What they do contain is a consistent ordering: AV1 over HEVC over H.264 for efficiency, and the reverse for compatibility. Pick the most efficient codec your editor will open without complaint.
Keep a second profile saved with x264. In 2026 forum reports, switching to it was the common workaround when QSV failed, and OBS itself can fall back to it. That second profile costs nothing, and it is the difference between a failed session and a slightly warmer CPU. After every OBS or driver update, record a short test before you go live or start a long take.
Common questions
What are the best OBS settings for recording in 2026?
Use your GPU’s hardware encoder (NVENC, AMF or QSV), a constant-quality rate-control mode, 1920 x 1080 at 60 fps for gameplay and MKV as the recording format. Remux to MP4 if your editor needs it. Fine-tune the quality number by recording a test clip of your busiest scene.
Is NVENC better than x264 for recording?
For gameplay, usually yes in practice, because NVENC leaves the CPU free for the game. The sources do not give a dated quality benchmark between them. x264 is still a valid option when you have spare CPU headroom or no hardware encoder.
Should I use CQP or CBR for local recordings?
Use CQP or another constant-quality mode. NVIDIA’s guide recommends CQP for NVENC and lists VBR as an alternative. CBR is the streaming convention and wastes quality in busy scenes when you are recording to disk.
Should I record in MKV or MP4?
Record in MKV, because it survives a crash better, and remux to MP4 afterwards if your editor or the platform needs it. Remuxing rewrites the container without re-encoding, so quality does not change.
Is AV1 or HEVC better for OBS recordings?
Forum guidance from November 2026 says AV1 gives better quality per bit than HEVC, and HEVC beats H.264. H.264 remains the most compatible. Choose the most efficient codec that your GPU can encode and your editor can open.
Why did my encoder disappear after updating OBS?
The usual cause is an outdated graphics driver. OBS can raise its minimum driver as vendors update their encoding SDKs, and AMD’s current AMF SDK needs Adrenalin 26.9.2 or newer. Update the driver, restart OBS, and check the encoder dropdown again.
Does OBS 33.0 change recording quality?
Your recording quality still depends on the encoder, codec, rate control and driver you choose.
More from the Vipid blog
- OBS vs Streamlabs [2026]: $0 vs $27/mo for Ultra
- Twitch Chat Overlay Obs [2026]
- AV1 vs HEVC [2026]: 30.6% Fewer Bits, 1 Vendor Test
- Your Video a channel-style intro theme
- Intro themes stream and channel intros
- Sample videos finished Vipid intros
- Vipid intro maker make a custom intro in the browser
Jonah Reyes
Jonah Reyes is the Editing & Export Editor at Vipid. He covers editing software, export settings and codecs, and the video specs of YouTube, Shorts, TikTok and Reels, plus OBS and screen recording. He builds Vipid’s spec tables from the platforms’ own documentation and re-checks them every 60 to 90 days, so the numbers in a guide match what the upload dialog actually accepts.
![Screen Recorder for Mac [2026]: $0 vs $108/yr](https://ivipid.com/blog/wp-content/uploads/2026/11/screen-recorder-for-mac-2026-gen-800x450.webp)

![Starting Soon Screen [2026]: 3 Formats, $0 to $27/mo](https://ivipid.com/blog/wp-content/uploads/2026/11/starting-soon-screen-loop-vs-browser-vs-image-2026-gen-800x450.webp)