AI metadata is a feature that leverages the design context available in Frontitude and integrates it into writing and localization workflows. This means more AI-generated context that eliminates the need for manual input!
It’s worth mentioning that even after being generated automatically, metadata can always be edited.
Configuring AI Metadata
This feature is enabled by default, but you can turn it off in your workspace settings if you prefer not to use it.
What metadata is generated
Frontitude uses AI to generate the following metadata for copy components:
Unique key
Each copy component is assigned a unique key, which serves as an identifier for tracking and referencing content across different workflows.

A few important notes:
- If a unique key convention is defined in your workspace settings, Frontitude AI will follow it and generate keys accordingly.
- If there are any saved copy components with unique keys, Frontitude AI will learn from them and reuse their convention and style.
- Generated keys are unique across your workspace.
Component name and category
Frontitude AI automatically categorizes copy components into existing or newly generated copy library categories based on their function and design context, while also generating a descriptive name.

💡 Tip: It’s recommended to build your copy library structure using empty categories to help Frontitude AI adjust categorization to your framework.
A few important notes:
- Frontitude AI has access to your existing copy library categories and will reuse them when relevant.
- If relevant, Frontitude AI can apply nested categorization with up to three levels.
Design context
Frontitude AI extracts written design context from the design file to provide additional details about where and how each copy component is used.

A few important notes:
- Design context is included in file exports to support workflows that lack visual design context.
- Design context is used to generate design-aware translations with the AI Translation feature.
Tags
Frontitude AI assigns tags based on content patterns and design context. These tags make it easier to filter, search, and manage copy components within the Frontitude workspace.

A few important notes:
- Generated tags are saved in your workspace’s tag collection.
- If relevant, Frontitude AI will reuse existing tags saved in your workspace.
- AI metadata generates three tags for each copy component.
How to trigger AI metadata generation
Currently, the only way to trigger AI metadata generation is by creating a copy component using:
- Save to Library: Available in the web app and Figma plugin for both single and bulk actions.
- Finalizing texts: Applies to both single and bulk regular text finalization.
- Copy component import: When importing copy components into the copy library.
- Manual creation: When manually creating a copy component in the copy library.