Key Clustering

Key clustering works best when you’re uploading content through API-based integrations like Figma or Strapi and want to automatically handle duplicates without manual work.

It’s particularly useful if you’re using Figma as your source of truth since it prevents you from having to manually manage duplicate text nodes.

Choose Duplicity Linking when you need to handle duplicates across multiple files or projects, or when you want full control over which keys get linked together. Key clustering only works within a single file and handles duplicates automatically, while duplicity linking gives you more flexibility but requires manual setup.

Keys nested within a cluster don’t count toward your source key limit, which can help you stay within your plan’s limits even with lots of duplicate content.

For example, if you have 50 duplicate “Save” buttons from different Figma frames, they’ll all be clustered under one source key that counts as just one key against your limit.

This is different from Duplicity Linking, where each linked key still counts toward your limit. The clustering happens automatically when you upload content through API-based sources, so you don’t need to do anything special to get this benefit.