Window is solid black or solid white; looks like a blank page


Window is solid black or solid white; looks like a blank page

This has been reported with several issues:

The root cause appears to be that Chromium is having a problem with hardware acceleration. Disabling hardware acceleration in our preferences screen (if you’re able to get that far) doesn’t always work. We do have a documented issue to make this easier to try… but in the meantime, here are some steps you can take.

Command line flags and their impact

  • --ignore-gpu-blacklist: Per Chromium: "Ignores GPU blacklist.". If your GPU is blacklisted you likely will have display problems. This removes it from that list and should still keep hardware acceleration (important for media like WebGL)
  • --disable-gpu: Per Chromium: "Disables GPU hardware acceleration. If software renderer is not in place, then the GPU process won't launch.". This is a more extreme option


  1. Right click the Brave shortcut and pick properties
  2. In the Target area, paste in the command line flag at the end (see above). For example, the screenshot below shows the more extreme option, --disable-gpu
  3. Click Apply and close the window
  4. Launch the shortcut you just changed

screen shot 2017-01-29 at 10 53 40 pm


  1. Open a terminal (CTRL + ALT + T on many distributions)
  2. Locate the Brave desktop file using locate brave.desktop.
  3. Open the file in an editor as root. Example: sudo nano /usr/share/applications/brave.desktop.
  4. Change the Exec=brave %U line to either Exec=brave --ignore-gpu-blacklist -- %U or Exec=brave --disable-gpu -- %U.
  5. Save the file and exit the editor. In nano, this is done with CTRL + O then CTRL + X.
  6. (Re)start Brave.

Updating Brave issue
The interface goes white, and parts of the web view are whited out on hover

Black page with specific picture in Brave Browser in Win7 pro

Something important to check if the above does not work (and you are on macOS for example). Check and see if you have an environment variable set for NODE_ENV. If this is set, you may encounter a problem. This behavior is not intentional (it’s a bug) and is tracked with