A file on disk does not prove an export is usable, and a failed-job label does not by itself prove that the file is unusable. Shotcut’s support documentation notes that, in some cases, the background export program can fail during cleanup; it recommends opening the result in Shotcut and running an Integrity Check Job. Treat that check as evidence about the file, not as a rewrite of the original export task’s status.
Check the output in a deliberate order
- In the Jobs panel, record the original export’s displayed status and any exit code shown. Keep the job log if you may need to troubleshoot later; Shotcut’s export troubleshooting guide identifies the job log as a useful place to inspect failure details.
- Locate the exact output path associated with that job. Confirm that the candidate file is the intended export, rather than an earlier file with a similar name. Its existence is only a reason to inspect it, not evidence that it is complete.
- Open the candidate file in Shotcut so that it is loaded as media. If Shotcut cannot load it, note that result and do not treat the integrity check as completed.
- With the loaded file selected in Properties, open the Properties menu and choose Start Integrity Check Job. Then observe the new task in the Jobs panel. The Properties documentation lists this command and confirms that its result appears in Jobs.
- Record the integrity-check job’s final status separately from the original export task. Decide whether to use the file only after reviewing both records and confirming that the file contains the intended material.
A successful integrity check is relevant evidence, but do not inflate it into a guarantee about creative requirements that the check does not claim to evaluate. For example, separately judge whether the output has the expected content and duration for your delivery.
A two-column acceptance worksheet
The following is a hypothetical record to show how to separate task evidence from file evidence. The observations are illustrative, not results from a Shotcut test. The numbers are user-recorded facts; no size threshold or automatic pass rule is implied.
| Export task record | Output file record and decision |
|---|---|
| Status: failed; log shows exit code 3 | Candidate exists and loads in Shotcut; Integrity Check Job: completed, result noted as reported; review the content before accepting |
| Status: failed; no exit code recorded | Candidate exists but cannot be loaded; integrity check not run; do not accept on file existence alone |
| Status: failed; cleanup failure is suspected from the available report | Candidate loads; Integrity Check Job reports failure; hold the file and investigate rather than treating the export as verified |
Replace these hypothetical observations with what your own Jobs panel and loaded media show. Preserve the original task status even when the file appears usable: the two columns answer different questions.
Limits and what to do next
The supplied Shotcut documentation describes how to start the check and observe its job, but does not define a universal interpretation for every possible result or promise that the check validates editorial choices. If the file will not load, the check fails, or its result is unclear, keep the file unapproved and inspect the original job log for clues. The troubleshooting guide advises looking at log details, including exit codes; those clues can guide a separate diagnosis, but they do not replace checking the candidate file. If you cannot establish whether it is complete, create a new export to a distinct destination and evaluate that output independently. Keep the original candidate and records until you have made the replacement decision.
Three quick questions
Does a file’s presence mean the export succeeded? No. It establishes only that a file exists at that location; loading and the integrity-check result provide additional evidence.
Does a failed export job prove the file is broken? Not always. Shotcut documentation gives an example of a background program failing during cleanup and recommends checking the result separately.
Should I change the original task to “passed” if the check succeeds? No. Record the export task and Integrity Check Job independently, then make a separate use decision.
Sources and next step
- Export failed - Find solutions - Documentation - English - Shotcut Forum
- Audio/Video Properties - Documentation - English - Shotcut Forum
This guide interprets public documentation and uses explicitly hypothetical acceptance examples, not application tests. Controls and availability can change; verify the cited manual against your installed version.
For work created in Imagild, carry the input requirements and acceptance checklist into the film workspace. The external software controls discussed above belong to their respective products.