Opens in a new tab
Tutorial

After Effects Text From CSV

Published November 13, 2026

To get text into After Effects layers from a CSV, you map each column to a text layer by name, and let a tool read one row at a time into the composition. In our world that tool is Templater, and the one catch is that it reads tab-separated files, Google Sheets and JSON rather than a raw CSV, so a CSV takes one conversion step first.

It is worth saying that catch early. The rest of this guide covers what the mapping looks like, what happens when the text from row 40 is three times longer than the text from row 1, and how to set the data up so you are not debugging at midnight. If you only need a single title changed once, you do not need any of this. Double-click the text layer and type. Everything below is for the person who has a spreadsheet with a lot of rows and a template that has to come out looking right every time.

Three ways to get CSV text into a layer, and who each one is for

There are really three jobs hiding inside the phrase “text from CSV,” and they call for different tools.

The first job is one composition, one set of values, changed occasionally. After Effects can bring in a data file as footage, and an expression on a text layer can read a value out of it. This is general practice among motion designers and it works. It suits a lower third that reads from a short list, or a chart label you update by hand when the numbers change. It stops being pleasant when you need a finished video file for every row, because someone still has to step through the rows, render each one and name each file. It also puts logic inside an expression, and expressions are a good place for logic to go quiet and break later. We wrote about that failure mode in when an After Effects expression is too fragile to maintain.

The second job is many compositions, one per row, rendered in a batch. This is what Templater does. Every row in your data source is one render job. Every column is one dynamic element in the template. A cell can hold text, a URL, an image path or a hex color. The headline in row 1 becomes the headline of video 1, the headline in row 2 becomes video 2, and so on down the sheet. Templater Rig is the part that prepares the project, maps your data to layers and previews the result. Templater Pro adds Render and Replicate, which turn each row into a finished video. Templater Bot adds automation and command line control for when you want a system to feed it instead of a person.

The third job is a queue that several people or several machines share. That is the territory of Que, our companion app for job data. Its dashboard has a Batch Import that accepts a JSON file, an Excel file with a header row, or a CSV or TSV file. You pick the satellite that will process the jobs and the autograf that will use the data, and the rows appear as jobs in a campaign. So if your CSV is the thing you already have and your plan involves a queue, Que reads it directly. We cover that path in inserting a batch of jobs into Que from Excel, CSV or JSON.

This guide spends most of its time on the second job, because that is where the question “how do I get my text layers filled from a CSV” is hardest to answer well, and where the work is.

Wiring columns to text layers, step by step

Here is a scenario to hold in your head. The scenario is illustrative, not a customer story. A regional gym chain wants a weekly class-schedule video for each of its locations. The producer has a CSV with one row per class. The columns are className, instructor, startTime, location and tagline. She has one After Effects template with five text layers, and she needs a separate 1080 by 1080 video for each row so each studio can post its own.

Start with the template. In After Effects, build the composition the way you normally would, with placeholder text in each layer so you can see the design working. Then rename each text layer to match a column header exactly. The layer holding the class name becomes className. The one holding the instructor becomes instructor. Our support documentation is firm on two details here. You must rename the layer explicitly after you create it, even when the name Templater would have given it looks identical to the column header, because if you do not, Templater may not process the layer as dynamic. And keep spaces out of layer names, since the layer name has to correspond to a column name or a property key in your data source.

Next, apply the Templater Settings effect to each of those layers. You will find it under Effect, then Dataclay, then Templater Settings. Apply it once per layer. Applying it twice to the same layer gives you unexpected results, so if a layer misbehaves, open its effect stack and check for a duplicate before you look anywhere else.

That is the whole mapping. There is no field-by-field dialog and no script to write. The layer name is the connection. When Templater previews, renders or replicates, it matches each mapped layer to the column with the same name and fills it with the value in the current row. Our guide to data sources covers what each source type looks like in practice.

Now the data. This is where the CSV question gets answered honestly. Templater does not list CSV as a data source. What it reads is Google Sheets, a tab-separated value file, a plain text JSON file, a remote JSON feed, or a Que campaign. Our FAQ also says plainly that Templater cannot read an Excel workbook directly. You have to export it first to a tab-delimited file. A CSV sits in the same position. The practical route is to open the CSV in the spreadsheet app you already use and save or export it as tab-delimited text, or to paste it into a Google Sheet and point Templater at that. Both are simple, and neither changes your data.

Tool comparison

Templater vs. Que: which handles your CSV

Reads CSV directly?
TemplaterNo, convert to TSV or Google Sheets first
QueYes, Batch Import accepts CSV and TSV files
What drives the batch?
TemplaterOne render job per row in your data source
QueRows appear as jobs in a campaign
Who feeds it?
TemplaterA person maps data and previews the result
QueA system can feed it via automation and command line

Que’s Batch Import is the exception, since it takes CSV directly.

Layer mapping process

How to wire a CSV column to a text layer

  1. Build the templateBuild the composition the way you normally would, with placeholder text in each layer so you can see the design working.
  2. Rename each text layerRename the layer so it matches a column header exactly, with no spaces, even when the old name looks identical to the column header.
  3. Apply Templater Settings onceApply the Templater Settings effect to each of those layers, once per layer, found under Effect, then Dataclay, then Templater Settings.
  4. Convert the CSVOpen the CSV in the spreadsheet app you already use and save or export it as tab-delimited text, or paste it into a Google Sheet, saved as UTF-8.
  5. Preview the ugly rowsFind the longest class name, the shortest, the one with an apostrophe, the one in another script before you render.
Applying the Settings effect twice to the same layer gives unexpected results, check the effect stack first if a layer misbehaves.

Two details matter when you do that. The first is encoding. Our documentation says TSV and JSON files must be UTF-8 so that every international character survives. If your class names include accented letters or a language that is not English, a file saved in the wrong encoding is the first thing to suspect when the text in the video looks wrong. The second is the header row. The column headers are what Templater matches against layer names, and they are case-sensitive in the same way our reserved names are. If you are using Google Sheets as the source, our docs add a specific warning. Headers that begin with a numeral, contain spaces or contain a low-line character are not supported there. So startTime works, and start_time or 1st class will not.

One more setting to know about is the single-source rule. A Templater setup connects to one data source, and when that source is a Google Sheet it connects to a single worksheet. If your CSV has grown into three files for three studios, stack them into one sheet with a column for the studio. Do not expect Templater to merge them for you.

Finally, give every row an identity. A column named id is reserved and recommended, because Templater uses it to name each output. Without one, it falls back to the row’s position in the sheet. A column named output overrides id for naming, and if the output cell is blank, id is used. For the gym chain, an id like downtown-spin-0900 means that the file list afterward tells you exactly which video is which. Our guide to custom output file names goes further on that.

When the text does not fit

The mapping is the easy part. The part that decides whether your batch is usable is what happens when real text meets a design that was built around a placeholder.

Real data is uneven. In our gym sheet, one class is called “Spin” and another is “Sunrise Strength and Mobility for Beginners and Returners.” The shorter one looks fine. The longer one runs off the side of the frame, or wraps into the next element, or collides with the instructor’s name. A first batch that comes back looking wrong often traces to this, and it is a design problem, not a data problem. Fixing the data hides it for a row or two. Fixing the layout solves it for every row.

Templater has layout rules for this. When the layers in your project receive new data, their size, alignment or position may need adjusting, and the rules let you say how. The Templater Settings effect carries the parameters. A Scale Factor value, for example, resizes a layer to a percentage of its parent composition’s dimensions, so you can force a headline to fit inside 90 percent of the frame width whatever its length. You can also pin a layer to a corner or edge of its composition. In the same composition, a different layer can follow different rules, so the tagline can sit at the bottom left while the class name sits at the top.

There is one limit that our documentation states. Layout rules do not function correctly on layer properties that have Separate Dimensions turned on. If a layer refuses to scale the way you expect, check that first.

Relationships between layers matter as much as sizes. Suppose a small logo sits to the right of the instructor’s name. When the name gets longer, the logo has to move, or it will end up sitting on top of the last letters. You solve this by applying the Settings effect to the logo layer and attaching it to the text layer. You choose which edge or corner of the text layer it attaches to, and Templater moves the logo as the text width changes. We walk through that in how to make a graphic follow a changing text layer.

Language is the other place where text surprises people. If your CSV includes rows in more than one language, Templater can style the text per row. You add a second column named after the text layer with the suffix @style, so the class name layer gets a className@style column. In that cell you can set the font by its PostScript name, the text direction and the justification. This needs Templater 3.4 or later. The behavior around fonts is worth knowing before a batch, because it is not forgiving in one case. If you specify a font that is installed but does not include the characters for that row’s language, Templater does not import the text, and nothing appears in the composition for that row. If you specify a font that is not installed, Windows falls back to a default font and macOS gives unexpected results. If you leave the style cell blank, the text uses your defaults from Templater Preferences. Details are in dynamic text styling.

Watch for commas inside a field, which are a classic way to break a column in a CSV. Check how the app that converts your file handles them, and open the converted file to confirm each cell holds what you expect before you point Templater at it.

The safest habit is to preview before you render. Templater’s preview has a manual mode that steps you through rows one at a time and a cycle mode that runs through a range on its own. It re-reads your data source every time you preview and does not cache, which means an edit you just made in the sheet shows up on the next preview. Keep the range small while you are checking, because previewing a short range is faster. Then go looking for your worst rows on purpose. Find the longest class name, the shortest, the one with an apostrophe, the one in another script. Our guide to preview modes and spot checks explains how to sample a big batch without watching every video.

Keeping the sheet clean so the batch does not surprise you

A good template and a messy CSV still produce a bad batch. A few habits keep the sheet from causing trouble, and most of them are common sense you would apply to any data that feeds a design.

Start by checking the reserved words. Templater reserves a handful of column names for its own use: id, target, output, aep, render-status, bot, module and render-settings. They are case-sensitive, and our documentation warns that using one of them as a dynamic layer name can cause an error. If your CSV came from another system, scan its headers against that list before you rename a single layer. A column called id is fine and encouraged. A text layer named target is asking for trouble.

Reserved column names

Column names Templater reserves for its own use

Column name What it controls Safe to use as a layer name?
id Names each output file; falls back to row position if absent Yes, encouraged
output Overrides id for file naming; id used when cell is blank No, reserved
aep Switches project files per row No, reserved
target Reserved by Templater No, causes an error
render-settings Reserved by Templater No, reserved

Then read the data the way a viewer will. General practice for any data-driven design is to look for the things a spreadsheet hides from you. Stray spaces at the start or end of a cell, a blank where a value should be, a name typed in all capitals in one row and lowercase in the next, a character that looks like a hyphen but is something else. None of these are errors to the software. They are all visible errors to the person watching the video. A quick scan of the sheet in the app that made the CSV costs minutes, and a batch you have to throw away costs a lot more.

Decide what a blank means before you hit render. If a tagline is missing in row 14, do you want an empty space, a default line or a skipped job? Templater will do what the layout rules and your data tell it, and that may not be what you meant. A cleaner approach is to make the sheet complete. Put the default text in the cell yourself so the choice is visible in the data.

Treat numbers and dates as text. Everything Templater reads from a source arrives as a string, which our documentation says directly in the context of expressions. If you want a date to read “Saturday, 9:00 AM” on screen, put exactly that in the cell. If an expression on your layer needs to do arithmetic on a value, cast the string to a number inside the expression. Our guide to using Templater data in After Effects expressions covers the pattern.

Last, test with a small file. A short run of five or six rows that includes your longest, shortest and strangest values will tell you more than a full pass of the sheet. Dataclay offers a free 30-day trial of Templater with all features included, and the trial adds a watermark to dynamic layers. That makes it a safe place to confirm that your layer names, your headers and your layout rules all agree before you commit machine time.

Before you render

Sheet habits that prevent a bad batch

  • Scan column headers against Templater’s reserved words: id, target, output, aep, render-status, bot, module and render-settings
  • Check for stray spaces, blank cells, and inconsistent capitalization a viewer will see
  • Decide what a blank cell means and put the default text in the cell yourself
  • Save TSV and JSON files as UTF-8 so every international character survives
  • Test with five or six rows that include your longest, shortest and strangest values before a full pass

Where this approach is the wrong fit

It is fair to say who should not use this. If you are changing a few words in one comp, an expression reading a small data file, or even your own hands, will be faster than rigging a template. If your text has to be generated or rewritten by a language model for each row, Templater is not the writing tool, though it will render whatever text lands in your sheet. And if your CSV changes every minute and has to flow into video with no person involved, you are in Bot and Que territory, which is a bigger design than filling text layers, and worth planning on its own.

The other honest limit is the file format. If your pipeline emits CSV and cannot be changed, you will carry a conversion step to tab-delimited text or to Google Sheets. That is a small cost, and it is a real one. Que’s Batch Import is the exception, since it takes CSV directly.

So here is the bottom line. Getting text from a CSV into After Effects layers comes down to three rules. Name each text layer exactly like its column header and apply the Settings effect once. Convert the CSV to a source Templater reads, and save it as UTF-8. Then design for your longest row, not your first one, and preview the ugly rows before you render. Do those three things and a spreadsheet with hundreds of rows turns into hundreds of finished videos without anyone retyping a word.

We covered a lot of ground up there, so here are answers to common questions about connecting a CSV and a template.

Frequently Asked Questions

Can Templater read a CSV file directly?

Not as a Templater data source. The data sources we list are Google Sheets, tab-separated value files, plain text JSON files, remote JSON feeds and Que campaigns. The simplest route is to open your CSV in a spreadsheet app and save it as tab-delimited text, or paste it into a Google Sheet. Que is different. Its dashboard Batch Import accepts CSV and TSV files, along with JSON and Excel files that have a header row.

How do I connect a column to a text layer?

Rename the text layer so it matches the column header exactly, with no spaces, then apply the Templater Settings effect to it once. The layer name is the link. If you skip the explicit rename, even when the old name looks identical, Templater may not treat the layer as dynamic. When you preview, render or replicate, each mapped layer is filled with the value from the current row.

Why is my text not showing up for some rows?

Check fonts first if you use a style column. When a row names a font that is installed but does not contain the characters for that row’s language, Templater does not import the text, so nothing appears. Also confirm the layer was renamed explicitly, the header matches the layer name, and the Settings effect is on the layer only once. A reserved column name used as a layer name can also cause errors.

What happens when a row has much longer text than the others?

The text may overflow your design unless you set layout rules. Templater Settings lets you scale a layer to a percentage of its composition and align it to an edge or corner, and you can attach other layers to a text layer so they move as its width changes. Rules do not work correctly on properties with Separate Dimensions turned on. Preview your longest row before rendering.

Do I need a special file encoding for non-English text?

Yes. Our documentation says tab-separated and JSON files must be UTF-8 so Templater can read international characters. Templater accepts text from any language, including right-to-left scripts, as long as the font you use has the glyphs. For per-row fonts or text direction, add a style column named after the layer with the suffix @style, which needs Templater 3.4 or later.

Can I use more than one CSV or sheet tab at once?

A Templater setup uses a single data source, and with Google Sheets it uses a single worksheet. If your data is split across several files, combine it into one sheet, adding a column that says which location or version each row belongs to. You can also switch project files per row with the reserved aep column, which keeps different templates in one sheet.

How do I name the output files from my CSV rows?

Add an id column with a unique value for each row, or an output column if you want full control over the file name. When both exist, output wins for naming. If the output cell is blank, Templater uses the id. If neither exists, it falls back to the row’s position in the sheet, which makes the files harder to match back to your data.

Leave the first comment

Sign up

Stay up to date with Datclay's newsletter. We won't spam your inbox.

Newsletter Signup
Name
Name
First
Last

By submitting your email, you agree to our Terms and Privacy Policy. You can opt out at any time.