OBS Can't Find NVENC/AMF Encoder — Missing Hardware Encoder Diagnosis Guide

Key Summary
OBS lists only the encoders it can see, so a missing NVENC or AMF option means the encoder layer cannot be reached, not that the card has failed. Note which encoder is missing, test x264 as an isolation control, confirm which GPU OBS is running on, and work through driver, occupancy, and capability layers in order.
The Opposite Shape: Missing, Not Overloaded
OBS is opened, the output settings are checked, and the encoder list does not contain NVENC or AMF. The option is not greyed out with a warning and it is not failing halfway through a stream. It is simply not there. Sometimes OBS reports an "Encoder Missing" error at start-up instead. The first reaction is usually to conclude that the graphics card has failed. That conclusion is too fast, and it skips the distinction this guide is built on.
That distinction is between an encoder that is missing and an encoder that is overloaded. They are opposite shapes, and their diagnostic trees are completely different. An overloaded encoder exists: it appears in the list, it can be selected, and OBS complains during output that the encoder cannot keep up with the load. A missing encoder cannot be selected at all, because OBS cannot see it. Overload is a load signal, not a damage diagnosis — the encoder is present and working, but the work asked of it is too much. A missing encoder is an availability problem: something between OBS and the hardware encoder is broken, blocked, or absent, and the encoder layer cannot be reached. The two symptoms point in opposite directions, so the fix for one must not be applied to the other. Raising or lowering encoder settings cannot bring back an encoder that OBS cannot see, and reinstalling a driver will not cure an encoder that is present but overloaded.
This guide covers desktop computers where OBS cannot find a hardware encoder — NVENC, AMF, or Quick Sync — and the option is missing from the encoder list or reported as missing at start-up, while the computer otherwise starts and displays normally. It does not cover the case where the encoder is present and OBS reports overload during recording or streaming, which is a different shape with a different diagnosis. It does not cover a black capture picture where the encoder list is complete, which belongs with the capture layer, not the encoder layer. It does not cover a recording that starts and then stutters, which is a performance question, not an availability question. The core claim is simple: a missing encoder is evidence about one layer — the encoder layer — and the cause must be found by recording which encoder is missing, testing the software encoder as a control, and working through driver, occupancy, GPU selection, capability, and OBS itself in order.
Three Separate Layers: Display, Encoding, Capture
Three things can each be true or false on their own, and confusing them is the most common error in this subject. They are the display layer, the encoding layer, and the capture layer, and each one is certified separately.
The display layer is what Device Manager checks. If Device Manager shows the graphics card, that proves the display layer recognises the card: the card is present, its driver has loaded far enough for Windows to list it, and a picture can reach the screen. That is all it proves.
The encoding layer is what OBS checks when it builds its encoder list. NVENC on an NVIDIA card, AMF on an AMD card, and Quick Sync on an Intel processor are fixed-function hardware encoder blocks. They are separate units from the 3D rendering cores: encoding is a different job from drawing a picture, and it does not use the CUDA cores or the processor in the way rendering does. OBS must be able to reach that encoder block through the driver. If it cannot, the option disappears from the list. Device Manager showing the card does not prove that OBS can see the encoder, because seeing the card and seeing the encoder are two different checks.
The capture layer is what OBS checks when it takes a picture from a game or a window. A black capture picture with a complete encoder list is a capture-layer problem, and it is not this guide. A missing encoder with a normal capture preview is an encoder-layer problem, and it is not a capture problem either. The three layers fail independently, so evidence from one layer must never be used as proof about another. A card that displays perfectly can still have an unreachable encoder, and a card whose encoder works perfectly can still show a black capture.
OBS itself makes this harder to notice. In Simple output mode, OBS shows only the encoders that currently exist. A missing encoder is not listed with a warning that it is missing; it quietly disappears from the list. To see the full encoder list, switch to Advanced output mode and open the Output page. That is where the absence becomes visible, and where the exact missing encoder can be named. Recording which encoder is missing, and in which mode it was checked, is the first step of the diagnosis, and it must be done before anything is changed.
What NVENC, AMF and Quick Sync Actually Are
A hardware encoder is a fixed-function block built into the graphics hardware. Its job is to compress video into a stream — H.264, HEVC, or AV1 — without using the 3D rendering cores and without loading the processor. Rendering and encoding are two different jobs, carried out by two different parts of the hardware. That separation is the reason a machine can render a game perfectly while its encoder is unreachable, and it is also the reason the software encoder test in this guide works as a control: switching to x264 moves the encoding job onto the processor, bypassing the hardware encoder block entirely.
Codec support is locked to the hardware generation, and no driver update can add it. AV1 encoding through NVENC is available only on the RTX 40 and 50 series, according to the published NVIDIA matrix. An Ampere card will never gain AV1 encoding, however many times its driver is updated. That is not a fault and not a driver problem; it is a capability limit of the hardware itself. The same applies in the other direction: an entry-level card may have no usable hardware encoder at all, and that absence is a property of the card, not a sign that it is broken.
OBS has also changed how it reports this. From OBS 33 onwards, OBS checks at start-up whether an encoder used previously is still present, and if it is not, OBS reports an "Encoder Missing" error. Older versions of OBS did not perform this start-up check, so the same machine could show no error on an older version and an error on a newer one. The error is new information about the encoder layer, not new damage to the card. The official OBS knowledge base lists the NVENC check errors that can appear, including "No NVIDIA GPUs found", "No NVIDIA devices with NVENC support found", and "Encoder session limit exceeded", which means another program is already using the encoder. Kepler-generation cards are no longer supported for NVENC in current OBS versions, and AV1 is listed as unsupported where the hardware does not provide it. An OBS update can also demand a newer driver software development kit, so a driver and an OBS version that do not match can produce a "Failed to initialize video encoder" error even when the card itself is fine.
There is one more encoder that is easy to overlook. A missing audio encoder can also prevent output from starting, even when every video encoder is present. If output refuses to start and the video encoder list looks complete, the audio encoder deserves the same check as the video encoder, because output needs both.
The Five Layers of Suspicion
Once the missing encoder is named, the fault can be placed in one of five layers. Each layer has its own decisive check, and the order runs from the most common and least destructive to the deepest.
| Layer | What it covers | Decisive check |
|---|---|---|
| 1. Driver layer | The driver is damaged, its version does not match this OBS version, or the installation is incomplete, so the system layer cannot see the encoder | Update the driver to the current release; if the fault began after a driver update, compare against the version that previously worked |
| 2. Occupancy layer | Another program is already using the encoder, and the simultaneous session limit has been reached, so OBS cannot obtain an encoder session | Close every program that may be using the hardware encoder, then reopen OBS and see whether the encoder returns |
| 3. GPU selection layer | OBS is running on the wrong graphics processor in a machine with more than one, so the encoder it looks for is not on the processor it is using | Check which graphics processor OBS is running on in Windows graphics settings, and confirm at the system layer that the card is visible |
| 4. Capability layer | The card itself has no such encoder, or the codec is locked to a newer hardware generation, so there is nothing to recover | Check the published hardware matrix for this card and this codec; a codec the hardware never had cannot be restored by a driver update |
| 5. OBS layer | The OBS version changed its encoder check, or the OBS settings file is damaged, so the encoder disappeared after an OBS update | Note whether the fault began immediately after an OBS update, and compare the encoder list in Simple mode against Advanced mode |
The order is itself the diagnosis. A reader who jumps to layer four and concludes the card is too old has skipped the driver and occupancy checks, which cost nothing and often answer the question. A reader who works through the layers in order will either find the fault early or arrive at the deeper layers with the cheap explanations already ruled out.
Two cautions belong with this table. First, the simultaneous encoder session limit is a number that has changed over time in published NVIDIA material, and it is not a fixed rule. Do not treat any single session number as a permanent limit; check the current published NVIDIA matrix and software development kit notes for the card in question. Second, the driver version that works is a matter of matching this OBS version against this driver release. Published guidance does not fix a single minimum driver version as a universal rule, and none is given here. The direction must follow the pairing of the installed OBS version and the installed driver, because updating can fix a damaged driver while rolling back can fix a driver that a new OBS version does not yet match.
The Seven Steps, In Order
The sequence below is the diagnostic method of this guide. The order is deliberate: each step rules out one layer before the next layer is touched, and no step is skipped because its answer seems obvious.
- Record which encoder is missing, and in which mode. Is NVENC missing, is AMF missing, or are all hardware encoders missing? Was this checked in Simple mode or in Advanced mode? Copy down the exact error message OBS shows, word for word — for example "Encoder Missing" or "Failed to initialize video encoder". Do not move to the next step until this record exists, because every later step is judged against it.
- Run the x264 software encoder isolation control. Switch the encoder to x264 software encoding and start output again. If x264 produces video, that proves the rendering and capture layers are working, and the problem is locked to the hardware encoder layer — rendering and encoding are two different jobs, and the software encoder has bypassed the hardware one. If x264 also fails to produce output, the problem is not in the encoder layer, and the investigation should return to capture and output settings instead. Note carefully: x264 producing video is a diagnostic result, not a repair. The hardware encoder is still missing, and the picture quality and processor load of software encoding are not the same as hardware encoding.
- Check which graphics processor OBS is running on. On a machine with more than one graphics processor, check in Windows graphics settings or the NVIDIA control panel whether OBS is running on the processor intended. Then confirm at the system layer that the card is visible, for example with the NVIDIA system management tool, which reports whether the driver has loaded and the card is present. Device Manager showing the card does not prove that software can see the encoder, so the system-layer check is a separate step, not a repeat of the Device Manager check.
- Compare the driver layer. Update the driver to the current release and test again. If that does not restore the encoder, perform a clean driver reinstall, following the established clean-reinstall procedure, and test again after each single change. If the fault began immediately after a driver update, compare against the version that previously worked and roll back to it for testing. Change only one thing at a time, and test immediately after each change. Do not delete driver folders or system files by hand, and do not change registry values as a general repair.
- Check for other programs occupying the encoder. Close video editing software, another live streaming or recording program, and 3D software that may be using the hardware encoder, then reopen OBS and see whether the encoder returns. The session limit is another form of "missing": the encoder exists, but every session is already taken, so OBS cannot obtain one. If the encoder returns after closing another program, the fault was occupancy, not damage.
- Compare with hardware-accelerated GPU scheduling switched off. Switch off hardware-accelerated GPU scheduling, known as HAGS, and test again. This step comes from an OBS forum reply that reports HAGS as a known source of conflict with OBS. It is a forum observation, not an official OBS conclusion, and it must be read as one. If switching it off improves matters, record that. If switching it off changes nothing, do not treat HAGS as the cause.
- Cross-test, or bring the card in. Try the same encoder in a different recording program, for example ShadowPlay or another encoder tool. If no other program can use the encoder either, the fault leans towards the driver or hardware layer. If another program can use the encoder normally, the fault leans towards an OBS-specific problem, and reinstalling the driver first would be the wrong move. Bring the card in with the full record: the OBS version, the driver version, which encoder is missing, the exact error message, and the system-layer result.
That record should be complete enough that an inspection can start at the right layer instead of repeating the whole sequence from the beginning. A record that says only "OBS cannot find the encoder" will be tested from scratch. A record that says which encoder, in which mode, with which exact message, on which OBS and driver versions, and after which steps, can be acted on at once.
Diagnostic Logic: Reading the Symptom
| Symptom | Most likely cause | Next step |
|---|---|---|
| NVENC missing, AMF and Quick Sync present | NVIDIA driver or occupancy layer, or OBS running on the wrong processor | Run the x264 control, then check GPU selection and the driver |
| All hardware encoders missing, x264 also missing | OBS itself or the output settings, not the graphics hardware encoder layer | Check OBS settings and the OBS version before touching the driver |
| Only AV1 missing, other encoders normal | Generation-locked capability, not a fault | Check the published hardware matrix; do not try to recover a codec the hardware never had |
| Encoder missing only after an OBS update | New OBS start-up check, or a driver and OBS version mismatch | Compare the OBS version against the driver, and check Advanced mode |
| Encoder missing only after a driver update | Driver pairing problem | Compare against the version that previously worked; consider rolling back for testing |
| Encoder returns after closing another program | Occupancy: the session limit was reached | Keep the other program closed while OBS runs, or record which program holds the session |
| Encoder missing in Simple mode, present in Advanced mode | Simple mode only lists encoders that currently exist | Use Advanced mode to see the full list; the encoder was hidden, not absent |
| Another program can use the same encoder normally | OBS-specific problem | Do not reinstall the driver first; investigate the OBS side |
| No program can use the encoder | Driver or hardware layer | Work through the driver layer, then bring the card in with the record |
| x264 produces video, hardware encoder still missing | Fault locked to the hardware encoder layer | Continue with GPU selection, driver, and occupancy checks; do not call x264 a repair |
| x264 also fails to produce output | Problem outside the encoder layer | Return to capture and output settings |
| Kepler card with current OBS, NVENC missing | Kepler NVENC no longer supported in current OBS | Use an older OBS version that still supports it, or replace the card; this is not a card repair |
Edge Cases That Are Not This Problem
Only one codec is missing, for example AV1, while other encoders work normally. That is a generation capability question, not a fault. Check the published NVIDIA matrix for the card, and do not ask the reader to recover through a driver update a codec the hardware itself does not have.
All encoders are missing, including x264. That is an OBS or output settings problem, not a graphics hardware encoder problem. The investigation should stay with OBS itself before any driver is touched.
The encoder disappeared only after an OBS update. That points at the new start-up check introduced in OBS 33, or at a mismatch between the new OBS version and the installed driver. Older OBS versions did not report this error, so the absence of the error before the update does not prove the encoder was healthy before it.
Another program can use the same encoder normally. That is an OBS-specific problem. Do not ask the reader to reinstall the driver first; the driver has already proved it can deliver the encoder to other software.
A Kepler-generation card with a current OBS version. OBS no longer supports Kepler NVENC, so the encoder will not appear. The direction is to use an older OBS version or to replace the card, not to repair the card.
The capture picture is black, but the encoder list is complete. That is not this guide. A black capture with a full encoder list belongs with the capture layer, and the encoder steps here do not apply to it.
The encoder is present but OBS reports overload during output. That is the opposite shape from this guide. Overload means the encoder exists and cannot keep up with the load; missing means the encoder cannot be selected at all. The two must not be given each other's fixes.
Six Common Mistakes
- Assuming that a missing encoder means the card is broken. Wrong. A damaged driver, another program occupying the encoder, OBS running on the wrong graphics processor, or an OBS version problem can all make an encoder disappear while the card itself is completely healthy.
- Assuming that Device Manager showing the card means OBS must see the encoder. Wrong. Device Manager showing the card only proves the display layer recognises it. The encoding layer is a separate check, and it can fail while the display layer passes.
- Assuming that switching to x264 and getting video means the problem is fixed. Wrong. x264 only bypasses the problem. The hardware encoder is still missing, and the picture quality and processor load are not the same as hardware encoding. It is a diagnostic control, not an equivalent repair.
- Assuming that updating the driver will always fix it. Wrong. A driver update can fix a damaged driver, but it cannot fix occupancy, a wrong GPU selection, or a generation-locked capability. Those three layers need their own checks.
- Assuming that overload and missing are the same thing. Wrong. Overload means the encoder exists but the load is too heavy; missing means the encoder cannot be selected at all. The two symptoms point in opposite directions, and their fixes must not be swapped.
- Assuming that a missing AV1 option is a driver problem that an update will fix. Wrong. AV1 support is locked to the hardware generation, and an older card will never gain it, however many times its driver is updated.
When to Stop and Bring the Card In
Stop changing settings when any step brings the encoder back and OBS outputs normally with it, and keep that combination. Do not keep changing the driver or clearing settings after the problem has gone, because each further change adds a new variable and can create a new problem.
Stop and bring the card in when all seven steps have been completed and the encoder is still missing, with the full record in hand — the OBS version, the driver version, which encoder is missing, the exact error message, and the system-layer result — or sooner if no program at all can use the encoder, because that points beyond OBS and towards the driver or hardware layer. Bring the card in with that complete record, so the inspection can start at the right layer.
Inspection takes place at Room 1209, Dali Plaza, Shek Mun. You can call 2186 8010, or reach the shop on WhatsApp at 6558 6806. Inspection is charged at the site's published three-tier fees of HK$400–2,800, with the actual quote following inspection. There is no home-visit service and no Mong Kok shop; inspection is carried out in the shop.
Frequently Asked Questions
The NVENC option is missing in OBS — does that mean my graphics card is broken?
Not necessarily. A damaged driver, another program occupying the encoder, OBS running on the wrong graphics processor, or an OBS version problem can all make the encoder disappear while the card itself is completely healthy. Work through the seven steps in order: record which encoder is missing, test x264 as a control, check which graphics processor OBS is running on, and compare the driver layer before deciding anything about the card.
Device Manager shows my graphics card, so why does OBS still say it can't find the encoder?
Because Device Manager and OBS perform two different checks. Device Manager showing the card only proves the display layer recognises it. The encoding layer is a separate check: OBS must be able to reach the fixed-function encoder block through the driver. That check can fail while the display layer passes, so a card that displays perfectly can still have an unreachable encoder.
What is the difference between an encoder being "overloaded" and an encoder being "missing"?
They are opposite shapes. An overloaded encoder exists: it appears in the list, it can be selected, and OBS complains during output that the encoder cannot keep up with the load. A missing encoder cannot be selected at all, because OBS cannot see it. Overload is a load signal, not a damage diagnosis. Missing is an availability problem in the encoder layer. Their diagnostic trees are completely different, and their fixes must not be swapped.
Switching to x264 software encoding produces video — does that mean the problem is fixed?
No. x264 producing video is a diagnostic result, not a repair. It proves the rendering and capture layers are working, and it locks the problem to the hardware encoder layer, because rendering and encoding are two different jobs. The hardware encoder is still missing, and the picture quality and processor load of software encoding are not the same as hardware encoding. Continue with the GPU selection, driver, and occupancy checks.
How can I check whether OBS is running on the correct graphics card?
On a machine with more than one graphics processor, check in Windows graphics settings or the NVIDIA control panel which processor OBS is assigned to, and confirm it is the processor intended. Then confirm at the system layer that the card is visible, for example with nvidia-smi, which reports whether the driver has loaded and the card is present. Device Manager showing the card is not enough on its own, because it only covers the display layer.
The encoder disappeared after a driver update — should I update the driver again or roll it back?
Neither direction is a fixed rule. Published guidance does not fix a single minimum driver version as a universal rule, and the correct direction depends on the pairing of this OBS version with this driver release. If the fault began immediately after a driver update, compare against the version that previously worked and roll it back for testing. If the driver was already old or damaged, updating to the current release may restore the encoder. Change only one thing at a time and test immediately after each change.
Can other programs using NVENC stop OBS from finding the encoder?
Yes. The encoder has a simultaneous session limit, and when another program — video editing software, another recording or streaming program, or 3D software — is already using it, OBS may be unable to obtain a session, so the encoder appears missing. Close every program that may be using the hardware encoder, then reopen OBS and see whether the encoder returns. The session limit number itself has changed over time in published NVIDIA material, so check the current published matrix rather than relying on any single fixed number.
Why is the AV1 encoding option missing, and why doesn't updating the driver bring it back?
Because AV1 encoding support is locked to the hardware generation. AV1 encoding through NVENC is available only on the RTX 40 and 50 series, according to the published NVIDIA matrix. An older card will never gain AV1 encoding, however many times its driver is updated. That is a capability limit of the hardware itself, not a fault and not a driver problem, so no driver update can restore it.
Why does OBS show "Encoder Missing" only after I upgraded OBS?
Because OBS changed how it reports this. From OBS 33 onwards, OBS checks at start-up whether an encoder used previously is still present, and if it is not, OBS reports an "Encoder Missing" error. Older versions did not perform this start-up check, so the same machine could show no error before the upgrade. An OBS update can also demand a newer driver software development kit, so a mismatch between the new OBS version and the installed driver can produce a "Failed to initialize video encoder" error as well.
When should I send the card in for inspection, and what should I record first?
Send it in when all seven steps have been completed and the encoder is still missing, or sooner if no program at all can use the encoder. Record first: which encoder is missing, whether it was checked in Simple or Advanced mode, the exact error message word for word, the OBS version, the driver version, and the system-layer result. Inspection takes place at Room 1209, Dali Plaza, Shek Mun. You can call 2186 8010, or reach the shop on WhatsApp at 6558 6806. Inspection is charged at the site's published three-tier fees of HK$400–2,800, with the actual quote following inspection.