A line of text has to stay on screen long enough to be read, and the length of time that takes depends on the language and the reader. That sounds obvious until a localized video ships with a German headline that vanishes before anyone finishes it, because the template was timed around the English. The fix is not a separate template for every language. In Templater, it is a single rigged After Effects template that treats duration as something each data row decides, plus a small amount of discipline about where that decision lives.
This article is for a motion designer or video producer who has one design, several languages, and a spreadsheet of translations. We will cover what a reading-speed budget is, how to build timing into one Templater template so it adapts, and where the approach runs out of road. We will say clearly which parts come from our documentation and which parts are general practice, and we will not give you a number for how many words a person reads per second. We do not have a source we can stand behind, and the right figure depends on your audience.
What a reading-speed budget is, and why it breaks in translation
A reading-speed budget is the amount of time you allow a viewer to read a piece of text before it changes or leaves the frame. Every video with on-screen words has one, whether anyone wrote it down or not. A designer sets it by feel. They read the line aloud, add a beat, and move on. For a single-language project that works fine, because one person made one judgment about one line.
Translation breaks that judgment in three ways, and it helps to name them separately because each one needs a different answer.
The first is length. The same message takes more characters in some languages than in others. A headline that fit comfortably in two short lines may need three, or may need a smaller size. Longer text takes longer to read, so the hold time that suited the original is now too short. This is the problem most people see first.
The second is script and reading behavior. Some languages are written right to left. Some use characters that are denser or sparser than the Latin alphabet, and readers of different scripts take in a line differently. We are not going to guess at the details, because they vary by language and by audience, and a producer with a native reviewer will know more than a general rule can tell you. The practical consequence is that a budget that is right for one script may be wrong for another, even when the character count looks similar.
The third is context. A viewer on a phone with the sound off reads differently from a viewer in a lean-back setting with narration. A line that is a label is read faster than a sentence that carries the message. Translation does not change those facts, but it multiplies them, because now you have one template and several audiences.
So the budget is not a single number you can paste into a project. It is a relationship between how much text there is and how long it stays. A good template expresses that relationship once, and then lets each language fill it in.
Building duration into one template instead of branching
The word “branching” matters here, so let us define it. Branching means maintaining separate versions of a template, one per language or one per case, and choosing between them by hand or by a rule. It feels safe at first, because each version is simple. It becomes a burden quickly. A fix to the design has to be made in every branch, and branches drift. Four languages become four files that were once identical and no longer are.
Templater gives you a way to avoid most of that. You rig one composition so that the content layers are dynamic, you point them at a data source with one row per language or per variant, and you let layout and time rules adjust the composition around whatever arrives. Three documented capabilities do the work.
Layout rules. When Templater updates a composition with your data, it adjusts dynamic layers relative to their containing composition and to sibling layers. You do not hand-align or hand-scale the layers each time. When a German line runs longer than the English one, the layout responds according to the rules you set. This handles the length problem on the space axis, so that text which gets longer does not collide with the layer beside it.
Time Sculpting. This is the patented feature that lets you define rules for how layers respond to changes in the duration of other layers. You can crop, trim, shift, and stretch layers by rule. It is documented for the case where footage sources have varying duration. The design stays intact when the clip underneath is shorter or longer than the one you built the template around. This handles the length problem on the time axis, but with a limit we will get to.
International text support. You can insert characters from any language into your spreadsheet and they appear in your text layers. Templater reads the text as it appears in your spreadsheet, so commas, quotes, apostrophes, and new lines are accepted, and right-to-left scripts are supported. The one condition is that the installed fonts need the glyphs you require. A template that works in English and shows empty boxes in another script has failed on fonts, not on timing, and it is worth checking first.
There is a fourth capability that matters for typography. Templater’s dynamic text styling lets font-face and direction properties be controlled directly from a data source. If one language needs a different typeface or a different direction, that can be a column in the spreadsheet instead of a separate branch of the template.
Now put those together with a concrete case. Say you make a fifteen-second promo for a product launch, and it goes out in English, German, Arabic, and Japanese. The design has a headline, a sub-line, and a closing call to action over a background clip. In the spreadsheet, each language is a row. The columns hold the headline text, the sub-line, the call to action, the font choice, the text direction, and the path to a background clip.
The timing decision is where the interesting part lives. Instead of hard-coding how long each line holds, tie the timing to something that changes per row. The background clip is the natural candidate, because footage sources for dynamic layers can come from local or cloud-based locations and can be set per row. Prepare each language’s background so its length reflects the reading time that language needs, as judged by a native reviewer. Then Time Sculpting rules, set once, let the text layers and the closing card stretch, trim, or shift to follow the clip. The template carries one rule. The data carries the per-language answer.
That is language-aware timing without branching. Notice what changed. The reading-speed decision moved out of the template and into the data, where the person who knows the language can make it. The designer stops being the bottleneck for judgments that belong to someone else.
We want to be honest about the edge of this. Our documentation describes Time Sculpting in terms of layers responding to changes in the duration of other layers, with footage of different lengths as its stated use. It does not describe deriving a hold time automatically from how many characters a text layer contains. If you want text length itself to drive duration, you should test whether your rules deliver that behavior in your template and your version before you build a pipeline on it. A small batch and a preview will tell you in a few minutes. That is what the preview feature is for. You can iterate through previews of your render jobs and see how Templater treats different text, footage, and colors, and you can resolve problematic data before you render.
The spreadsheet itself deserves some design, because it is now carrying decisions that used to live in the timeline. A practical layout has one row per language and one column per thing that varies. Put the text in its own columns, one per line of copy. Put the typeface and direction in columns of their own, so a reviewer can see at a glance that the Arabic row is set to run right to left. Put the path to the background clip in a column, and name the clip files so the language is obvious from the file name. Add a notes column that nothing reads, where the native reviewer can write “hold longer” or “line two reads awkwardly” without touching the working columns. That is general practice for any multilingual sheet, and it keeps a producer, a translator, and a designer from overwriting each other.
Keep one rule firmly in mind. Data should hold values and the template should hold rules. If you find yourself encoding design logic into a cell, such as a column that says “use the second layout if the line is long,” stop and ask whether that belongs in the layout rules or in a deliberate project switch. A sheet full of design logic is branching in disguise, and it is harder to read than the branches you were trying to avoid.
Checking the result, and knowing when to branch anyway
A template that adapts is only good if you verify the adaptations. The failure mode is quiet. A line holds for exactly as long as it did in English, nobody notices, and a viewer in another market reads the first half. So build a check into the process.
Start with preview. Templater lets you preview compositions with your data before rendering or replicating. Run your full set of languages and look at the longest and shortest cases first, because the extremes are where timing fails. A native reader should look at the text, not only a designer. Our post on breaking language barriers with Templater covers the localization workflow in more detail, and our write-up on layout rules shows how the spatial side behaves.
Then use spot checks for quality assurance. Templater Pro and Bot offer a spot check feature that exports stills or short movie clips of chosen frames from data-merged compositions. You can specify frames by using named composition timeline markers, and otherwise Templater samples frames at even intervals. For timing, place markers where each line should be fully visible and fully readable, and the spot check will show you that frame for every language in one pass. We describe the technique in generating spot checks with Templater.
Finally, name your outputs sensibly. Templater lets you set a custom output file name for each render job from within your data source, so a reviewer can pull up the German file and the Arabic file without opening each one to find out which is which. It sounds minor, and it saves real time during review.
When should you branch anyway? Branching is the right call in a few honest situations. If two languages need a different structure, not just different timing, a single rigged composition may be harder to maintain than two. A language that needs a different number of lines, a different reading order, or a different layout idea is a design problem, not a timing problem. Templater can help here too, because it can switch between template projects on a per-row basis within the same data source. That gives you a controlled branch. Each variant lives in its own project, and the data still decides which one runs. It is branching with a switch you can see, which is a better kind than branching by hand.
Another case is subtitles. If your video carries spoken narration and the text on screen is a transcript, then timing is set by the audio and not by reading budgets in the abstract. Dataclay offers a Dynamic Subtitles Autograf rigging utility that automates the addition of subtitles, closed captions, and translations, and our post on setting up dynamic subtitles is the place to read about that. It is a different tool for a different timing problem.
There are also limits to what a template can know. Nothing in a spreadsheet tells Templater how fast your particular audience reads. A children’s channel, a legal disclosure, and a sports ticker all have different tolerances, and no piece of software can supply them. You can, and a reviewer who reads the language can. So the most reliable version of this approach has two ingredients. The template makes timing adjustable per row, and a person who reads the language sets it.
General practice is also worth following on the content side. Write shorter lines when you can, because a short line is a short line in every language and it relieves the budget problem before it starts. Leave breathing room at the end of a line, because translations tend to need it. Avoid putting a key message on screen for exactly as long as it takes to read once. Give the viewer a beat to take it in. And keep the same budget logic across a campaign, so the German and the Japanese versions of one video feel like they came from the same hand.
The bottom line is that one template can handle many languages if timing is data and not design. Use layout rules for space, Time Sculpting for the clips that carry duration, dynamic text styling for fonts and direction, and a per-row source for whatever sets the pace. Test the one thing our documentation does not promise, which is text length driving duration by itself, and check every language in preview and with spot checks. If a language needs a genuinely different structure, switch projects from the data and call it a branch you chose. The Templater page shows the full feature set, and the Time Sculpting post goes deeper on the technique.
Before you set up your own multilingual template, here are the questions we hear most about timing and translation.
Frequently Asked Questions
Can Templater set how long text stays on screen based on how much text there is?
Our documentation does not describe that behavior directly. Time Sculpting is documented as rules for how layers respond to changes in the duration of other layers, with footage of varying length as its stated use. If you want text length to drive duration, test it in your own template and version using the preview feature before building a pipeline around it. A small batch will show you the result in minutes.
Does Templater support right-to-left languages?
Yes. Templater reads text as it appears in your spreadsheet, so commas, quotes, apostrophes, and new lines are accepted, and right-to-left scripts are supported. You can also control font-face and direction properties from a data source using dynamic text styling. The condition is that your installed fonts must contain the glyphs you need, because missing glyphs show up as empty boxes regardless of timing.
Do I need a separate template for every language?
Usually not. You can rig one composition, put one language per row in your data source, and let layout rules and Time Sculpting adjust around the content. If a language needs a genuinely different structure, Templater can switch between template projects on a per-row basis within the same data source, so the data still decides which design runs. That is a controlled branch rather than a pile of manual copies.
How do I check that every language has enough reading time?
Use preview first, then spot checks. Templater lets you preview compositions with your data before rendering, so run all your languages and look at the longest and shortest first. The spot check feature in Templater Pro and Bot exports stills or short clips of chosen frames, and named composition timeline markers let you pick those frames. A native reader of each language should review the result.
What reading speed should I budget per language?
We do not publish a figure, because our documentation does not provide one and the right answer depends on the language, script, audience, and viewing context. A native reviewer for each language is the most reliable source. Build the template so timing is adjustable per row, then let that reviewer set it. Shorter source lines and a little breathing room at the end of each line help in every language.
Can the data source change fonts per language?
Yes. Templater’s dynamic text styling lets font-face and direction properties be controlled directly from a data source. That means a column in your spreadsheet can pick the typeface and text direction for each language row. Remember that the installed fonts need the glyphs the language requires, so install and test them on every machine that renders, not only on the design workstation.
What about subtitles with spoken narration?
That is a different timing problem, because the audio sets the pace. Dataclay offers a Dynamic Subtitles Autograf rigging utility that automates the addition of subtitles, closed captions, and translations. Our post on setting up dynamic subtitles in After Effects with Templater walks through it. Reading-speed budgets matter most when text is on screen without narration to pace it.
