I meant to examine the fonts the sheet uses. If you find one that is corrupted, then you should replace it (as you should with any corrupted font). Unfortunately, I only know font management on the Mac. I don't really know how to go about looking for a corrupted font on Windows or Linux. If you do happen to be on a Mac, You can inspect fonts on the sheet with the inspector as a clue for which ones to investigate with the Font Book app. At a quick glance, the sheet seems to use a lot of "Tiamat Text" in Dark Mode. I assume this is a web font, since it's not commonly installed. I do happen to have that font on my desktop computer due to being a contractor who works on WotC material. If I toggle the font off, the sheet does redraw very slightly (supporting that this is likely a web font) , but doesn't redraw to three columns or anything drastic. It's also possible that for some reason, your computer is not being served the right font at all. Sometimes AWS doesn't deliver all the way through. The fonts for regular text input seem to draw from the following definitions, in order of whether they are available: "Proxima Nova", "ProximaNova-Regular", -apple-system, BlinkMacSystemFont, "Segoe UI", Roboto, Oxygen-Sans, Ubuntu, Cantarell, "Helvetica Neue", sans-serif;" That's as is served to my machine, which is identified as a Mac by the browser. It would be safest for you to right-click and choose "Inspect" on your side, if it's something you want to go to the trouble over. However... I'm just another user in this case. I'm willing to look into it further, but honestly I'm down to grasping at straws without actually sitting behind your keyboard. If you want more informed and official support, the best bet is a Help Center Request . They will likely ask for a Console Log ( Chrome , Firefox ) from the time of opening a sheet. This sounds like a problem they have to deal with upon occasion. It's not terribly common, but I do see someone reporting it maybe a couple of times a year. If they do manage to work it out, please post back so the next time someone has this issue, they can hopefully find a solution as well.