Mutiny syncs site content into Framer as native layers so customers can continue editing generated pages inside Framer. Our synced CMS payload includes complete typography metadata, including custom font families, weights, styles, sizes, line heights, and colors. Customers can upload those same custom font files into their Framer project, but the plugin API does not expose or accept those uploaded fonts when creating text styles or setting text node attributes.

This blocks visual parity for Mutiny-to-Framer sync. Even when fontFamily: "Affix Trial Regular" is present in the CMS entry and the font has been uploaded into the Framer project, the plugin cannot resolve it via getFont/getFonts, and Framer drops optimistic fontFamily/fontWeight/fontStyle or family/weight/style attributes. As a result, generated Framer layers lose the customer’s brand typography and require manual font correction after every sync.