Shotcut's official user guide attributes silent audio in an export to invalid export settings, not to a bug in your project. If the timeline plays with sound but the exported file is mute, the guide points at three specific things — and all three live in the Export panel, not in your clips.
What silent audio in a Shotcut export actually means
The Shotcut User Guide has a short block on codec compatibility that is the hardest official statement on this problem. It lists the pitfalls:
"Examples of common pitfalls: Choosing a codec not supported by the selected container Enabling hardware encoding with unsupported formats Mixing incompatible pixel formats or profiles"
And then the consequences:
"These issues can: Cause export failure Produce unplayable files Result in silent audio or missing video"
That last line is the one that matters. Shotcut's documentation puts "silent audio" in the same bucket as a failed export — a symptom of a settings combination the app accepted but could not actually produce correctly. Note what is not in that list: nothing about your source clips, your audio tracks, or your mixer. All three named pitfalls are choices made in the Export panel.
The guide is also blunt about why Shotcut lets you build a broken combination in the first place. From the Export Basics section, describing the Advanced button:
"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."
"Does not protect you from yourself" is the whole story. There is no validation step that blocks a bad container-and-codec pairing before the job runs. The export completes, the progress bar reaches 100%, and the damage only shows up when you play the file.
The fastest fix: reset the Export panel
Because the documented cause is a combination, undoing the whole combination beats toggling options one at a time. The guide says outright 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."
So: open Export, click Reset (or select the preset named Default), export again. If the sound comes back, the fault was in the settings you had layered on top, and you can reintroduce them one at a time until it breaks again.
One trap while you do that. Advanced mode normally clears itself between sessions, but not if you pinned it:
"By default the next time you restart Shotcut, the advanced mode is turned off again. However, you can pin it to the on or enabled state by clicking the checkbox next to Advanced."
If you pinned it once, months ago, you may still be carrying overrides you no longer remember setting.
Try it right here
Runs in your browser. Your file is not uploaded anywhere.
If the only reason you were in the Advanced tab was to get a smaller file, that is worth reconsidering. Export with Default, then shrink the finished MP4 in the tool above — it runs in your browser tab, so the file never leaves your machine, and you keep Shotcut's export on the path its own defaults describe.
Other causes, in order of likelihood
1. Hardware encoding combined with a format that does not support it
This is pitfall number two in the official list, and the guide reinforces it twice in the presets section:
"Some export presets may not support hardware encoders"
"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."
Uncheck Use hardware encoder and export again. And do not assume Shotcut quietly rescued a broken configuration for you — the guide lists the outcomes side by side as possibilities:
"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"
"May fail" and "may fall back" are given as alternatives, not as a guaranteed safety net.
2. An audio codec the chosen container will not carry
Pitfall number one. In the Advanced export section, the guide names examples rather than complete lists — "Container: mp4 , mov , mkv , etc." and "Audio codec: AAC, Opus, PCM, etc." Both end in etc., so neither is a whitelist, and that section lists examples rather than compatibility rules. For any specific container-and-codec pairing, check the official documentation.
The practical move is the same as above: if you changed either dropdown by hand, put the panel back to its defaults, which the guide describes as producing an H.264 MP4.
3. A preset that came from somewhere else
Presets are plain files that travel between machines:
"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."
And the guide describes what a preset actually contains: "The preset is really a list of thing to change from the defaults." A preset someone posted for their GPU is a diff against the defaults, applied blind on your hardware. The documentation sets expectations accordingly:
"Export presets are not: Project templates Guaranteed-safe configurations Automatically compatible with all codecs or hardware encoders"
"Using presets assumes you understand the implications of the selected settings."
4. Advanced parameters copied from an ffmpeg command line
If you pasted extra options into the Advanced tab's Other field, note that they are not ffmpeg command-line arguments. The guide is explicit:
"Please keep in mind that Shotcut is not a ffmpeg command line front end except in the rare cases of Properties > Convert and Reverse and proxy media generation."
"Melt only accepts the encoder and muxer options here, but only some of ffmpeg's options are for the encoder and muxer."
It also notes that options there are written without leading dashes. An option that does not apply cleanly is exactly the kind of "invalid combination" the Advanced disclaimer warns about.
How to tell it worked
Play the exported file, obviously — but if you want evidence rather than a guess, the Jobs panel keeps it. The guide describes the right-click options on a job, including a log window that shows the technical output of the process, and a View XML entry that shows the MLT code actually sent to the background engine. That XML is where you can see which codec and container the job really used, as opposed to what you thought you selected.
One thing to avoid while testing: the Repeat entry in that same menu "Restarts a finished or failed job using the original settings." Repeating a silent export reproduces the silence. Change the settings first, then export fresh.
Also worth remembering from the Quick Start guide: "Do not close Shotcut until the export finishes."
Still stuck? Our other export troubleshooting write-ups cover neighbouring symptoms, and CapCut's version of the silent export is a useful comparison.
FAQ
Why does my Shotcut export have no sound when the timeline plays fine? Shotcut's user guide attributes silent audio to invalid export combinations: a codec the container does not support, hardware encoding enabled with an unsupported format, or mixed pixel formats and profiles. The timeline uses none of those settings, which is why playback inside Shotcut is unaffected.
Does turning off hardware encoding fix silent audio? It is the fastest thing to test, because "Enabling hardware encoding with unsupported formats" is one of the three documented pitfalls, and the guide separately warns that some export presets may not support hardware encoders. It is not guaranteed — if the sound is still missing, reset the panel to Default.
Is this a bug in Shotcut? The documentation frames it as a consequence of advanced settings rather than a defect. Advanced mode, in the guide's own words, "does not protect you from yourself" when you build combinations that are not valid.
Can I fix the file by changing its container instead of re-exporting? Not losslessly inside Shotcut. The guide states: "Shotcut can not "pass through" or copy codecs without re-encoding." The nearest thing is Properties > menu > Extract sub-clip, which the FAQ describes as not frame accurate and carrying some pitfalls.
How do I export audio only from Shotcut? The official FAQ's suggestion for extracting audio is "Ogg Vorbis, FLAC (lossless with compression), or good old MP3". If you would rather not re-export the whole project, you can pull the audio out of the finished video directly.
Getting a silent export twice in a row usually means the same preset is being reapplied. Reset first, export once with the defaults, and only then reintroduce the settings you actually need. Everything else in our browser-based toolkit is listed at all Clapr tools.
Quotations are from Shotcut's official User Guide (June 2026 edition) and the shotcut.org FAQ, checked September 2026.
