KNOWLEDGE BASE

Fonts Not Displaying as Expected After Publishing to Tableau Public or Tableau Cloud


Published: 22 Aug 2016
Last Modified Date: 28 Nov 2023

Issue

When publishing a workbook to Tableau Public or Tableau Cloud, some fonts, such as Lucida Bright or Book Antiqua, do not display as expected.   

Environment

  • Tableau Desktop
  • Tableau Public
  • Tableau Cloud

Resolution

Because some fonts are not installed on the Tableau Public or Cloud servers, they may not render as expected in published views, including images rendered for subscriptions or exported via tabcmd and  REST API.  The fonts listed below are installed on the Tableau Public and Tableau Cloud servers and should display correctly in published views and in exported images. 

If the font selected in Tableau Desktop does not display as expected on Tableau Public or Tableau Cloud, but does appear on the list below, then install the font locally and test the published workbook again. If it is not possible to install the font locally on the client machine, server-side rendering should occur. As noted in the Configure Client-Side Rendering Tableau Online Help, i
f a view uses the polygon mark type or the page history feature, server-side rendering is always performed, even if client-side rendering is enabled.

The list below is supported by Tableau Public and Tableau Cloud, some fonts may need to be installed locally to display in the font selection drop-down or to draw correctly in the browser.

  • Andika
  • Andika New Basic
  • Arial 
  • Benton Sans
  • Calibri
  • Courier New
  • Georgia 
  • Meiryo UI
  • Muli
  • Noto CJK Sans
  • Noto CJK Serif
  • Noto Thai Sans
  • Noto Thai Serif
  • Open Dyslexic
  • Poppins
  • Roboto
  • Roboto Condensed
  • Tableau fonts
  • Times New Roman 
  • Trebuchet MS 
  • Verdana 

Note: Some fonts may not display as expected when using the Safari browser.

Cause

Tableau Public and Tableau Cloud support fonts officially licensed for our Linux servers. Other fonts cannot be guaranteed to display as expected, since browser rendering of fonts depends on fonts being installed on both the server and client devices and whether browser or server-side rendering is occurring.
 
Did this article resolve the issue?