Salesforce Font: Salesforce Sans and the Native-Font Change

Salesforce’s official Summer 2021 notes say Lightning Design System tokens moved from Salesforce Sans to the native sans-serif UI font provided by the operating system. The related note applies this to Lightning Experience and the Salesforce mobile app. This is direct evidence of a particular product change, not a claim about the Salesforce logo, every marketing page or every separately configured rich-text field.

Salesforce describes the change in terms of readability, localization, reduced branding conflicts and avoiding a font download for system text. Its own explanation contrasts the earlier family with broader platform-font support. Treat those as the vendor’s reasons for the documented change. An old screenshot may therefore differ from another device or release without either image proving a single permanent Salesforce font.

A dashboard label, an email template and a rich-text value can have separate formatting controls. Before trying to match one, record where the text appears and whether a custom component is involved. An instruction to change a font in authored content is different from identifying the application’s default. Keep those questions separate so a historical brand-family name does not become an incorrect setting recommendation.

Use Inter, Source Sans 3 and Manrope for an independent dashboard mockup. They are comparison families, not a claim about the exact default on every Salesforce device. Include a long field label, several numeric values and a wrapped error message. Choose consistent reading sizes and spacing, and make status differences explicit rather than relying on small font-weight changes alone.