A failed Shotcut export is a failed background job, not a damaged project. Shotcut answers this in exactly one paragraph in its FAQ, and the most useful sentence in that paragraph is a locating trick that almost nobody repeats: take the percentage the export reached before it died, apply it to your project duration, and go look at that part of the timeline.
That is the official method, quoted below in full. Start there — it points at your timeline rather than at your computer.
What a failed export actually means
Exporting in Shotcut is a separate operation from saving. The user guide is explicit: "The Export panel (also File > Export Video...) is used to create a new video or audio file from your project because File > Save saves a project file." A failed export therefore costs you the output file and the time, not the edit.
Exports run as queued background jobs, and a failed one shows up in the Jobs panel with a specific marker — the guide describes it as "Failed (Red X): The task encountered an error. You can right-click these to view a log for troubleshooting."
The guide's Quick Start table also warns "Do not close Shotcut until the export finishes.", and its troubleshooting section opens with "At times exporting may fail." before conceding that "Video editing is a very complicated task for anyone and their computer."
The fastest fix: Shotcut's own sequence
Here is the whole official answer to "What can I do if Export is failing or getting stuck?", verbatim from the Shotcut FAQ:
"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."
Broken into steps:
- Give it time first. The FAQ's parenthetical matters — a percentage that has not moved for a while is not automatically a hang.
- Stop the job from the Jobs panel, by right-clicking it, rather than killing Shotcut.
- Re-export with parallel processing unchecked. The FAQ writes the path as Export > Video > Parallel processing; the guide's memory-reduction page writes the same control as Export > Advanced > Video > Parallel processing and gives the reason it helps: "That uses more threads, which needs more memory."
- Convert the failure percentage into a timecode. If the job dies at 18% of a 40-minute timeline, that is roughly the 7-minute mark. Go there and look for whatever the guide calls "something complicated or different" — then temporarily remove it and export again.
That last step turns a vague "export failed" into a bounded search over a few seconds of timeline.
Try it right here
Runs in your browser. Your file is not uploaded anywhere.
A related tactic: once any export completes — including a deliberately modest draft — you no longer need Shotcut to also hit a size target. Re-encoding that finished file in the browser above (or via compress video) is far simpler than re-running a fragile export at new settings.
Read the job log before you change settings
Before you start toggling codecs, read what the job actually said. The guide describes the Jobs panel context menu items directly:
- View Log — "Opens a text window showing the technical output of the process. Essential for diagnosing "Failed" exports."
- Repeat — "Restarts a finished or failed job using the original settings."
There is also an application-wide log, and it has a trap: "Note: The application log is cleared every time Shotcut starts up. When providing an application log to provide information about a problem, be sure to provide a log from the same session of Shotcut when the problem occurred. Click Previous to view the log of the previous session." So if your instinct after a failure is to restart Shotcut, do it after you have copied the log out.
The official pages we could find do not decode specific export error numbers — they route you to the job log instead.
Other causes, in order of likelihood
You are in Advanced mode with a combination that cannot work. The guide's own disclaimer is unusually blunt: "Click Advanced to show many more controls and options. However, by clicking Advanced you should understand that Shotcut expects you to be advanced and know what you are doing. There are simply too many combinations of settings and options that Shotcut's advanced export mode lets you create invalid combinations and does not protect you from yourself." It names the pitfalls — "Choosing a codec not supported by the selected container Enabling hardware encoding with unsupported formats Mixing incompatible pixel formats or profiles" — and the consequences: "These issues can: Cause export failure Produce unplayable files Result in silent audio or missing video."
The escape hatch is that you do not need a preset at all: "NOTE: 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. Clicking Reset or the preset named Default restores the panel to its default values."
The preset expects a hardware encoder your machine does not have. The guide lists this outcome explicitly: "If the preset is used on a system where the hardware encoder is unavailable: The export may fail Shotcut may fall back to software encoding Results may differ from expectation" — two parallel possibilities, not a guarantee of graceful fallback. It also notes "Some export presets may not support hardware encoders." When detection finds nothing, the Quick Start guide's verdict is "If nothing is detected then your graphics card is not compatible.", and greyed-out entries in the Configure dialog mean "The encoder exists in Shotcut But is not available on your system" — not that something disabled them. (For how the same trade-off looks elsewhere, see hardware acceleration in DaVinci Resolve.)
Memory. The guide's "How to Reduce Memory Usage" page lists turning off parallel processing, turning on the hardware encoder, "Reduce the resolution of the Video Mode.", and a heavy-handed one: reboot, open only Shotcut, load the project without playing through it, then export. The FAQ's stated minimum RAM is "At least 4 GB for SD, 8 GB for HD, and 16 GB for 4K."
Filenames, paths and specific clips. Shotcut's release notes name several concrete export-failure causes that were fixed in specific versions — "Fixed export with ‘&’ in the file path or name." (Release 25.10.31), "Fixed export on Windows not working with some special characters in a filename (broke in v25.10)." (Release 25.12.30), "Fixed odd value for computed width in Reframe output video filter causes export to fail." (Release 24.10.29), and "Some Lottie animations make export fail." (Release 22.06.23). These are records of what was fixed when, not statements about current behaviour — but they show what kinds of things have broken exports before, which helps when step 4 lands you on a specific clip.
How to tell it worked
The job leaves the Failed red X state and produces a file — then play that file all the way through. Silent audio or missing video is a documented symptom of an invalid container/codec combination, so a file that exists is not yet proof.
FAQ
Why does my Shotcut export fail at the same percentage every time? A repeatable percentage is the useful case, not the bad one. The FAQ tells you to apply that percentage to your project duration to find the rough time where it is having trouble, then temporarily remove things in that area and try again.
Should I turn off parallel processing in Shotcut? As a diagnostic step, yes — it is the first thing the official FAQ tells you to try after stopping the stuck job, and the guide separately lists it as a way to cut memory use because "That uses more threads, which needs more memory." Turn it back on once the export succeeds.
Does enabling the hardware encoder fix a failed export? Sometimes — the guide lists it under reducing memory usage. But it can also be the cause, since a preset that assumes a hardware encoder may fail on a system without one. After ticking the checkbox, watch the status message below the player controls to see what detection reports.
Where is the Shotcut export log? Right-click the job in the Jobs panel and choose View Log; the guide calls it essential for diagnosing failed exports. The separate application log is wiped on every startup, so copy it before restarting.
Is antivirus software or a network drive causing my Shotcut export to fail? Those are common forum theories, and the official Shotcut pages we could find do not discuss them. What the official docs do give you is the job log and the percentage-to-timecode method above — start there rather than with guesses.
Quotes are from Shotcut's official FAQ, user guide and release notes, checked 17 September 2026. Shotcut changes behaviour between releases, so verify against the current official documentation. More troubleshooting write-ups live in fixes, and the browser-based converters are listed under all Clapr tools.
