Shotcut export failed or the video won't play? How to fix it

By the FixMP4 engineering team · · 9 min read

Shotcut is a free, open-source editor built on the MLT framework and FFmpeg. That gives it support for almost any input, but it also means an export failure can come from several layers: the codec settings, the GPU encoder, a problem clip on the timeline, or the disk the file is being written to. Shotcut is good at telling you which one, if you know where to look. This guide starts there and then covers the common failures one by one.

Read the job log first

Exports run as jobs. When one fails, the Jobs panel marks it as failed, and the reason is in its log:

  1. Open the Jobs panel (View, Jobs if it is hidden).
  2. Right-click the failed job and choose View Log.
  3. Scroll to the bottom. The last ten lines matter most.

Messages you are likely to see, and what they mean:

Log message containsMeaning
"Cannot load library", "No capable devices", "nvenc", "qsv", "amf", "vaapi"Hardware encoder failed to start
"No space left on device", "Error writing"Destination disk full or not writable
"Invalid data found", "error while decoding"A source clip has damaged data
A crash with no message, at the same percentageUsually a single problem clip or filter at that point
Memory errors on long or 4K timelinesNot enough RAM for the current settings

Hardware encoding

The Export panel has a "Use hardware encoder" checkbox. When ticked, Shotcut sends encoding to NVIDIA NVENC, Intel Quick Sync, AMD AMF or VA-API, depending on your computer. It is fast, but it fails when:

  • the GPU does not support the chosen codec, for example HEVC on older graphics or AV1 on most cards a few years old;
  • the driver is outdated or the encoder is busy with another application such as a game capture tool;
  • the resolution or frame rate exceeds what the encoder supports.

Untick the option and export again. If the software export succeeds, update the graphics driver and use the "Configure" button next to the checkbox to let Shotcut detect which hardware encoders actually work on your system.

Problem clips on the timeline

If the export always fails or freezes at the same percentage, the cause is almost always what is on the timeline at that moment. Convert the percentage into a time: an export failing at 60% of a 10-minute project has trouble around the 6-minute mark.

Common culprits:

  • Variable frame rate phone footage and screen recordings. Shotcut warns about these on import and offers to convert them. Accept the conversion, which creates an edit-friendly copy, and replace the clip in the project.
  • Damaged source files. A phone video that was cut off when the battery died may import and preview but break the export when the encoder reaches the damaged part. Check the source on its own in a player.
  • Heavy filters. Stabilisation, some third-party plugins and stacked effects can crash on specific frames. Temporarily disable filters on that clip and export again to test.

If a source file is damaged because its recording was interrupted, repair it before you rebuild the edit. The FixMP4 repair tool rebuilds missing MP4 and MOV indexes in your browser using a healthy clip from the same camera as a reference, and our guide to repairing MP4 files explains the process step by step.

Proxies and preview scaling

Shotcut's proxy editing and preview scaling make editing smoother on slower computers, and exports normally use the full-quality originals automatically. Problems arise when the originals have moved or been renamed since the proxies were made. Shotcut then reports missing files when the project opens, and an export can fail or contain placeholder frames. Use the Missing Files dialog that appears when the project opens to point Shotcut at the originals again before exporting.

Disk space and destination

An export of a long 4K timeline can take tens of gigabytes. Shotcut writes the file progressively, so a full disk near the end leaves a file that is the right size up to that point but has no index. Before exporting:

  • check free space on the destination drive;
  • avoid exporting straight to a USB stick or network share; write to an internal disk and copy afterwards;
  • on FAT32-formatted drives, remember the 4 GB per-file limit, which stops long exports cold.

An export that will not play

If the job finished but the file will not play, or plays only in some players:

  • Plays in VLC but not in Windows Media Player or QuickTime: the chosen codec or settings are not supported by that player. The built-in "YouTube" or "H.264 High Profile" presets produce files that play everywhere.
  • Audio but no picture on Mac: HEVC exported with the hvc1 tag missing, or a codec QuickTime does not support. Use an H.264 preset for maximum compatibility.
  • Will not open at all, normal file size: the export was interrupted, and the index was never written.

For that last case, the fastest fix is to export again. If you no longer have the project or the sources, the file can be repaired: export a few seconds of anything with exactly the same preset to create a reference, then use the repair tool. It reads the raw H.264 or HEVC frames, rebuilds the sample table and lets you check a free preview before saving. If you want to see what is wrong first, the MP4 file checker shows whether the index is missing.

Shotcut crashed during the edit, not the export

Shotcut autosaves projects. After a crash, it offers to recover the autosave when you next start it. Accept, then save the recovered project under a new name. Your source media is not affected by an editor crash, so nothing beyond the latest edits should be lost.

Settings that rarely fail

When you just need a file that works, these export settings are reliable in Shotcut:

  • Format mp4, video codec libx264, rate control Quality-based VBR around 60-70%;
  • audio codec aac at 192 kbps;
  • frame rate matching the project, with "Use hardware encoder" off;
  • interpolation and deinterlacer left at defaults.

For more editor-specific export problems, see our pieces on CapCut exports, Premiere exports and HandBrake's "No valid source found".

Using Filmora rather than Shotcut? See Filmora export failed or corrupted.

Frequently asked questions

Why does my Shotcut export fail?

The most frequent causes are the hardware encoder option on a GPU that does not support the chosen settings, a source clip with variable frame rate or a damaged section, too little disk space at the destination, and running out of memory on long 4K timelines. The job's log names the step that failed.

Where do I find the Shotcut export error log?

Open the Jobs panel, right-click the failed job and choose View Log. The last lines usually contain the actual error, such as an encoder initialisation failure, a missing file or a write error.

Should I turn off "Use hardware encoder" in Shotcut?

If exports fail or produce green or corrupted frames, yes. Untick it in the Export panel's codec settings and export with the software encoder. It is slower but works on every system, and it rules out the graphics driver as the cause.

Can I repair a Shotcut export that stopped partway?

If the export was writing an MP4 or MOV and stopped before finishing, the file lacks its index. FixMP4 can rebuild it in your browser using a short successful export with the same preset as the reference, but re-exporting from the project is quicker when it is still available.

Have a broken recording right now?

Diagnose it and hear or watch a free repaired preview. Nothing is uploaded.

Open the repair tool
  • Shotcut
  • export
  • FFmpeg
  • hardware encoder
  • MP4