Saving caption colours and borders does not also save a scene sequence. The inspected format reuses formatting and frame dimensions; it does not define where replacement photographs or videos belong in a finished sequence. The word template needs that distinction.
A template-comparison request led to Rust source, the comparison guide and aggregate records of earlier output tests. The explanation below is limited to the fields and application paths inspected at that time. I did not run the original editor, media or renderer, or freshly review the screen and sound.
Begin with the fields the file actually stores
The inspected built-ins are documentary, news information, vertical short, advertising title and simple interview: five named presets. Their application function resets the global caption style, then adjusts such values as size, color, alignment, background box and border. The vertical preset also changes the frame dimensions.
The serialized Template contains schema, style, frame_width, frame_color, width and height. It reuses caption formatting, the outer border and frame dimensions. Its fields do not include scenes, source media, music, transitions, keyframes or replaceable slots. A feature or asset existing in the editing project does not establish that this file stores it.
A news label therefore does not supply a news opening or story sequence. An advertising title does not provide a complete arrangement with replaceable product photographs, prices and enquiry copy. Formatting preset was the more precise description of the inspected saved scope.
Per-clip formatting can take precedence over the global style
If existing text keeps its color after the global caption color changes, the button connection and style precedence need separate checks. The inspected ASS writer chooses clip.caption_style as its base when present, falling back to the project style otherwise. Changing only the global style does not overwrite every per-clip caption color.
A historical report of test material owned by the project records yellow text pixels with a mint global style and a yellow clip style, then mint pixels after the clip style was removed. The report explicitly says the probe did not call the built-in apply function. It supports the renderer’s precedence at that time, not a template-button click or a new output test in this writing run.
Selecting the base style is not the last source of formatting. Character-range emphasis and the karaoke path can insert their own colors. I therefore do not claim that every character follows the global color whenever a clip lacks a local style. Identify whether the intended change concerns the project, clip or character range.
Applying the vertical preset and loading a file take different paths
Preserving a local style also needs a field-by-field explanation. The vertical preset calls Project.resize with 1080×1920. That function scales values including existing clip-caption, character-range and title sizes. The precedence of a local color does not mean every local formatting value remains unchanged.
Loading a saved style file instead assigns its dimensions, global style and border to a project copy, validates the copy and commits it. This path does not call resize. Reaching the same frame dimensions can therefore involve different treatment of existing titles and individual text sizes.
Actual material and output are needed to determine the visible effect. Inspecting a path that skips scaling is not proof that every layout breaks. A later review can check title safe areas, long-caption readability and retained emphasis after switching orientation. Those are outstanding observations, not results of this source review.
A scene template needs replacement conditions
The next design proposal involves more than adding names to the style file. It would retain scene order and duration, tracks, transitions, music and replaceable material. A space-introduction sequence might define places for a leading video, detail photographs and a closing message. That is an illustrative proposal, not a template implemented or rendered in this run.
A slot also needs to state whether it accepts an image or video, the required duration and aspect ratio. A short video needs a policy: reject it, repeat it or hold its last frame. Without those conditions, replacing a file can change timing and composition in ways the recipient cannot anticipate.
CapCut’s official help likewise describes creators marking replaceable clips for users to substitute their own material. I use that documented, platform-specific workflow for comparison. It does not establish the same capabilities or library on an installed desktop app or account. A count of preset names cannot compare these different forms of reuse.
Source: CapCut Help, How to Set Replaceable Material Clips.
A documented replacement workflow, not a fresh test of installed-app or account capabilities.
Show the preview and application scope before selection
The inspected UI code offers named buttons for the built-ins and connections for saving and opening the current format. Those connections do not establish a per-template thumbnail, playback example or required media count. As similarly named presets accumulate, a person needs to see what will change before applying one.
A scene-template chooser could show total duration, aspect ratio, the number and types of replacement assets, and editable copy. A formatting preset could state whether it changes only global defaults, overwrites selected clips or preserves their local styles. These are proposed selection details, not features claimed to exist in the current chooser.
An earlier website case found matching template names attached to different structures. In this editor, the distinction is saved formatting versus a scene sequence. First define which values are reused and which material can be replaced; then specify the preview evidence and originals to preserve.
Valid project data does not establish a well-finished film
The built-in test definition applies each preset to a fresh default project and validates the resulting project data. I read a historical report of that check passing and a separate aggregate output record. Default-project validation does not test every long caption, aspect ratio, music track, transition or design decision.
This article draws on selected source, guides and historical aggregate results. I did not open the original media or output-video pixels, run a GPU render, play audio or click through the interface. Color detection in an internal output record remains distinct from a person reviewing legibility on screen.
Use the following list to record another editor’s saved format and review scope. State which values the formatting preset changes. Present a scene template as a separate result once its replacement conditions and verification evidence exist.
- List stored global formatting and scenes or media excluded from the file.
- Separate project, clip and character-range precedence from the intended application scope.
- Check how resizing and file loading handle existing text and titles.
- Specify scene-slot media types, duration, fit, music and replacement conditions.
- Retain separate results for data validation, internal output, screen review and listening.