Currently, File fields in the CMS can't be localized with Framer's native localization, while Text, Formatted Text, Image and Link fields can. This is a problem for multilingual sites that offer downloadable content such as brochures, manuals, datasheets or terms & conditions, which usually differ per language.

Right now the workarounds are using a Link field with externally hosted files, or creating separate File fields per language and switching between them with code overrides. Both add complexity and move file management outside Framer or away from the localization workflow.

Request: Make CMS File fields localizable, so a different file can be uploaded per locale, just like Image fields. Ideally this falls back to the default locale's file when no translation is provided, and shows up in the localization table alongside other fields.