When you enable proxies in a Shotcut project that is already open, treat locating and generating proxies as separate stages from loading them into the project. Shotcut automatically reopens the project to look for available proxies and may offer to generate missing ones. For those prompted batch jobs, completion alone does not mean the open project has switched its clips to the new proxies: after all jobs finish, reopen the project again to pick them up.
Decide which stage the project has reached
Use this sequence when Settings > Proxy > Use Proxy is enabled while the project is open:
- Record the starting state. Note which project is open and which clips currently show original-media information in Properties. This is your comparison point, not a claim that every clip must be eligible for a proxy.
- Allow the automatic reopen to finish. Shotcut says it reopens the project while locating proxies that already exist. It can take time; avoid treating the reload itself as a generation job.
- Separate lookup from creation. Shotcut searches for existing proxies, then prompts about generating proxies for eligible files that do not currently have them. Accept the prompt only if you intend to queue those jobs. Turning on proxy use does not, by itself, automatically generate each missing proxy at this stage.
- Watch the Jobs panel until the prompted jobs are done. The documentation distinguishes this batch workflow from a proxy job triggered when a file is added, which may use Replace when it completes. For the prompted jobs associated with enabling proxies in an open project, it explicitly says successful completion will not perform Replace.
- After all prompted jobs finish, reopen the project. This is the documented step for picking up the newly generated proxies. Do not infer that the earlier open timeline updated merely because the job queue is clear.
- Check a clip in Properties. For a video or image actually using a proxy, the panel displays (PROXY) next to its resolution. Treat that label as evidence for the selected clip, not as proof that every project asset has a proxy.
The Shotcut proxy-editing documentation describes the open-project sequence and why its batch jobs do not replace matching clips on completion. It also documents the Properties indicator.
Acceptance worksheet for a hypothetical project
The following observations are a hypothetical acceptance record, not a report of a software test or a guaranteed count. Record states rather than assuming the job total equals the number of timeline clips: eligibility depends on the documented rules, and the material does not define a count formula for a particular project.
| Checkpoint | Hypothetical observation | Decision |
|---|---|---|
| Before enabling | Timeline is open; selected clip shows a resolution without (PROXY) | Save this as the comparison state |
| First automatic reopen | Project reloads; existing proxy lookup occurs | Wait for the project to finish reopening |
| After lookup and prompt | Shotcut offers generation for files without proxies | Decide whether to queue the offered jobs |
| During queued jobs | Jobs panel still shows work in progress | Do not mark the timeline as proxy-loaded |
| Jobs complete, same session | Queue is clear; selected clip has not been checked after reopening | Generation is complete; loading is not yet accepted |
| After final reopen | Selected clip’s Properties shows (PROXY) beside resolution | Accept proxy use for that selected clip |
The label check is grounded in Shotcut’s description of Properties when a proxy is in use. As an author-recommended comparison, use the same identifiable clip before and after the final reopen, and record the displayed resolution and label. The documentation says that some other Properties fields continue to describe the clip rather than proxy; do not use those fields alone to decide whether proxy media is loaded.
Limits and next steps if the check fails
If the selected clip still lacks (PROXY) after reopening, the observation does not establish why. Check whether a proxy exists and whether that file is accessible, then review the project’s proxy storage locations: Shotcut says it looks in both the global and project proxy folders when opening a project. If no proxy exists, use the supported route for the situation: the open-project prompt for eligible missing files, or Properties > Proxy > Make Proxy for an individual clip. The latter forces generation and its job does a Replace operation, so it is not the same action as the prompted batch workflow.
Not every media item qualifies for automatic proxy generation. The documented exclusions include image sequences, files with an alpha channel, cover-art-only video, clips already having a proxy, and clips disabled for proxy in Properties; there is also a resolution threshold tied to preview scaling or 540 when scaling is off. If a clip is ineligible or proxy use remains unclear, check its Properties and the documentation rather than assuming the queue missed it. Shotcut also warns that proxy editing can conceal problems in source media, so a proxy indicator is not evidence that the original itself is free of playback or seeking issues.
Common questions
Does enabling proxies in an open project immediately generate every missing proxy? No. Shotcut reopens to locate existing proxies and then prompts about generating eligible missing ones; the enable action alone is not described as creating them automatically at that point.
If Jobs shows completion, has the timeline switched to the new proxies? Not for this prompted batch workflow. Reopen after all jobs are done, then check the selected clip’s Properties.
Does (PROXY) next to resolution confirm the whole project is using proxies? It confirms proxy use for the clip whose Properties you are viewing. Check other clips individually if you need to establish their state.
Sources and next step
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.