When Shotcut finds no hardware encoder, the official Shotcut User Guide treats that as a statement about your machine, not about a setting you forgot to flip. The Quick Start Guide's export table says it in one line: "If nothing is detected then your graphics card is not compatible."
That is blunt, and it is also the most useful sentence in the documentation for this problem, because it tells you where to stop looking. Here is what detection actually does, why the Configure dialog lists encoders that are unchecked, and the causes worth ruling out before you accept that verdict.
What "not detected" actually means
Hardware encoding is a checkbox in the Export panel. The User Guide (June 2026 edition) describes it this way: "Use hardware encoder is option to use the hardware-accelerated encoder in your NVIDIA or AMD GPU or CPU (Intel Quick Sync on most processors since 2012, but it may depend on your motherboard as well)."
Note the qualifier at the end. Even on the Intel side, the guide does not treat a recent CPU as a guarantee — it says it may depend on your motherboard as well.
Detection is triggered by the checkbox itself: "You will need to tell Shotcut which you have, but if it has not been configured Shotcut tries to automatically detect it when you click the checkbox to turn it on. Pay attention to the status message area just below the player controls for several seconds after clicking the checkbox to see what it reports."
That is the first thing most people miss. The result is reported in the status message area under the player controls, for a few seconds, and then it is gone.
What the scan covers is also narrower than "your GPU": "Shotcut automatically scans the system and lists all hardware encoders it can access on the current operating system." The guide lists what that access depends on:
- "Your GPU vendor (Intel, AMD, NVIDIA)"
- "Installed drivers"
- "Operating system support"
- "Enabled APIs (VAAPI, NVENC, etc.)"
So "not detected" can come from any of those four layers, not only from the card itself.
The fastest fix
- Tick Use hardware encoder in the Export panel and watch the status message area below the player controls for several seconds.
- Open Configure... to see the result. Per the guide, it "opens a dialog for the configuration of the hardware encoder. This is useful in case there was a problem with automatic detection, you want to see what automatic detection found, or you want to change it if you have more than one available on your system." The Quick Start table also points you at Configure and its Detect action to set the encoder.
- If the scan still reports nothing, apply the official criterion quoted at the top and move on to a software export.
Losing hardware encoding is not the same as losing the export. The guide is explicit that you do not need a preset at all: "It is not necessary to choose a preset! Shotcut comes with default values that creates a high quality H.264 MP4 file at a reasonable size and speed that automatically adapts to the resolution, frame rate, and visual complexity of your project."
If what you actually wanted from the hardware encoder was a smaller file to send somewhere, you can shrink the finished export in a browser tab instead of re-rendering the timeline:
Try it right here
Runs in your browser. Your file is not uploaded anywhere.
Nothing is uploaded — the file is re-encoded locally and handed back. More of these live in the Clapr tool directory.
Why the Configure dialog shows unchecked encoders
This is the question the forums answer badly, and the guide answers in one line. Under how detection works, it states:
"Unchecked options mean: The encoder exists in Shotcut But is not available on your system"
An unchecked entry is not a disabled feature and not a toggle you should force on. It means Shotcut ships support for that encoder, and the scan could not reach it here. NVENC gets the same treatment spelled out separately — those entries "appear only if: An NVIDIA GPU is present Proper NVIDIA drivers are installed", and "If unchecked, it usually means no NVIDIA GPU is detected."
The names follow a pattern the guide documents:
| Entry | What the guide says |
|---|---|
h264_vaapi | "H.264 encoding using VAAPI" |
hevc_vaapi | "HEVC (H.265) encoding using VAAPI" |
h264_nvenc, hevc_nvenc | listed as the NVENC equivalents |
_vaapi suffix | "Linux VAAPI backend" |
_nvenc suffix | "NVIDIA hardware encoder" |
The guide adds that "NVENC is NVIDIA's proprietary hardware encoder" and that "VAAPI (Video Acceleration API) is commonly used on Linux systems." Its explainer section covers those two backends. Other backend names show up in the release notes instead: h264_mf and hevc_mf were added for Windows on Arm CPUs as of Release 25.01.25, Release 24.08.29 records a fix for hevc_toolbox failing detection on some Intel Macs, and Release 20.07.11 records a fix for h264_qsv or hevc_qsv with Quality-based VBR on older Intel chips. Release 22.01.30 notes improved VA-API compatibility on Linux, particularly on Wayland.
Minimum driver versions or GPU models are not given anywhere in these pages — for those, check the official documentation.
Other causes, in order of likelihood
The preset is fighting you. The guide's limitations list includes "Some export presets may not support hardware encoders" and "Not all codecs are available on all GPUs". It also warns that if a preset is used where the encoder is unavailable, "The export may fail Shotcut may fall back to software encoding Results may differ from expectation" — those are listed as possibilities, not a promise of a clean fallback.
You are asking for 10-bit H.264. Release 26.6.25 fixed "10-bit H.264 encoder fails with hardware encoding on", and explains the scope precisely: "No H.264 hardware encoders support 10-bit; this change simply makes it use software encoding with x264." That is specific to H.264, not to hardware encoding in general.
You expected AV1. The two things the guide says about codec coverage do not line up. Export Basics says "This feature currently only supports the H.264 (aka AVC) and HEVC (aka H.265) codecs." The Hardware Encoding section in the same document lists "av1_vaapi -- AV1 encoding using VAAPI (if supported)" and "av1_nvenc (newer GPUs only)", and describes AV1 as "Very efficient, newest standard, limited hardware support". The release notes side with the latter: Intel qsv AV1 in Release 23.05.07, av1_nvenc in 23.11.29, AMD av1_amf and av1_vaapi in 24.02.29. Keep the qualifiers — "if supported", "newer GPUs only" and "limited hardware support" are the official wording.
You need HDR metadata. Release 26.6.25 states that export "only embeds PQ HDR metadata for the libx265 and libsvtav1 video codecs and no hardware encoders."
How to tell it worked
Re-tick the checkbox and read the status message area, then reopen Configure to see which encoder is now selected. If an export still fails, the Jobs panel is where the evidence is — a failed job shows a red X, and the guide describes the View Log entry on its context menu like this:
"Opens a text window showing the technical output of the process. Essential for diagnosing "Failed" exports."
Two things are normal once it does work. CPU use stays high — the FAQ says "you cannot expect Shotcut to use close to 0% CPU and much of the GPU when exporting using the hardware encoder because the reading of files and decoding alone becomes a bottleneck to feed the hardware encoder." And the file may be bigger: the guide's own framing is that "Hardware encoding is usually less compression-efficient, not lower quality."
FAQ
Why does Shotcut say no hardware encoder was detected? Because the scan could not reach one through your GPU vendor, drivers, operating system, or the enabled APIs. The Quick Start Guide's criterion is direct: "If nothing is detected then your graphics card is not compatible."
Why are the encoders in the Configure dialog unchecked? Unchecked is not "disabled". The guide states that it means the encoder exists in Shotcut but is not available on your system. For NVENC entries specifically, unchecked "usually means no NVIDIA GPU is detected."
Can I still export without hardware encoding? Yes. Shotcut's defaults produce an H.264 MP4 with the software encoder, and the guide says choosing a preset is not necessary at all.
Is a software export lower quality? The guide points the other way for hardware: it calls hardware encoding "usually less compression-efficient, not lower quality", and recommends software encoding for "Maximum compression efficiency Archival-quality exports Advanced codec tuning".
Why is my CPU still busy with hardware encoding on? Because decoding and image processing stay on the CPU. Shotcut's FAQ says reading and decoding files alone becomes a bottleneck feeding the hardware encoder, and that noticeable image processing will use significant CPU.
More export troubleshooting lives in the fix archive, and if the goal was simply a smaller file, compress the video after the export instead of chasing the encoder. Quotes above are from Shotcut's User Guide, FAQ and release notes as captured in September 2026 — verify against the current official documentation before relying on them.
