Opens in a new tab
Guide

Excel File to Video: One Video per Row

Published November 13, 2026

An Excel file turns into videos when each row becomes one render job and each column feeds one layer in an After Effects template. Dataclay gives you two ways to do that, and which one you pick depends on whether the person running the batch sits inside After Effects or inside a web dashboard.

This guide is for the producer, agency lead or marketer who already has the spreadsheet. Maybe it is a list of a few hundred sales reps, each with a name, a region, a headshot link and a quarterly result. Maybe it is a list of event honorees or customers. The design is done or nearly done. The question is how to get from the file on your desktop to a folder of finished videos without retyping a single name. We will cover the two routes, how to shape the sheet so every row survives, and how to run the batch without learning about a bad row on hour six.

Two routes from an Excel file to finished video

Start with the honest limit. Templater, our After Effects plugin, does not read an Excel workbook directly. Our FAQ says so plainly: you must first export the Excel data to a tab-delimited file. That is a small step, and it is the one people skip and then wonder why their text looks strange. We will come back to it.

The second route skips the export. Que, our companion for automation, accepts an Excel file with a header row straight into a campaign through the Que Dashboard. It also takes CSV, TSV, and a JSON file that holds one array of objects. If your team would rather drop a file in a browser than sit at an After Effects workstation, that is the shorter path.

Here is how the two compare in practice.

Route one: export to a tab-separated file and use Templater. You rig the template in After Effects, point Templater at the exported file as its data source, and work through the rows. A data source in Templater is just a table where each row is a render job and each column is a dynamic layer. Cells hold text, URLs, image file paths or hex color values. Pick this route when a motion designer owns the project, when you want to preview rows inside After Effects while you tune the layout, or when the batch is a one-off that someone will start by hand. We cover the data source idea in more depth in what a data source is in Templater.

Route two: upload the Excel file to Que. In the Que Dashboard you open the campaign that will hold the jobs, choose Batch Import, drop in the file, pick the satellite that will process the jobs and the autograf that will use the data, then click Upload. When the import finishes, every row shows up as a job in the campaign. A satellite is a machine running Templater that does the rendering. An autograf is a rigged template registered with Que. Pick this route when the person starting the batch is not the person who built the template, or when you want a dashboard that shows each job moving through its states. The click path is spelled out in inserting a batch of jobs into Que.

Que Dashboard Upload

How to import an Excel file into Que

  1. Open the campaignOpen the campaign that will hold the jobs.
  2. Choose Batch ImportChoose Batch Import in the Que Dashboard.
  3. Drop in the fileDrop in the Excel file with a header row.
  4. Pick satellite and autografPick the satellite that will process the jobs and the autograf that will use the data.
  5. Click UploadWhen the import finishes, every row shows up as a job in the campaign.
Every row appears as a job in the campaign once the import finishes.

There is a third door for developers. Que has an Import Jobs endpoint in its API, so a script or your own app can push many jobs into a campaign without anyone opening the dashboard. If an Excel file is only the first stop and the real goal is a repeatable pipeline, that endpoint is where you end up. It is outside the scope of this page, but it is good to know the file upload is a convenience and not the only way in.

Neither route is better in general. Templater with a tab-separated file gives the designer the most control and the fastest feedback loop. Que gives the producer the fewest steps and the best view of progress. Some teams use both: the designer builds and previews in After Effects, then the team feeds the production batch through Que. If you are choosing between the two products for a whole pipeline, Que versus Templater goes deeper.

Two Routes

Templater vs. Que for Excel batches

File input
TemplaterTab-delimited export required
QueExcel file uploaded directly
Who runs it
TemplaterMotion designer at After Effects
QueProducer in a web dashboard
Best for
TemplaterOne-off batch, preview while tuning
QueTeam where builder ≠ batch starter

Some teams use both: the designer builds and previews in After Effects, then the team feeds the production batch through Que.

One more note on editions. Templater comes in Rig, Pro and Bot. Rig sets up the template. Pro processes batches. Bot automates the whole workflow. For an Excel batch that you start yourself, Pro is the role you want. The free trial contains all features for all versions, with a watermark added to dynamic layers, so you can run your real file through it before you decide anything.

Shape the sheet so every row renders

Many failed batches trace back to the spreadsheet, not the template. The design was fine. Row 212 had a path that pointed nowhere, or a name with a character the file could not hold. A little discipline in the sheet saves a lot of grief later.

One row, one video. One column, one layer. This is the whole mental model. Templater maps data by matching a layer name in your After Effects project to a column header. A layer called headline receives whatever is in the headline column on that row. So the header text has to match the layer name exactly. Rename a column after the template is built and the layer goes quiet. Our own advice on Google Sheets is to avoid headers that begin with a numeral, contain spaces or contain the _ character, and the same habit helps in any spreadsheet: short, plain, one word where you can manage it.

Know the reserved columns. Templater sets aside a few column names for its own use, and column names are case-sensitive. If you use one as a layer name, you can cause an error in processing. The ones that matter for an Excel batch are these.

  • id labels each row with your own identifier. If you leave it out, Templater uses the row index. We recommend you set it.
  • output sets the output file name for each job. If you leave it out, Templater devises a name for you.
  • target names the composition to render. If the column is missing or the name is not found, Templater uses the default target composition.
  • aep switches the project file row by row, using absolute file paths. That lets one sheet drive several templates.
  • render-status is required for Bot, and it tracks whether a row is ready, queued, processing or done.
  • module and render-settings pick the output module and render settings template, and their values are case-sensitive.

For a first batch you only need id and output. Think about output names before you think about anything else, because the file name is how a human finds the right video afterward. If both columns exist, the output value wins over the id value for naming. If neither exists, you get index numbers, which tell you nothing in a folder of three hundred files. Our guide to custom output file names shows the patterns.

Reserved Columns

Templater reserved column names and their roles

Column What it does Required?
id Labels each row with your identifier Recommended
output Sets the output file name per job Recommended
target Names the composition to render Optional
aep Switches project file row by row Optional
render-status Tracks row state for Bot Required for Bot only

Make every name unique. This is not just tidiness. When a run is fully automated, the Bot overwrites existing files if two rows resolve to the same output name. Two reps named Sam in the same region, with only a first name in the output column, means one video silently replaces the other. Put a unique id in each row and you will never have to debug that.

Put the right thing in each cell. Text goes into text layers. Image columns hold a URL or a file path. Color columns hold a hex value. Because a cell is only a string, mistakes slip through quietly. A phone number that Excel reformatted into scientific notation is still a string, just a wrong one. A date that Excel converted to a serial number is still a string, just not the one you meant. Look at the exported file in a plain text editor before you trust it. We wrote about the mismatches that cause trouble in field type mismatches between data sources.

Export correctly if you take route one. Save the sheet as a tab-delimited text file. Two details trip people up. First, the file must be UTF-8, because that is what lets Templater read accented letters, non-Latin scripts and other international characters. Second, Templater Preferences has a checkbox for tab-delimited files exported from Excel or Numbers. Our troubleshooting notes say that when unintended characters appear in dynamic text layers, the cause is either that this box was not checked for a file that came from Excel, or that it was checked for a file that did not. Check the box only when the file really came from those programs.

Before You Batch

Shape your sheet so every row renders

  • Match each column header exactly to its layer name in After Effects
  • Give every row a unique value in the id column
  • Set a readable output name for each row
  • Save the tab-delimited file as UTF-8
  • Check the Excel and Numbers checkbox in Templater Preferences only when the file came from Excel or Numbers
  • Preview the longest and shortest entries before running the full range

Mind multi-line text. If a cell holds a message with a line break, the After Effects text layer has to be a multi-line text box, which you create by click-and-dragging with the Text tool. A layer made by a single click is a single-line box and will not show the break. Use your spreadsheet application’s own method to make the line break inside the cell.

One worksheet only. Templater maps data to a single worksheet, and more generally pulls from a single data source. If your workbook has a tab per region, merge them into one sheet with a region column. That column is often useful anyway, because you can then drive the headline or the color from it.

Keep asset references in the project. When a run fails with a message like “Failed at N/A,” it usually means After Effects did not find an asset, a footage file or a font where the project expects it. For a sheet that points at headshots, that means every path in the image column has to resolve from the machine doing the rendering. If you render through Que, the assets, fonts and plugins the template needs must exist on each satellite, because the satellite is the machine that actually opens the project.

Mind the header row. The first row of the sheet is the header, which is the one row that does not become a video. This matters when you set the range later. For a tab-delimited file, the start row must be greater than 1, because row 1 is the header. Que’s Excel import also expects a header row.

That is the discipline. It reads like a lot, but it is really three habits: match the header to the layer, give every row a unique name, and look at the file before the machine does.

Run the batch without finding the bad row at the end

You can start the full file right away. Please do not. A batch is only as safe as the test you ran before it.

Preview inside After Effects. Templater can preview the target composition with your data in it, and it re-reads the data source every time you preview. You can step through rows one at a time with the arrow icons and watch the dynamic layers update, or you can set a range and let it cycle through automatically. Keep the range small while you work, because a small range makes each preview faster. One catch: in cycle mode, Templater reads the data source once before it starts. If you fix a cell in the file while cycling, you will not see the fix until you start again. Our write-up of preview modes and spot checks covers this.

Previewing is where you find the rows that stress the design. The longest name. The shortest. The one with a very long region. Templater’s layout rules resize and reposition dynamic layers relative to the composition and to each other, but you still want to see the extremes yourself before you trust them.

Render a canary row first. Pick one ordinary row and one ugly row and run only those two. Look at the actual files, not just the preview. Check the name, the image, the text fit and the file name. A canary row that fails costs you a minute. The same failure in the middle of the full run costs you an afternoon. We explain how to choose one in designing a canary row.

Set the range, then choose Render or Replicate. In the Templater panel, under Transport, you enter the range of rows that the batch should process. After that you pick how the batch runs. Render produces finished files with the least handling. Replicate inserts the data and saves a copy of the project for each version, so you can send the copies to the After Effects render queue or to Adobe Media Encoder. Choose Replicate when you want to touch a few versions by hand before they render. We lay out the full set of choices in how to render versioned video in a batch.

Or hand it to Que. If you took the upload route, the imported rows sit in the campaign as jobs. Each job moves through a set of states. A job is ready when it has all its data. It is queued while it waits for its satellite. It is processing while Templater versions and renders it. It is done when the render completes. It is canceled if someone stops it, and an error code appears if something fails along the way. A new job with no status is set to ready, and a job that does not name a satellite takes the campaign’s default satellite. A campaign also has a default autograf. Those defaults are handy, and they are also a reason to check the campaign settings before you click Upload. If you want the meaning of each state and what to do next, see Que job states.

Plan for the time. Render time depends on the length of the video, the resolution, the hardware, how much of the video is dynamic versus static, how heavy the effects are, and how the template was built. We cannot give you a number without seeing your template. What we suggest instead is a pre-flight: render one similar video on a comparable machine and multiply by the number of rows. More machines running at once shorten the total. Projector, our rendering companion, renders several videos at the same time on one machine, using the cores it has.

Keep the file next to the finished videos. When a viewer or a client says “the video for Dana in the Northeast region has a typo,” you want to open the exact row that made it. Save the sheet you actually ran, with its id column, in the same project folder as the output. That is the audit trail. It also makes the second run easy. Fix the row and render it again.

When an Excel file is the wrong starting point

Excel is a fine source for a batch you can see all at once. It is a weaker source in three situations.

The first is when the data lives somewhere else and the Excel file is only a copy. If the rows come out of a CRM every week, an exported file is already stale the moment you save it. A direct feed of the data is a better fit than a file someone re-exports by hand. We describe that case in personalized video from a CRM export.

The second is when several people edit the file at once. Templater can read a native Google Sheets document, which suits a team where producers fix cells while the batch is being planned. An Excel file on one desktop does not give you that. The trade-off is that a Google Sheet has its own header rules, as we noted above.

The third is when the batch must start the moment a new row appears. That is Bot territory, and it needs a render-status column and a data source the Bot can watch. A file that a person emails around is the opposite of that.

It is also worth asking whether the video should be a template at all. A template-driven video is the right tool when every video follows one design and only the data changes. If every video needs its own creative decisions, no spreadsheet will help, and you are better off with a designer and a deadline.

So here is the bottom line. If you have an Excel file and a finished template, you are close. Export it as a UTF-8 tab-delimited file and run it in Templater, or upload it directly to a Que campaign. Give each row a unique id and a readable output name. Preview the extremes, render a canary row, then set the range and go. The routes are easy. The discipline in the sheet is where the batch is won or lost.

We covered a lot above. Here are the questions people ask us most when they bring us a spreadsheet.

Frequently Asked Questions

Can Templater read an Excel file directly?

No, not directly. Templater needs the Excel data exported first to a tab-delimited file, which it reads as a data source. Save the sheet as tab-delimited text with UTF-8 encoding so international characters survive, and check the Excel and Numbers checkbox in Templater Preferences only when the file came from one of those programs. If you would rather not export at all, Que accepts an Excel file with a header row through its Batch Import dialog in the Que Dashboard.

What file types can I import into a Que campaign?

The Que Dashboard accepts a JSON file that contains a single array of objects, a Microsoft Excel file with a header row, a comma-separated file, or a tab-separated file. You choose the campaign, click Batch Import, select or drag in the file, pick the satellite that will process the jobs and the autograf that will use the data, and click Upload. Each row then appears as a job in the campaign’s job listing.

Which columns does my Excel sheet need?

Only the columns that match your layers, plus whatever you want for control. Templater reserves a few names: id, output, target, aep, render-status, bot, module and render-settings. For a first batch we recommend id and output so each video has a name you can find. Render-status is required only if you use Bot. Column names are case-sensitive, so keep them exact.

Why do strange characters show up in my text layers?

The usual cause is the tab-delimited file and the Templater Preferences checkbox disagreeing. If the file was exported from Excel or Numbers and the Excel or Numbers checkbox is not checked, odd characters appear. The reverse mistake does the same thing: the box is checked for a file that did not come from those programs. Also confirm the file is saved as UTF-8, then preview the row again.

How do I keep one video from overwriting another?

Give every row a unique value in the id or output column. When both exist, the output value is used for naming. The Bot overwrites files that resolve to the same output name, so two rows with the same output value will leave you with one file instead of two. Combine a name with an id, such as the person and a row number, and every output stays distinct.

Can one Excel workbook feed several templates?

Yes, with some care. Templater can only map data to a single worksheet, so merge your tabs into one sheet first. Then add an aep column holding the absolute path of the project file for each row, and a target column if the rows need different compositions. That lets a single data source drive more than one template without splitting the file.

How do I test before running the whole file?

Preview a small range of rows in After Effects, including your longest and shortest entries, then render one ordinary row and one difficult row as a canary. Templater re-reads the data source each time you preview, so fixes to the file show up on the next preview. Once those files look right, set the full range.

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.