Opens in a new tab
Guide

What a Que Autograf Manifest Is

Published November 13, 2026

A Que Autograf manifest is a JSON record of your After Effects project, and it is how Que learns which layers in that project take data. If you have ever wondered what Que actually stored when you clicked a button in Templater, the answer is in that record.

We make Templater and Que, so this page comes from our own help pages and API reference. We will say where those sources disagree with each other, and we will say what we could not confirm. The reader we have in mind is a producer or developer who has an Autograf working and now needs to understand what is inside it, because a pipeline eventually needs somebody who can read the record and not just trust it.

What the manifest is and where it comes from

An Autograf is an After Effects project that has been prepared with Templater so that certain layers accept data. A layer becomes dynamic when it has the Templater Settings effect applied. The manifest describes those dynamic layers and the environment the project was authored in. Que stores the manifest, and the Autograf in your account is described by it.

The manifest gets created from inside After Effects. Our API reference says Templater users open the Autograf Setup dialog and click Create Manifest to register the data-mapped project with Que. Older help pages call the same dialog by an older name, Project Manifest. The API reference is newer, so we use Autograf Setup here. The button names in the API reference are Create Manifest and Update Manifest.

Before Templater sends anything to Que, it writes a manifest file into the same folder as your project file. Our help page names that file dataclay-autograf.json. Our API reference gives a different file name for the same location. Because our two sources disagree, we do not state one exact name here. Look in the project folder for the JSON file Templater wrote. Either way the idea is the same. The manifest sits beside your project, you can open it in a text editor, and the copy inside Que is built from it.

The record matters because Que works from it, not from your open project. If the two differ, reading the manifest shows you what Que holds.

Reading the manifest key by key

You can read the manifest two ways. Open the JSON file in the project folder. Or open the Que Dash, go to the Autografs tab, click the arrow next to the Autograf to expand it, and click Read Manifest in the Autograf Manifest section. Both show the same schema, with one difference we will get to in a moment.

The top level of the manifest has an env object and a rig object. The API reference lists both as required. It also lists a panel object, meant to describe the state of the main Templater panel when the manifest was made, but says that as of Templater 3.0 it is not yet implemented. Do not build anything on it.

The env object holds the authoring environment. Here is what each key tells you, and why you would care.

The env.author and env.author_email keys name the Que user who made the Autograf. They are only set if that person was logged into Que at the time. If they are blank, the help page’s rule is that they are set only when the user is logged into Que.

The env.hostmachine and env.hostuser keys name the computer and the account that authored the project. Together they record where the Autograf was authored.

The env.filepath key holds the full path to where the Autograf is saved on the authoring machine. Our help page flags this one with an IMPORTANT note. The value is used for a Job’s aep property if none is specified. Related keys are env.filefolder, the directory containing the Autograf, and env.filename, the project file name. The env.name key matches env.filename.

The env.target key is the name of the default target composition in the project. Our API reference calls it best practice to set a default target composition inside the project before you create the manifest.

The env.rigver and env.rigbuild keys record the version number and build number of the tool that authored the Autograf. They default to Templater’s own version and build.

The env.host_app object has a name, a version and an os. It records which authoring application, which version, and which operating system the project came from. Our API example shows an After Effects version and an operating system value in these fields.

The env.fonts and env.effects keys are arrays. They list the fonts and effects the Autograf depends on being installed on a host machine. In the API reference’s example, the fonts array holds a single font name, and the effects array holds Drop Shadow, Glow and Templater Settings. We come back to this pair below.

Now the difference we promised. Five keys appear only in the copy stored in your Que account, and not in the file next to your project. They are _id, _orgId, _createdAt, _updatedAt and _isEnabled. The _id is the manifest’s ID in Que. The _orgId is the organization the author belongs to. The two timestamps record when the Autograf was added and when it was last updated. The _isEnabled flag says whether the Autograf is available for use, and it always defaults to true. If you are comparing the file on disk to the copy in Que and the two look different, these five keys are the expected difference.

Two Manifest Copies

Local file vs. Que-stored copy differ by five keys

Where to open it
Local file (project folder)Open the JSON file in the project folder
Que-stored copyOpen Autografs tab, click Read Manifest
Has env and rig objects
Local file (project folder)Yes, both required
Que-stored copyYes, both required
Underscore keys present
Local file (project folder)Not included
Que-stored copy_id, _orgId, _createdAt, _updatedAt, _isEnabled

Five keys appear only in the copy stored in your Que account, and not in the file next to your project.

The rig object, layer by layer

The rig object describes the dynamic elements. They are sorted by layer type, and each type is an array where every object is one dynamic layer. The types are text, footage, solid, comp, adj and json. In plain terms, those are dynamic text layers, footage layers, solid layers, pre-composition layers, adjustment layers and JSON layers. The parameter settings for each dynamic element are stored in the manifest as well.

This is the part that ties the manifest to your job data. A job in Que is a set of key-value pairs, and the keys map onto dynamic layers in the Autograf. Our API reference gives a hypothetical example: a headline key and a subtitle key feeding two text layers, a feature-image key feeding a footage layer, and a bg-color key holding a hex value for a solid layer. The manifest is where Que learns which dynamic layers exist at all.

Rig Layer Types

Six dynamic layer types inside the rig object

Type key Plain-English name Example data key
text Dynamic text layers headline, subtitle
footage Footage layers feature-image
solid Solid layers bg-color
comp Pre-composition layers —
adj Adjustment layers —
json JSON layers —
The types are text, footage, solid, comp, adj and json, every dynamic layer in your project maps to one of these.

Take the layer shown in our API reference example. It is a text layer named caption-2, at index 1, with the type text, sitting in a composition named caption bottom. Its layout block records a scale of 100 and an alignment with an edge of top_left and a padding of 0. That is the level of detail the manifest keeps. It is a description of a layer, so a reader, human or program, can see what the layer is and where it lives without opening After Effects.

There is one more key under rig worth knowing. The rig.spotchecks object describes each composition timeline marker used for spot checking in Templater. Only markers whose names are wrapped in double braces, like , get written to the manifest. If you named a marker without the braces and expected it in the spot-check list, that is why it is missing. Our page on preview modes and spot checks covers what the checks are for.

One honest limit here. Our saved sources show the shape of a text layer in the API example, and they name the other layer types, but they do not walk through every field of every type. We will not pretend to document the footage or JSON layer fields beyond what the help page states. If you need that level, open a real manifest from your own project and read it. You will learn more from your own file than from a description of someone else’s.

A worked example: a job fails on a second machine

Here is a scenario that shows how the manifest earns its keep. A motion designer builds a template on her own workstation and uses a licensed display font. She maps a headline and a subtitle to two text layers, sets a default target composition, and creates the manifest from Autograf Setup. A producer then builds a campaign on top of it and inserts rows. The jobs are assigned to a satellite, a separate machine that renders them. That satellite does not have the display font installed.

Where do you look? The Autograf’s env.fonts array. The manifest lists the font by name, because it records fonts the Autograf depends on being installed on a host machine. Our help page on working with Autografs says the same thing from the operations side. If you need your Autografs and their dependencies on multiple Satellites, you will need a workflow for deploying them to each one, and you may need to install and activate specific fonts and effects on each Satellite so the Autograf can be processed without dependency errors. The manifest does not fix the problem. It tells you the exact list to fix. That turns a vague “the render looks wrong on machine two” into a checklist.

The same logic covers effects. The env.effects array in the API example includes Templater Settings, which is expected, and two ordinary effects. A satellite that lacks an effect the project uses has the same kind of gap. Read the arrays, compare them to what is installed, and close the difference before you insert hundreds of rows.

The second place this scenario can bite is the file path. Remember env.filepath, the full path on the authoring machine. Our help page says it is used for a job’s aep property if none is specified. The job documentation says that if a job request does not include an aep or bot value, Que sets them to the campaign’s default Autograf and satellite. Our reading, and this is our reasoning and not a documented guarantee, is that a path recorded on the designer’s workstation points to a location on that workstation. If the render machine cannot see the same location, the job has nowhere to go. The help page suggests a sync folder service as one way to keep the latest Autograf on every satellite.

For the file-sharing question, we will not recommend a specific setup. The help page names the idea, a sync folder service, and leaves the choice to you. Pick whichever your team already trusts, and test one job on each satellite before you trust it with a batch.

Keeping the manifest current, and what lives where

An Autograf is not frozen. After you create one, you will probably tweak the project. Our API reference says the best practice for updating an Autograf is to use Autograf Setup in Templater and click Update Manifest. You can also call the API directly, with a PUT request to the autografs endpoint and the Autograf’s ID. The body of that request is merged with the properties of the current Autograf as stored in Que. Merged is the word the reference uses, so send what changed and expect the rest to stay.

The rest of the Autograf endpoints are what you would expect. A POST to /api/v1/autografs creates one. A GET with an ID retrieves one, and a GET with no ID retrieves all of your organization’s Autografs. The ID must be in ObjectId format, according to the reference. A DELETE removes one, and the reference is blunt about it. Deletion is permanent, and any job that references a deleted Autograf cannot be processed until a new Autograf is assigned to that job.

That last point deserves a plain statement. If you clean up your Autografs list and delete an old one, you are not only removing a template. You are stranding every job that points at it. Our page on job states explains what the render-status values mean and what to do next when a job stops moving.

There is a design detail that quietly protects you here. When an After Effects project file is added to Que, its corresponding ID is stored in the file’s XMP metadata, according to the API reference. That means no matter where you copy or share the .aep, its Autograf ID stays embedded and is never erased. The practical meaning is that a copied project keeps its identity. The sources do not say what Templater does when you open a copy, so we will not guess. Our help pages cover cloning an Autograf as its own action, and our complete guide to Autografs is the better place to start if you want the whole lifecycle.

Our help page says you can use the Que Dashboard to inspect an Autograf’s manifest or remove it from Que if your user account has those privileges.

One more fact connects the manifest to everything else in Que. A campaign needs an Autograf. At least one must be in your account before you can create a campaign, and you pick a default Autograf when you create it, so any inserted job uses that default when none is specified. Later you can edit an individual job in the Que Dash to use a particular Autograf. If you are scripting the steps, getting started with the Que API walks through keys, endpoints and a first job, and our page on satellites covers the machines that do the rendering.

Where the manifest does not help you

Be clear about what this record is not. It is not your data. The rows that make each video live in jobs, and the manifest says nothing about the values you will send. It is not a backup of your project either. It describes layers and the environment, and your .aep still has to exist where the render machine can reach it. It will not tell you whether a design looks good, and it does not render anything.

It also will not stay correct on its own. When you change the project, the manifest in Que changes only when you update it. A designer who adds a new dynamic layer and forgets to click Update Manifest has created a template that looks right in After Effects and wrong in Que. Make the update step part of the handoff, the same way you would make a version bump part of a release. That is our general practice suggestion and not a documented rule.

The bottom line

The manifest is a plain JSON description of your project: the environment it was built in, the fonts and effects it needs, the dynamic layers by type, and the markers used for spot checks. Que stores it, and everything else in Que, from campaigns to jobs, points back to it.

Read it when something is off. Check env.fonts and env.effects when a second machine cannot process a job. Check env.filepath when a job cannot find its project. Click Update Manifest whenever the project changes. Do not delete an Autograf that a live job still uses. If you remember only one thing, remember that Que works from this record, so keep it in step with your project.

Manifest Health Check

What to do when something is off

  • Check env.fonts and env.effects when a second machine cannot process a job
  • Check env.filepath when a job cannot find its project
  • Click Update Manifest whenever the project changes
  • Do not delete an Autograf that a live job still uses
  • Install and activate specific fonts and effects on each Satellite so the Autograf can be processed without dependency errors

Here are specific questions about reading a manifest.

Frequently Asked Questions

How do I view an Autograf’s manifest in the Que Dash?

Open the Autografs tab, click the arrow next to the Autograf you want to expand it, and click Read Manifest in the Autograf Manifest section. You need an account with the privileges to inspect manifests, according to our help page. The copy you see is the one stored in Que, so it includes the keys whose names begin with an _ character and are not in the file next to your project.

Why does the manifest in Que have keys that my local file does not?

Five keys whose names begin with an _ character appear only in the copy stored in your Que account. They are _id, _orgId, _createdAt, _updatedAt and _isEnabled. Que adds them when it stores the Autograf. They hold the manifest’s ID, the organization ID, the added and updated times, and whether the Autograf is available for use. The _isEnabled value defaults to true.

What happens to my jobs if I delete an Autograf?

Deletion is permanent. According to our API reference, any job that references a deleted Autograf can no longer be processed until a new Autograf is assigned to that job. Before you delete, check which campaigns and jobs still point at it, and assign a replacement first. Our help page says you can remove an Autograf in the Que Dash if your account has that privilege.

How do I update an Autograf after I change the After Effects project?

The best practice in our API reference is to open Autograf Setup in Templater and click Update Manifest. You can also send a PUT request to the autografs endpoint with the Autograf’s ID. The request body is merged with the properties of the current Autograf as stored in Que, so you can send only what changed. The help pages do not list what else needs an update, so check your own project.

Which fonts and effects does an Autograf need on a render machine?

The manifest tells you. The env.fonts array lists fonts the Autograf depends on being installed on a host machine, and the env.effects array lists the effects it depends on. Our help page says you may need to install and activate specific fonts and effects on each satellite so the Autograf processes without dependency errors. Compare the arrays against each machine before you run a batch.

Why is a spot-check marker missing from the manifest?

Only composition timeline markers whose names are wrapped in double braces, like , get written to the rig.spotchecks object. A marker named without the braces is not recorded. Our help page describes this behavior under the rig.spotchecks key.

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.