Label Templates

Label templates let you save a complete label schema and reuse it across multiple projects. Instead of manually recreating the same set of labels, colors, and shortcuts every time, save your schema once and load it wherever you need it.

Overview

When you work on multiple projects that share the same annotation vocabulary — for example, the same set of manipulation primitives like "reach", "grasp", "lift", and "place" — recreating the label schema from scratch for each project is tedious and error-prone. Templates solve this by capturing your label configuration as a reusable blueprint.

Templates are stored per user. Your saved templates are available to you across all your projects.

What Templates Include

A template captures the label names from your schema:

Label names — The human-readable names of each label.

Colors, keyboard shortcuts, export values, and order are not stored in templates. When you load a template, the label names are imported and you can then configure the remaining settings (colors, shortcuts, etc.) for the new project.

Templates do not include annotations

Templates store only the label schema definition. They do not include any annotation data (which frames are labeled with what). Annotations remain tied to their respective datasets.

Saving a Template

To save your current label schema as a template:

Open the Labels tab in your project settings.
Ensure your labels are fully configured — names, colors, shortcuts, and export values should all be set as desired.
Click Save as Template.
Enter a descriptive name for the template (e.g., "Manipulation Primitives" or "Pick-and-Place Actions").
Click Save. The template is now available to you across all your projects.

Loading a Template

To apply a saved template to a project:

Open the Labels tab in the target project.
Click Load Template.
Select the template from the list of available templates.
Confirm the import. The template's labels are added to the project.

Loading replaces existing labels

Loading a template replaces the project's current label schema. If the project already has labels with annotations, those annotations may be affected. Load templates into new projects before starting annotation work.

Templates are personal — each user manages their own library of templates. Your saved templates are accessible from the Labels tab of any project you have access to.

Common use cases for templates:

Standard task vocabularies — Define your canonical set of manipulation labels once and reuse them across projects.
Multi-robot consistency — Use the same label names across different robot platforms to produce comparable datasets.
Quick project setup — Load a template when creating a new project instead of recreating the same labels from scratch.

Managing Templates

You can view, rename, and delete templates from the organization settings. Deleting a template does not affect projects that have already loaded it — the labels remain in those projects independently of the template.

If you update labels in a project after loading a template, the template itself is not modified. Templates are snapshots — changes to the source project or the loaded project do not propagate back to the template.

Version your templates

If your label schema evolves over time, save updated templates with version numbers in the name (e.g., "Manipulation v2"). This lets you track which projects use which version.

Workflow Examples

Here are two common workflows using templates:

Starting a new project from a standard schema:

Create a new project in your organization.
Go to the Labels tab and click Load Template.
Select your standard template.
Upload your datasets and begin annotating immediately.

Creating a template from a well-configured project:

Set up and refine your labels in a project until the schema is finalized.
Save the schema as a template with a descriptive name.
Other team members load this template into their projects for consistent labeling.