If a style is only for one subtitle file, create it within that file; if you need it available across files, create it in the global space. Use ASS override tags for a different task: styling part of a subtitle’s text. In Kdenlive, those choices are managed in the Subtitle Manager, but a global style’s availability should not be mistaken for proof that another subtitle file uses it.
Decide the scope and set it up
Use the Styles section of the Subtitle Manager, opened from Sequence > Subtitles > Manage Subtitles > Styles. The official subtitle styling guide describes styles stored within an individual subtitle file or in the global space, and explains how to assign a style to the subtitle being edited.
Choose the location based on the intended handoff:
- One project, one subtitle file: Select that file in the sidebar before creating the style. This keeps the style associated with that file rather than making it a shared resource.
- Several subtitle files need the same reusable style: Select the global space before adding the style. This makes it available globally; it does not, by itself, assign that style to every subtitle.
- A single phrase needs emphasis: Keep the subtitle’s ordinary assigned style, then use an ASS override tag on the relevant text. Kdenlive’s text editor buttons can add or edit tags. A tag such as
Toggle Boldaffects text at or after the insertion point, or wraps selected text; it is not the same as changing the style assigned to the whole subtitle.
After choosing the sidebar location, click + Add Style and set the properties in the Style editor. To change where an existing style is stored, drag it onto the intended sidebar item. The documentation says this operation can move or copy the style; follow the interface’s result and check the destination rather than assuming a drag always leaves the original in place. Then select a subtitle and choose the intended style in the Subtitle Window’s Style combobox. The style applies to the entire subtitle.
Acceptance worksheet: three hypothetical handoffs
The table is an author-proposed review aid, not a report of a software test. Its observations are hypothetical; replace them with what the project actually shows.
| Hypothetical need | Example observation to record | Decision and handoff check |
|---|---|---|
| One-off file, “Festival-en” | The sidebar shows the style under that subtitle file; one cue is assigned to it. | Keep it file-level; check that the receiving editor has the subtitle file and that the cue still selects the intended style. |
| Shared style, “House Sans” | Two subtitle files are listed, but only one checked cue currently selects “House Sans.” | Keep a global copy if both files need access; inspect a cue in each file and record its assigned style separately. |
| One phrase emphasized, “IMPORTANT” | The cue’s assigned style is “House Sans”; an ASS tag surrounds only the word in the text. | Treat this as local emphasis, not a second file-wide style; inspect the tagged text and the surrounding words. |
For each delivery, record the style’s sidebar location, the subtitle file and cue checked, the assigned style, and whether any local tags are intentional. This catches a common handoff gap: a style exists in the project, yet the relevant cue has not been assigned it.
Limits and what to do next
The official subtitle documentation states that the style named Default cannot be moved or deleted. If it will not move, choose another style to relocate or create a separate one. The documentation also describes \r<style> as a way to reset style after a tag; do not treat that syntax as interchangeable with choosing a style in the combobox.
If the result differs from the worksheet, first inspect the style’s actual sidebar location and the cue’s Style selection. If those are correct but the appearance still differs, inspect the ASS tags in the text: a local override may affect only part of the subtitle. Kdenlive’s Simple editor hides ASS tag blocks, and its documentation cautions that style editing there can behave unpredictably in some cases. Switch to the normal subtitle editor for tag-aware inspection. If the delivery is meant to be a standalone subtitle file, confirm the exported format separately: the documented export choices are ASS and SRT, and the guide does not claim that every style or override is preserved identically in both.
Three quick questions
Does a global style automatically update every subtitle? The documentation says styles can be global and that a style is assigned to the subtitle being edited. Check the assignment in each file; global availability is not the same as automatic assignment.
Should I create a second style for one bold word? Usually not if the rest of the cue should retain its existing style. Use an ASS override for the selected text, then inspect the surrounding text for unintended effects.
Can I move the Default style to a subtitle file? No. The documented limitation is that Default cannot be moved or deleted. Create another style for a file-level or global use instead.
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.