This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

All of my text appears as question marks inside boxes on Google and other websites when I use Firefox.

  • 2 ŋuɖoɖowo
  • 54 masɔmasɔ sia le wosi
  • 6 views
  • Nuɖoɖo mlɔetɔ kerriefaye

more options

Even though I haven't changed any settings or fonts/font preferences, Firefox has started (out of the blue) displaying all of the text on my screen as questions marks inside boxes. This happens on Google and many other websites, but not every website. For example, it happens on Google, while it does not happen on Facebook, but it happens when Facebook displays another website on its page. This first happened yesterday on my desktop iMac. My laptop (Macbook Pro), however, has been fine all day...until about 30 minutes ago, when it too began displaying all text as question marks inside boxes. I have read a lot of online forums to see what others have done in this situation, and I have tried most of the troubleshooting suggestions, to no avail.

Even though I haven't changed any settings or fonts/font preferences, Firefox has started (out of the blue) displaying all of the text on my screen as questions marks inside boxes. This happens on Google and many other websites, but not every website. For example, it happens on Google, while it does not happen on Facebook, but it happens when Facebook displays another website on its page. This first happened yesterday on my desktop iMac. My laptop (Macbook Pro), however, has been fine all day...until about 30 minutes ago, when it too began displaying all text as question marks inside boxes. I have read a lot of online forums to see what others have done in this situation, and I have tried most of the troubleshooting suggestions, to no avail.

Ŋuɖoɖo si wotia

Hi, this is affecting quite a few Mac users.

Firefox 56 ratcheted up the security sandbox, limiting which files pages can use on your system. This apparently prevents Firefox from using font files in a "suitcase" or "Adobe Type 1" format. The developers are aware of this and considering solutions for a future version of Firefox.

For right now, you can reduce the sandbox security level back to what it was in Firefox 52-55 as follows:

(1) In a new tab, type or paste about:config in the address bar and press Return. Click the button accepting the risk.

(2) In the search box above the list, type or paste sand and pause while the list is filtered

(3) Double-click the security.sandbox.content.level preference and change the value from 3 to 1 and click OK

That change won't take effect until the next time you quit and restart Firefox.

Does that let Firefox show website fonts normally?

Xle ŋuɖoɖo sia le goya me 👍 115

All Replies (2)

more options

Ɖɔɖɔɖo si wotia

Hi, this is affecting quite a few Mac users.

Firefox 56 ratcheted up the security sandbox, limiting which files pages can use on your system. This apparently prevents Firefox from using font files in a "suitcase" or "Adobe Type 1" format. The developers are aware of this and considering solutions for a future version of Firefox.

For right now, you can reduce the sandbox security level back to what it was in Firefox 52-55 as follows:

(1) In a new tab, type or paste about:config in the address bar and press Return. Click the button accepting the risk.

(2) In the search box above the list, type or paste sand and pause while the list is filtered

(3) Double-click the security.sandbox.content.level preference and change the value from 3 to 1 and click OK

That change won't take effect until the next time you quit and restart Firefox.

Does that let Firefox show website fonts normally?

more options

jscher2000 Thank you! That seems to have fixed the problem.