An After Effects JSON file is one of three different things, and the search results mix them together. It can be a Lottie animation exported from After Effects, or a plain data file that feeds text, images and colors into a template. A third kind is a JSON file imported into a project as footage so expressions can read it. The file extension is the same in all three cases. The job each one does has nothing in common.
We make Templater, an After Effects plugin that renders batches of videos from data, so one of these three is the file our software reads. We will say which one that is, and we will be fair about the other two. If you landed here because someone handed you a file ending in .json and said “that’s the After Effects file,” the sections below will tell you which kind you are holding and what to do with it.
Three files that all end in .json
JSON is a text format. It stores values in named slots, written between curly braces and square brackets, and any program can read it. Because it is only a container, the extension tells you almost nothing about what is inside. Think of a .txt file. A shopping list and a novel are both .txt. The word “JSON” in a search for an After Effects file sits in the same position.
Here are the three meanings.
The first is a Lottie file. Lottie is a way to ship vector animation to apps and websites. A designer builds the animation in After Effects, exports it with a plugin, and gets a JSON file that describes shapes, colors and how they move over time. A small player library in the app or on the page reads that file and draws the animation live. The file does not contain pixels or video frames. It contains instructions. This is the meaning that can come up when the phrase “after effects json” appears in a developer conversation.
Three File Kinds
All three JSON files end in .json but share nothing else
| File kind | What it contains | What you do with it |
|---|---|---|
| Lottie file | Instructions: shapes, colors, keyframes | Play it in an app or web page through a player library |
| Data file | Content: text, image paths, hex color values | Feed it to a video template to render one video per object |
| JSON footage | Job data written by Templater for one render | Connect expression properties to it with the pickwhip |
The second is a data file. Here the JSON holds information, not drawing instructions. A list of customers, a list of sports scores, a list of listings, each one an object with named fields like a headline, a photo path and a hex color. Nothing in it describes motion. It is waiting for a template to pull values out of it. This is the file we mean when we say JSON, and it is the file our documentation describes. Templater reads a plain text file containing a JSON object array as a data source, alongside Google Sheets and tab-separated files, and it can also read a JSON feed from a URL.
The third is JSON footage. After Effects can import a JSON file into a project the same way it imports a video clip, and an expression can then reach into that file and read values from it. It is a niche trick, and our own documentation treats it as an experimental feature. We cover it near the end, because it is where the data meaning and the inside-After-Effects meaning meet, and it is the one most likely to cause trouble in a batch.
If you only need the quick test, open the file in any text editor. A Lottie file is long and dense, with keys about layers, shapes, frame rates and keyframes. A data file is readable, typically a list of repeated objects where each object looks like a row from a spreadsheet. Once you see which one it is, the rest of this page tells you what to do next.
Lottie: what it is, and where it stops being the right tool
Lottie solves a specific problem. A product team wants a small animated icon, a loading spinner or an onboarding illustration inside an app, and wants it to stay sharp at every screen size. A video file would be heavy and would blur when scaled. An animated image format would give up the vector crispness. A Lottie file stays light and resolution-independent because it describes the animation instead of recording it. The player on the device does the drawing.
The workflow is short. A motion designer animates in After Effects using shape layers. An export plugin converts the composition to JSON. A developer drops the file into an app or a web page and plays it through a library. Because the output is text, a developer can open it, change a color value, or load different animations at runtime. That flexibility is why developers like it.
Now the honest limits, and these are general practice, not Dataclay product claims. A Lottie file only carries what the export plugin and the player agree on. After Effects is a very large program, and a lot of what makes a finished video look the way it does lives outside that shared subset. Footage, video clips, many effects, heavy blurs and some kinds of layering do not travel well into a vector player. Designers who ship Lottie learn to build for it from the start, keeping animations to shapes and simple transforms. If you take a finished video comp and try to export it as Lottie, expect to rebuild parts of it.
That points to the real dividing line. Lottie is for animation that plays inside software you control, such as an app screen or a web page. It is not a way to produce a video file. If your goal is an MP4 that goes onto a social feed, into an ad platform, or onto a broadcast, Lottie is not the format. You need a render out of After Effects, which is a different job.
It is also worth saying what Lottie does not do for the problem our customers have. Suppose you have an animated template and a thousand rows of data, and you want a thousand finished videos, each with its own name, photo and price. A Lottie file can be swapped around by a developer who writes code to alter its values and plays it live in an app. That is fine for an interface. It does not produce a thousand video files you can post. The batch-video problem is a rendering problem, and rendering is what After Effects itself is good at.
Here is a concrete case. A product team at a fitness app has an animated badge that celebrates a user’s streak. The badge shows a number and a color, and it plays inside the app when a user hits a milestone. Lottie is the right choice. The animation is simple vector motion, it must stay small and sharp on every phone, and it plays live on the device. Nobody needs a video file.
Now take the marketing team at the same company. They want a short celebration video for each of their top users, with the user’s first name, their streak count and their photo, to send as a personal message. That is a different job. The result has to be a real video file per person, and it has to include a photo and a name in a font the brand chose. The marketing team does not need Lottie. They need a template in After Effects and a data source with one row per person. Same company, same animation idea, two different tools, and the confusing part is that the word “JSON” can show up in both conversations.
If you are a developer who has been asked to “send the After Effects JSON to the video team,” ask which file they mean before you export anything. A Lottie export will not help them. What they most likely want is the data.
JSON as data: what Templater reads, and what a good one looks like
In our world, a JSON file is a list. Each item in the list is one render job, and each named field in the item is one piece of content that goes into the template. Our documentation puts it this way: each row in a spreadsheet or object in a JSON array represents a specific render job, while each column or property key represents a dynamic layer element within the video template. The values can be text, URLs, image file paths or hex color values.
The keys in the file have to match the names of the layers in the After Effects project. If you name a text layer introTitle in the project, you use introTitle as the key in your data. Layer names should not contain spaces, and our documentation recommends renaming a layer explicitly after you create it, because a layer that keeps its default name may not be treated as dynamic. Each dynamic layer also needs the Templater Settings effect applied, once and only once.
A small example makes the shape clear. Based on the sample in our URL feed documentation, here is the shape, an array of objects, each with an id, a title, two captions, an image, a tint color and a status:
[
{
"id": "json_dyn",
"title": "Create Dynamic Renders",
"caption-1": "Prepare AE projects!",
"caption-2": "parameterized rendering",
"album-cover": "vangelis-spiral.jpg",
"tint": "89B85C",
"render-status": "ready"
}
]
Nothing in that block is about animation. It is content. The title goes to the layer named title, the tint goes to a layer that takes a color, and the album cover is a file path for an image layer. One object, one video. Add two hundred objects and you have two hundred jobs.
A few special keys are reserved for Templater itself, and they are case-sensitive. The ones worth knowing first are id, which labels each output, target, which picks the composition to render, output, which names the file, aep, which switches the project file for a given row, and render-status, which tracks whether a row is ready, queued, processing or done. You need render-status if you use the Templater Bot, because the Bot reads it to decide what to render next. If you leave out id, Templater falls back to the position of the object in the array, which works but makes outputs harder to trace later. We recommend setting your own id or output value so you can find a given video in a folder of hundreds. If both are present, the output value wins for naming.
Two practical details trip people up. The file must be UTF-8, so that international characters read correctly. And when the JSON comes from a URL feed, the Bot cannot update the render-status key itself, because the data source does not live on the machine. The feed is yours to run, with any technology you like, and our documentation suggests registering your own script on events such as Post Job or Post Batch to mark rows done. That is where a developer earns their place on a project like this. If that sounds like more than you want to build, our guide to using a URL feed or JSON file as a data source walks through the choices, and the post on unique IDs and switching project files covers the id and aep keys in more detail.
JSON is not the only way to feed a template. A Google Sheet or a tab-separated file exports from nearly any spreadsheet and is easier for non-developers to edit. JSON becomes the better choice when the data comes out of software and not out of someone’s hands: a database, a CRM export, a web service, your own app. A developer can generate it without a human opening anything. So the rule of thumb is simple. If a person maintains the list, use a sheet. If a program produces the list, JSON is a natural fit. The overview of data sources compares them side by side.
Que, the other product in our Station, takes JSON in a similar way for a different job. Que is a job queue for rendering, and you can insert a batch of jobs into a campaign by uploading a JSON file that contains a single array of objects. The same idea applies. One object, one job. If you want to see the mechanics, the post on inserting a batch of jobs into Que shows the options, and the Que page explains what the product does overall.
The third kind: JSON footage, and how to tell which file you have
After Effects lets you import a JSON file as a footage item. Once it is in the project, an expression can read its values. Templater uses this idea in an optional way. If you turn on a preference to import Templater data as JSON footage, the plugin writes a file named templater-data.json with the data for one job and brings it into your project. For each job it processes, it overwrites that file with the new job’s data. You then connect expression properties to it with the pickwhip.
There are real catches, and our documentation is direct about them. The feature is labeled experimental. Every value in that file arrives as a string, so an expression that needs a number has to convert it. And as of After Effects 15.1.1, Adobe shows a dialog when the structure of an imported JSON footage item changes, which can stall a batch that expects to run without anyone watching. For those reasons we recommend reading the Source Text of a dynamic text layer in expressions instead, which is the more stable route. If you plan to build expressions on top of your data, the post on using Templater data in After Effects expressions lays out both approaches, and the post on when an expression is too fragile to maintain is worth reading before you wire a long chain of them.
So this third meaning is real but narrow. You will meet it only if you are building expression-driven templates and want your data available inside the project.
Now back to the practical question, which is how to tell what you have and what to do. Open the file in a plain text editor and look at the first few lines.
If you see keys that talk about layers, shapes, frame rate, keyframes and similar words, you are holding a Lottie file. Use it where Lottie belongs, in an app or on a web page through a player library. Do not expect it to become a video file, and do not hand it to a team that wants to batch-render videos.
If you see a list of repeated objects with readable fields like names, prices, photo links and colors, you have a data file. This is what a video template wants. Check three things before you use it. First, do the keys match the layer names in the project, letter for letter. Second, are the file paths and URLs real, and do they point to files that exist on the machine that will render. Third, are any values empty or far longer than the layout expects. A missing photo or a very long name can cause a bad frame. Render a few rows first, look at them, and then run the rest. Our post on field type mismatches between spreadsheet, JSON and URL feed sources covers the problems that can come up.
Before You Render
Check three things before using a data file
- Do the keys match the layer names in the project, letter for letter
- Are the file paths and URLs real, and do they point to files that exist on the machine that will render
- Are any values empty or far longer than the layout expects
If you have a file named templater-data.json that showed up in a project panel, Templater put it there for expressions. You do not need to do anything with it unless you are working with that preference on purpose.
If you still cannot tell, ask the person who sent it where it came from. A file exported from an animation plugin is Lottie. A file produced by a database, a spreadsheet conversion or a web service is data. The origin settles it faster than the contents.
One more point of fairness about where our own tool fits. Templater is an After Effects plugin. It drives a project you built in After Effects, fills it with your data, and renders video files through After Effects. Lottie is not among the data sources it reads. If your need is animation inside an app, you do not need us. If your need is many finished videos from a list, Lottie is the wrong shelf and a data-driven template is the right one. You can read what Templater is for the plain version, and the Templater page has the editions and how they differ.
The bottom line is short. When someone says “After Effects JSON,” ask whether they mean motion or data. Motion means Lottie, and it belongs inside software that plays it live. Data means a list of objects that fills a video template, and it belongs in a pipeline that renders files. The third kind, JSON footage, is a narrow tool for expression work and is the one to approach with care. Once you know which file you are holding, the next step is usually obvious, and so is the question of whether you needed to open After Effects at all.
That covers the three kinds of file. If you are still sorting out which one you have, these are the questions we hear most.
Frequently Asked Questions
Is a Lottie file the same as an After Effects project file?
No. An After Effects project is a working file you open and edit in After Effects. A Lottie file is an export, a JSON description of an animation that an app or web page can play through a player library. You cannot turn a Lottie file back into your original project, so keep the project file. Lottie is for playing animation inside software. If you need a video file such as an MP4, you render from the After Effects project instead.
Can I use an After Effects Lottie file as the data source for Templater?
No, because the two files hold different things. A Lottie file describes shapes and motion. A Templater data source holds content, a list of objects where each object is one render job and each key matches a dynamic layer name in your project. Templater reads a plain text file containing a JSON object array, a URL feed that returns one, Google Sheets, or tab-separated files. A Lottie export is not a list of jobs.
What does a JSON data file for Templater need to contain?
A JSON array of objects. Each object is one render job. Each key should match a dynamic layer name in your After Effects project, or one of the reserved keys such as id, target, output, aep and render-status. Reserved keys are case-sensitive. The file must be UTF-8. Values can be text, image paths, URLs or hex color values. If you use the Templater Bot, include render-status so it knows which rows are ready.
Do I need a developer to make the JSON file?
Not always. If a person maintains the list, a Google Sheet or a tab-separated file is easier to edit and Templater reads both. JSON makes the most sense when software produces the data, such as a database export, a CRM or your own app. Then a developer writes the export once and it runs without anyone opening a file. A URL feed asks more of you, since you run a web server that returns JSON, so plan for developer time there.
Should I read my data through JSON footage inside After Effects?
Our documentation points to a more stable route. Templater can import a job’s data as a file named templater-data.json so expressions can reach it. Our documentation labels this experimental. Every value arrives as a string, and After Effects can show a dialog when the imported structure changes, which can interrupt a batch. We recommend referencing the Source Text of a dynamic text layer in expressions as the more stable method.
Why does my output file get a strange name when I use JSON?
Because no id or output key was set. Without them, Templater names the output from the object’s position in the array. Add an id key with your own label to each object, or an output key for the exact file name. If both exist, the output value wins for naming. Avoid periods inside custom output names, since they can cause output errors in After Effects.
