If a Shotcut clip stutters because real-time decoding, scaling, or effects are taxing the computer, try a proxy first. If the problem concerns how the source is structured or processed, such as variable frame rate (VFR) media or frame-accurate speed effects, consider converting it to an edit-friendly file. Conversion is not a general-purpose performance switch: it creates a new media file and replaces the project clip, while a proxy is an editing-time substitute for the original or converted media. Shotcut’s proxy documentation describes the playback workload reduction; its edit-friendly conversion documentation lists supported reasons to convert.
Decide what problem you are solving
- Identify the symptom. If playback is slow but the source behaves correctly when seeking or applying the intended effect, try proxy editing. Shotcut says proxies reduce real-time work by using fewer pixels; they do not change the source’s frame structure.
- Check the clip’s Properties and note any evidence relevant to the task, such as VFR media or a time-remap effect that needs frame-by-frame control. The conversion documentation names VFR, HDR, intra-only conversion for speed effects, motion-compensated frame-rate interpolation, and clips that are difficult to edit as possible reasons. These are options to assess, not guarantees that conversion will fix every issue.
- Before starting conversion, decide whether the project needs a replacement for every matching use of the source or only the selected, trimmed timeline clip. In the conversion dialog’s Advanced options, Use sub-clip converts the trimmed portion plus a little; the documentation says that only the currently selected instance is replaced when this option is used. Without it, avoid assuming the conversion is limited to the visible timeline trim.
- Choose the conversion scope and settings for the actual need. If an effect requires frame-by-frame access, intra-only conversion may be relevant. For detected VFR footage, Shotcut automatically sets the converted frame rate to the project’s Video Mode rate unless you override it. Treat that as a change to assess, not an assurance of a particular motion result.
Use this acceptance worksheet
The rows below are hypothetical diagnostic examples, not measured results or promises about Shotcut’s output. Record what you observe on a representative section after the chosen operation; use the observation to decide whether to continue with that route.
| Hypothetical observation | Route to consider | Acceptance question |
|---|---|---|
| A 4K clip drops frames during preview, but seeking reaches the expected frames and no speed effect is involved. | Proxy first. | Does preview become workable while the edit still shows the intended content? |
| A 30-second camera clip is identified as VFR, and a speed effect needs precise frame handling. | Consider full-clip conversion, or sub-clip conversion if only one trimmed timeline instance needs the change. | Does the selected instance behave as required through the speed-treated section? |
| Two uses of the same source need different treatments; only one has been trimmed for a speed experiment. | Consider Use sub-clip on the selected instance. | Is the other project use still the intended source, and did the selected instance receive the converted media? |
| An HDR source is the concern, not playback smoothness. | Evaluate conversion options for the intended color workflow. | Does the resulting image meet the project’s color requirements? Do not judge HDR handling from playback smoothness alone. |
Limits and what to try next
A proxy can conceal a source-media problem, including inaccurate frame-accurate seeking. If the speed-effect issue remains while using proxies, compare a short section of the original and a converted copy; this is an editorial diagnostic suggestion, not a documented guarantee. If conversion does not resolve the behavior, note the source’s frame rate, whether it is VFR, the selected conversion scope, and the effect settings before choosing another approach.
Conversion creates a new file and automatically replaces the project clip when the job finishes. The documentation calls the three quality choices visually lossless, notes that Good suits most applications, and says Best makes considerably larger files for only a slight quality improvement. These descriptions do not establish that every source or effect will produce the same result. If the wrong timeline use was replaced, stop and inspect the project’s clip instances before continuing; Use sub-clip is the documented option for limiting replacement to the selected trimmed instance.
Three quick questions
Will proxies make speed effects frame-accurate? They reduce playback workload; Shotcut warns that proxies can hide seeking problems. They do not promise a source-structure fix.
Does sub-clip conversion replace every use of the source? The documentation says only the currently selected instance is replaced when Use sub-clip is enabled.
Does conversion always improve editing performance? No such general guarantee is documented. Choose conversion for a specific media or processing need, and assess the result on a representative section.
Sources and next step
- Settings > Proxy Editing - Documentation - English - Shotcut Forum
- Convert to Edit-friendly Dialog - 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.