Avoid typewriter animation when revealing the text consumes time the viewer needs to read it, or when the subtitle is too long to reveal comfortably before it changes. Use character-by-character only for short text where the typing effect is intentional; consider word-by-word or line-by-line for larger units, and use normal display when the full wording needs to be available immediately. Judge the result on one timeline: subtitle duration, time when the complete text appears, and time left for reading.
Decide whether the reveal fits
Shotcut’s Subtitle Burn-In documentation describes three reveal modes: character by character, word by word, and line by line. It also says the rate is the number of frames between each character, word, or line appearance. A lower value reveals faster; a higher one reveals slower. The documentation recommends character-by-character animation for short subtitles and notes that word-by-word is generally easier to read. Treat those as design guidance, not a guarantee that a particular rate or mode will suit every caption.
For each cue, distinguish three moments: when the subtitle starts, when its last unit appears, and when the subtitle ends. Only the time after the last unit appears offers the viewer the complete text at once. That interval is not a universal reading-speed score, but it makes the tradeoff visible.
Use this sequence:
- Note the cue’s on-screen duration and whether it contains one line or several.
- Choose a reveal unit that suits the wording: characters for a deliberately typed short phrase, words for sequential chunks, or lines when a whole line should arrive together.
- Check the selected rate in frames per unit. Estimate the reveal span from the number of reveal events and frame interval, but confirm the actual completion point in Shotcut; do not assume undocumented counting details for spaces or punctuation.
- Compare that completion point with the cue’s end. If little time remains for the complete text, try a larger unit or disable the effect, then review the actual wording at playback size.
Do not respond to every tight cue by merely increasing the reveal speed. If the effect is not essential, normal display removes the reveal delay. If progressive appearance matters, increasing the unit from characters to words or lines can reduce the number of sequential events, but must still be checked against the shot and reading context.
Use a timing worksheet
The table is a hypothetical acceptance exercise, not a Shotcut test or a promised timing result. Assume a 30 fps project and the illustrative cues below. The rate shown is the documented frame interval; completion times are proposed observations to verify in the editor, not values derivable here. Record the real cue text and the point at which its final unit is visible.
| Hypothetical cue and duration | Reveal setting | Completion to inspect | Reading decision |
|---|---|---|---|
| “Wait.”, 2.0 s | Character, 4 frames per character | Is the full word visible early enough to leave a clear hold? | Keep only if the typing beat is intentional and the full word remains readable. |
| “Turn left at the next street”, 3.0 s | Word, 6 frames per word | Does the last word appear with enough time before the cue ends? | If the remaining hold is cramped, show the line at once or use line-by-line. |
| Two-line instruction, 2.5 s | Line, 8 frames per line | Does the second line arrive soon enough to understand the instruction as a whole? | If not, use normal display rather than just speeding up without review. |
For each actual cue, fill in the same fields: subtitle duration, reveal unit, frame interval, observed completion point, and final reading method. Review the rendered preview at its intended display size. This worksheet helps expose an insufficient hold; it does not establish a universal minimum reading time.
Know the limits and next step
The filter renders subtitles permanently into the image; viewers cannot turn them off after export, and the styling is fixed. The documentation explains the reveal controls but does not define a universal reading-time threshold or the exact counting behavior for every kind of text. Do not infer from the rate alone when a particular multilingual cue will finish. Observe the actual subtitle in the project and decide from the visible result.
If the final unit appears too late, first compare a larger reveal unit with normal display. If neither fits, reconsider the cue’s wording, segmentation, or screen duration with the editorial brief in mind. Do not silently remove required meaning to make an animation fit. Check that the final subtitle remains within the safe viewing area, as the documentation advises, and inspect the exported result because burned-in text cannot be disabled by the audience.
Common questions
Is word-by-word always easier to read? The documentation says it is generally easier than character-by-character animation. That does not establish that it is right for every cue; check whether each word arrives in time for the viewer to understand the complete message.
Should I use line-by-line for a long caption? It is a reasonable option when a complete line should appear as one unit, and Shotcut describes it as useful for long captions. Still inspect when the last line appears and how much of the cue remains.
What if the typing effect is important to the scene? Keep it only if the reveal and the remaining complete-text interval both suit the scene. If they conflict, consider changing the reveal unit or the cue timing with approval; otherwise use normal display.
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.