A Chrome window that flashes black or repaints itself every time you maximize it, or drop it into a macOS tile, is usually a rendering problem rather than a failing display.
Start with graphics acceleration, then compare a Guest window against your normal profile. If the flash survives both, check the GPU status page and test the occlusion flags one at a time.
In this guide, I have covered:
Contents
Why Chrome windows flicker when you maximize or tile on Mac
You hit the green button, or drag the window into a tile, and Chrome flashes black for a split second before the page settles. That flash is Chrome rebuilding its window surface, and it only becomes visible when the redraw doesn’t land in one pass.
It looks like a flicker, a blink, or a black rectangle in the corner of the window. It shows up when you maximize, use macOS window tiling, drag a window between displays, or move between a regular window and full screen.
Chrome’s rendering path and your Mac’s graphics driver decide how that redraw is handled. An extension, a damaged profile, or an experimental flag can be involved too. Work through the fixes below in order, and repeat the same window action each time so you can tell whether anything changed.
Turn Chrome’s graphics acceleration on or off
Chrome can hand page and window rendering to your Mac’s GPU. Flipping this one option changes how Chrome draws window surfaces, which makes it the quickest test to run first.
- Open Chrome Settings.
- Click System in the left sidebar. (If your Chrome still groups it under an expandable Advanced section, the path is Settings > Advanced > System.)
- Toggle Use graphics acceleration when available on or off, then relaunch Chrome.
After Chrome restarts, maximize or tile the window again. If the flash is gone, keep the setting that produced the stable result. If it’s still there, try the opposite state: some Mac and driver combinations behave better with acceleration off, others with it on.
The same switch decides how video and 3D content render, so read how hardware acceleration works in Chrome before you leave it off for good.
You’ll know it worked when the window draws in one clean pass, with no black gap and no double paint.
Chrome normally asks you to relaunch after this change. Finish the relaunch before you test. The new rendering mode isn’t active until the browser restarts.
Test a Guest window to rule out extensions and your profile
When the flicker only appears in your everyday profile, something installed there is the likely cause. A Guest window gives you a clean Chrome with no extensions and default settings, and it opens in a few seconds.
- Click the Profile icon in the top-right corner of the Chrome window.
- Click Guest profile.
Maximize or tile the Guest window using the same action that misbehaves in your normal profile. No flicker? Then your extensions or profile settings are the place to look, and you can switch extensions off one at a time until the flash stops.
If the Guest window flickers too, extension hunting is a dead end. Move on to the rendering checks below, because the problem sits in Chrome or macOS rather than in your profile.
You’ll know it worked when the flicker either follows your profile or appears in both windows, since each result points to a different next step.
Check Chrome’s GPU status page
Before changing anything else, confirm what Chrome thinks of your graphics setup. The internal GPU page lists the acceleration state and the backend in use, and it is read-only, so nothing there can make things worse.
- Open a new tab in Chrome.
- Enter chrome://gpu in the address bar.
- Press to open the GPU information page.
- Read the graphics feature status and the acceleration details it reports.
- Return to the window that flickers and maximize or tile it again.
If the page reports that acceleration is unavailable, or the status doesn’t match the setting you chose above, go back, set acceleration to the state you actually want, relaunch Chrome, and retest.
Test Chrome’s occlusion and compositing flags
Still flickering after the acceleration test? Two experimental flags control how Chrome decides a window is visible and how it composites that window. Change one at a time so you know which one mattered.
- Open chrome://flags in a Chrome tab.
- Search for Calculate native win occlusion.
- Set the flag to Disabled.
- Select and wait for Chrome to restart.
- Maximize or tile the affected window and check whether the flicker has stopped.
If it survives, search for Web contents occlusion, set that one to Disabled as well, and relaunch Chrome again. Then repeat the same maximize or tiling action.
Leave unrelated flags alone while you test. If neither flag helps, set both back to Default before you try another approach.
- Type chrome://flags into Chrome's address bar and press .
- Click the Reset all button at the top of the page.
- Click the Relaunch button at the bottom. Chrome will restart with default flags.
A reset gives you a clean baseline. After the reset and relaunch, repeat the graphics-acceleration test before adding more changes.
You’ll know it worked when the first maximize after a relaunch draws the window once, with no black flash.
Check for other window-state conflicts
Sometimes the trigger isn’t Chrome’s renderer at all, but the window state macOS puts Chrome in. Tiling, full screen, multiple displays, and Spaces each change what Chrome has to draw.
- Close unnecessary Chrome windows and tabs.
- Open the affected window at its normal size.
- Use the green window control to test macOS tiling without entering full screen.
- Repeat the test with the window in full screen.
- Test again after moving the window to another display, if your Mac has more than one.
Note which state flickers. When only one does, you are chasing a macOS window-mode issue rather than a broken Chrome setting.
Update Chrome, then restart the Mac
Chrome updates regularly, and some of them change how the browser composites windows. Get current before you decide the flicker is permanent.
- Open Chrome on the Mac.
- Select About Google Chrome from the main menu.
- Choose Check for updates.
- Install any available update and relaunch Chrome.
- Test the maximizing or tiling action again.
If the problem is still there after the update, restart the Mac and test once more. That clears the current display and graphics state, and it confirms whether the issue survives a clean session.
What you want at the end is a window that maximizes and tiles without a flash, plus a Chrome setup you can explain later. In practice that means one changed setting and everything else back at its default.
Frequently Asked Questions
Does turning off graphics acceleration fix Chrome window flickering on Mac?
Not every Mac gets the same result. Chrome can flicker with acceleration on, off, or both, depending on the graphics driver and the page involved. Test both states and keep whichever one removes the flash.
Why does Chrome flicker only when I maximize or tile a window?
Those actions change how Chrome redraws its window, which can expose an acceleration, occlusion, or compositing problem. Test the same action after each single change.
Are Chrome flags safe to use for a flickering window?
Flags are experimental and can change browser behavior. Use them for diagnosis, one at a time, and set them back to default if they don’t help.
Does the flicker mean that my Mac display is broken?
Not necessarily. If only Chrome flickers and another browser or the macOS desktop looks fine, the issue is more likely Chrome’s rendering or settings than your display.
