A slow Shotcut export is usually not one wrong setting — it is the CPU doing a pile of work the GPU was never asked to do. Shotcut's own FAQ says so in plain language, and once you have read it the usual advice ("just turn on hardware encoding") stops being a complete answer.
What actually determines Shotcut's export speed
Turning on Use hardware encoder moves exactly one stage of the pipeline onto your GPU: the encoding. Everything upstream still runs on the CPU, and Shotcut's FAQ is unusually direct about the consequence:
"Thus, 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. Also, if you have any decent amount of image processing, you should expect a significant amount of CPU usage especially if parallel processing is enabled."
The same FAQ then lists, item by item, what Shotcut does not put on the GPU by default. Its heading is "By default (CPU processing modes), Shotcut does NOT use the GPU for the following:" and underneath it are five things:
- "automatic (as-needed) filters to deinterlace, scale, and pad video and to resample or downmix audio"
- "filters that you add"
- "transitions"
- "compositing/blending video tracks"
- "mixing audio tracks"
Read that list against your actual timeline. Every filter you added, every transition, every stacked video track and every extra audio track is CPU work — which is why two projects of identical length can export in wildly different times on the same machine with the same encoder selected.
Shotcut explains why it is built this way rather than pushing the whole pipeline onto the GPU: "Software from other companies may limit itself to one GPU vendor API such as CUDA in order to provide almost entirely GPU-based pipeline. Shotcut has not chosen to go that route because it is a cross-platform solution."
The fastest fix: confirm the hardware encoder is actually engaged
The Shotcut User Guide (June 2026 edition) describes the checkbox and, importantly, how to tell whether it took effect:
"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."
If that message is not encouraging, open Configure... next to the checkbox — the guide describes it as 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 gives the blunt verdict for the bad case: "If nothing is detected then your graphics card is not compatible."
One thing that confuses people in that dialog: unticked encoders are not disabled features. The guide states that "Unchecked options mean: The encoder exists in Shotcut But is not available on your system", with availability depending on your GPU vendor, installed drivers, operating system support and enabled APIs.
The guide's own recommendation: "Enable hardware encoding for: Long exports High-resolution video Preview or draft renders Laptop or low-power systems", and prefer software encoding for "Maximum compression efficiency Archival-quality exports Advanced codec tuning".
Try it right here
Runs in your browser. Your file is not uploaded anywhere.
Worth separating two goals. If you need the edit rendered, you have to export from Shotcut. But if you already have an exported file and the real problem is that it is too big to send, re-encoding that finished file in your browser beats re-exporting the timeline, and it never leaves your device — whether you are compressing it for upload or pulling the audio out.
Other causes, in rough order of likelihood
1. You turned on the hardware decoder. This is the counterintuitive one. Release 26.1.30 added Export > Codec > Use hardware decoder, and the release note says outright: "It defaults OFF because it often increases the export time." Note the word — often, not always. But if you enabled it hunting for speed, that is a prime suspect. Shotcut's FAQ gives the underlying reason it limits hardware decoding in the first place: "The video stream always originates in system (CPU) RAM, and CPU-based video decoding is highly optimized and fast. Meanwhile, transferring full, uncompressed video from the GPU RAM to system RAM is relatively slow." The FAQ scopes hardware decoding to "1080p or less or with preview scaling".
2. Processing Mode is set to a slow one. Added in version 25.12 and, per Release 25.12.30, it "affects both preview and export". The guide labels the options itself: "Native 8-bit CPU (fast, flexible)", "Native 10-bit CPU (slower, better)", "Linear 10-bit CPU (slowest, best)", plus an experimental GPU/CPU mode. Those parenthetical labels are the official wording; no speed multiplier is published for them.
3. You are exporting a draft at full fidelity. The guide notes that "Export > Advanced > Video has the option Use preview scaling" and that "This is intended to provide a faster export for draft review." It also warns that preview scaling "does not provide perfect fidelity and full precision", with blur, softness and noise being where differences show. One exception: the Stabilize filter disables preview scaling on the clip it is applied to, because the two are incompatible.
4. The job is running at low priority. Shotcut's configuration keys document a setting for "the priority of background melt and ffmpeg jobs such as export and proxy: low (default) or normal". The guide's Job Priority section, introduced in version 22.01.30, describes Low as the default and recommended value, with Normal aimed at the efficiency cores on 12th-generation Intel CPUs.
5. Several exports are queued. "Sequential Processing: By default, Shotcut processes one job at a time to maximize system resources. As one job finishes, the next in the list begins automatically." A job that looks frozen may simply be waiting its turn.
6. Your machine is at the edge of the requirements. The FAQ asks for "at least one 2 GHz core for SD, 4 cores for HD, and 8 cores for 4K" and "At least 4 GB for SD, 8 GB for HD, and 16 GB for 4K". If memory is the constraint, the guide's advice is to turn off Export > Advanced > Video > Parallel processing because "That uses more threads, which needs more memory", turn the hardware encoder on, and reduce the Video Mode resolution.
Slow, or actually stuck?
These are different problems, and Shotcut documents a specific test for the second. Its FAQ answer for a failing or hung export reads:
"If a job appears to be stuck or hung (please allow ample time for percentage to change), right-click the job in the Jobs panel and choose Stop. Try export again with Export > Video > Parallel processing disabled (unchecked). If there is still a problem see what percentage it reaches before failing or hanging. Then, apply the percentage to your project duration to find the rough time of where it seems to be having trouble. Is there something complicated or different there? You can temporarily remove some things in this area and try again to see if export goes further."
That percentage-times-duration trick is the most useful line in Shotcut's troubleshooting section. A 10-minute project that stalls at 40% points you at roughly the four-minute mark — go look at what is there.
How to tell it worked
Watch the percentage in the Jobs panel move, not the wall clock, and heed the guide's instruction during any export: "Do not close Shotcut until the export finishes." If one ends in failure, right-click the job — the guide calls View Log "Essential for diagnosing 'Failed' exports", and Repeat "Restarts a finished or failed job using the original settings."
FAQ
Why is my CPU at 100% when hardware encoding is on? Because only the encode stage moved to the GPU. Shotcut's FAQ states that file reading and decoding alone become a bottleneck feeding the hardware encoder, and that image processing adds significant CPU usage on top, especially with parallel processing enabled.
Should I turn on Use hardware decoder to speed up export? Shotcut ships it off. The Release 26.1.30 note says it defaults off because it often increases export time, so treat it as something to test rather than assume.
Does hardware encoding make my video look worse? Shotcut's guide explicitly pushes back on that framing: "Hardware encoding is usually less compression-efficient, not lower quality." It also notes that file sizes may be larger at the same quality target — a bigger file from the hardware encoder is expected behaviour, not a bug.
Will turning off Parallel processing make export faster? Not necessarily. Shotcut lists disabling it as the first step when an export fails or hangs, and as a way to reduce memory usage — both of which are about finishing at all, not about finishing sooner.
How much faster will hardware encoding make my export? The gain depends on your resolution, the encoder your GPU exposes and the GPU itself — check the official documentation rather than a third-party multiplier. The guide's own advice is to reach for it on long exports, high-resolution video, draft renders and low-power machines.
Sourced from Shotcut's official FAQ, the Shotcut User Guide (June 2026) and the official release notes, as captured in September 2026. More troubleshooting walkthroughs are in the fix guides, and the browser-based converters are listed under all Clapr tools.
