My character sheet's background seems to be messed up

I've somehow managed to turn every image in my sheet white. I don't know how to fix it so I decided to ask for help here. It only happens with player sheets, not NPCs. I'd assume it has to do something with the color values in my browser. Any ideas? Any answer is greatly appreiated!

Hi Firgon72! Some screenshots might help to demonstrate the issue. Also, which sheet are you using, or is this a sheet you are developing?

Hi keithcurtis! I've tried to post screenshots originally, but sadly I encountered some issues, I'll try again now too. It is the regular 5e D&D character sheet, I tried but can't delve too deep into the inns and outs of sheet developing, mostly just to solve this issue. I appreciate the answer and that you reached out in such a timely manner! If you manage to find any solution, I'll be eternally grateful. Cheers!

Well, in terms of sheet development, there's not much you can do for the D&D 5th Edition by Roll20 Sheet, since the code is proprietary. Users don't have access to it. Unless you were messing around with CSS code in an extension like Stylus, I don't think this is anything you've done. I would suggest deleting cache and cookies from your browser, since it may be using cached light mode images while in dark mode. You could also test by running in a private browsing window. If the sheet looks fine there, it is almost certainly cached data or the action of a browser extension.

Sadly neither of these worked. The effect itself persists for different browsers, but not for different devices. I'm using Opera GX, so that might have had something to do with it. In any case, thank you for the suggestions!

Are you running a VPN, maybe? The only other advice I have ti try besides a  Help Center Request , is to go to your Account page and try turning on the Experimental Image Delivery Service. This uses a different method to serve images to your browser and may fix hiccups caused by overzealous security somewhere in the pipeline.

I've submitted a ticket, we'll see how that goes. I also checked it out on Crome, and the issue isn't present there, so it must be my browser. This might not be something that's fixable sadly.