A Shotcut export preset is not a self-contained recipe — the Shotcut User Guide describes it as "a list of thing to change from the defaults." (That wording, typo included, is the guide's own.) Defaults are one thing your two computers share. Hardware encoders are not.
So when a preset that exports perfectly on your desktop fails, stalls, or produces a different-looking file on a laptop, the preset file is usually intact. What changed is the machine underneath it.
What "the preset didn't work" actually means
The guide is unusually direct about this case. If the preset is used on a system where the hardware encoder is unavailable, it lists three outcomes:
- "The export may fail"
- "Shotcut may fall back to software encoding"
- "Results may differ from expectation"
Read those as three parallel possibilities, not a sequence. The guide says may in all three, and it does not say which one you get — so a preset that "doesn't work" on the second machine can show up as a red X in the Jobs panel, as an export that finishes but takes far longer, or as a file that completes and simply looks or sizes up differently than the one you're used to. All three are the same root cause wearing different clothes.
The same section sets expectations bluntly. Export presets, it says, are not "Project templates", not "Guaranteed-safe configurations", and not "Automatically compatible with all codecs or hardware encoders".
The fastest fix: check the hardware encoder checkbox first
This is the single highest-yield thing to look at, because of a rule most people never read:
"Presets may include hardware encoders. However, the Use hardware encoder checkbox will still affect which codec is used unless you choose a hardware codec that Shotcut does not manage, for example ProRes."
In other words, the checkbox on the new machine can override the encoder your preset asked for. The preset does not win that argument — except for codecs Shotcut doesn't manage, with ProRes named as the example.
So on the second computer, open the Export panel and look at Use hardware encoder before you look at anything else. The guide explains what happens when you tick it:
"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 status line is easy to miss and it disappears. Watch it. If you want to see or change what detection found, the guide points at the same dialog: Configure... "opens a dialog for the configuration of the hardware encoder", 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."
And the blunt verdict, from the Quick Start Guide's exporting table: "If nothing is detected then your graphics card is not compatible." At that point the preset isn't the problem — the second machine simply cannot do what the first one did, and a software-encoded export is the path forward.
Try it right here
Runs in your browser. Your file is not uploaded anywhere.
If the reason you're moving the preset around is just to get one file to a sane size on a machine that won't cooperate, the compressor above does it in the browser tab — nothing installed, no preset files, no encoder detection. It's a reasonable escape hatch while you sort the editor out, and the rest of the browser tools are listed on the tools page.
Other causes, roughly in order of likelihood
1. Shotcut never loaded the preset file. Copying a preset is a documented workflow, but it has a step people skip:
"Presets are saved as files in the presets > encode folder in the app data directory (Settings > App Data Directory > Show). You can share these with others. You must restart Shotcut after manually adding preset files in order for Shotcut to see them."
If your preset isn't in the list on the new machine, restart before troubleshooting anything else.
2. The encoder is listed but unchecked. In the Configure dialog, a greyed or unticked entry has a specific meaning. Shotcut "automatically scans the system and lists all hardware encoders it can access on the current operating system", and "Unchecked options mean: The encoder exists in Shotcut But is not available on your system". For NVIDIA entries specifically, "If unchecked, it usually means no NVIDIA GPU is detected." Availability depends on "Your GPU vendor (Intel, AMD, NVIDIA)", "Installed drivers", "Operating system support", and "Enabled APIs (VAAPI, NVENC, etc.)" — so identical GPUs with different drivers can behave differently.
3. The preset's combination is invalid on this machine. The guide's list of common pitfalls includes "Choosing a codec not supported by the selected container" and "Enabling hardware encoding with unsupported formats", and says these issues can "Cause export failure", "Produce unplayable files", or "Result in silent audio or missing video". If the export finishes but has no sound or no picture, that's the branch you're on — not a corrupt preset.
4. It's a 10-bit H.264 preset. Shotcut's release notes record that "Fixed 10-bit H.264 encoder fails with hardware encoding on" in Release 26.6.25, with the explanation: "No H.264 hardware encoders support 10-bit; this change simply makes it use software encoding with x264."
5. The output is HDR and the metadata vanished. Also from Release 26.6.25: "Export only embeds PQ HDR metadata for the libx265 and libsvtav1 video codecs and no hardware encoders." A preset that lands on a hardware encoder on machine two will not carry that metadata — a textbook case of results differing from expectation.
If you're in Advanced mode, keep the guide's own warning in view: it says Shotcut "expects you to be advanced and know what you are doing", and that advanced export mode "lets you create invalid combinations and does not protect you from yourself."
How to tell it worked
Watch the Jobs panel, not the progress bar. A failed job shows "Failed (Red X): The task encountered an error. You can right-click these to view a log for troubleshooting." The guide describes View Log as essential for diagnosing failed exports — it opens a text window showing the technical output of the process. Once you've changed a setting, Repeat "Restarts a finished or failed job using the original settings" — useful for confirming a job fails the same way twice.
For a job that hangs rather than fails, the FAQ gives a procedure worth memorising: stop the job from the Jobs panel, try again with "Export > Video > Parallel processing disabled (unchecked)", and if it still stalls, note the percentage it reached and apply that percentage to your project duration to find roughly where in the timeline the trouble sits. Then look at what's unusual there.
FAQ
Why does my Shotcut export preset work on one PC but not another? Because presets can reference hardware encoders, and those depend on the machine. The guide says that on a system where the hardware encoder is unavailable, the export may fail, Shotcut may fall back to software encoding, or results may differ from expectation.
Does Shotcut automatically fall back to software encoding? It may. The guide lists that as one of three possible outcomes alongside outright failure, so do not assume a silent, automatic fallback is guaranteed.
Where are Shotcut export presets stored?
In the presets > encode folder inside the app data directory, reachable via Settings, App Data Directory, Show. The guide notes you must restart Shotcut after manually adding preset files.
Does the Use hardware encoder checkbox override my preset? Yes, with one exception. The guide states the checkbox "will still affect which codec is used unless you choose a hardware codec that Shotcut does not manage, for example ProRes."
Do I even need a preset to export? No. The guide says choosing a preset is not necessary, and that Shotcut's default values create an H.264 MP4 that adapts to your project's resolution, frame rate, and visual complexity. Clicking Reset or the preset named Default restores those values.
What if I just need the file smaller, not perfect? Export with whatever works on that machine, then shrink the result — compress a video in your browser or convert the container with MOV to MP4. More export troubleshooting lives in the fix guides.
All quotations are from the official Shotcut User Guide, FAQ, and release notes, checked 16 September 2026. Release-note lines describe what changed in that version, not the current state of every build — verify against the official documentation for your version.
