Short answer: text that renders clipped or cut through the middle in Chrome on macOS, while looking correct in Safari, is a graphics rendering fault rather than a problem with the websites or your fonts. Turn off graphics acceleration at chrome://settings/system and relaunch. If the text renders correctly afterwards, the GPU rendering path was the cause and the sections below explain what to do next.
Who this applies to
Chrome on macOS. If you see the same clipping in Safari and other applications, this is not the right guide, and the problem is more likely a macOS font issue or a damaged font file. No administrator access is required for anything here.
How to confirm it is Chrome and not your Mac
Two checks, in this order:
- Open the same page in Safari. If the text is fine there, the fault is in how Chrome draws, not in the site or your system fonts.
- Open the page in a Chrome Incognito window. If it renders correctly there, an extension is involved rather than the graphics path.
Doing this first matters, because the fixes below only address Chrome-side rendering. If Safari shows the same broken text, changing Chrome settings will waste your time.
Why this happens
Chrome does much of its drawing, including text layout, through your Mac’s graphics hardware. When something in that path misbehaves, whether a driver-level quirk, a specific hardware and macOS combination, or a change in a Chrome build, glyphs can be drawn with the wrong dimensions and end up visually clipped.
An honest limit: we could not verify a specific, publicly documented Chrome bug that produces this exact clipping, nor any announced fix or version number. An earlier version of this article named a precise internal cause and promised a patch in an upcoming release. That was not supported by any source we can point to, and it has been removed. What follows are the settings that genuinely affect Chrome’s text rendering, presented as things to try rather than a diagnosis.
How to fix it
1. Turn off graphics acceleration
- Go to chrome://settings/system.
- Turn off Use graphics acceleration when available (labelled Use hardware acceleration when available on older builds).
- Click Relaunch.
- Reload an affected page.
This is the highest-value test. If the text is suddenly correct, you have isolated the problem to the GPU rendering path. Leaving acceleration off long-term does cost you smoothness in scrolling, maps, and video, so treat it as a diagnosis and move to step 2.
2. Update macOS and Chrome
- Install any pending macOS updates, since graphics drivers on a Mac ship with the operating system and cannot be updated separately.
- In Chrome, open the Chrome menu, then About Google Chrome, install any update, and relaunch.
If a Chrome build introduced the behaviour, a later build is the actual fix. Once you have updated, turn graphics acceleration back on and check whether the problem is genuinely gone before assuming it needs to stay off.
3. Rule out extensions
- Open an Incognito window with Cmd+Shift+N, where most extensions are disabled.
- Load an affected page.
- If the text is correct, go to chrome://extensions, turn everything off, and re-enable one at a time until the clipping returns.
Extensions that restyle pages, change fonts, apply dark themes, or enforce readability settings are the ones worth suspecting first.
4. Reset the page zoom
- On the affected page, press Cmd+0 to reset zoom to 100%.
- Check whether the text renders correctly.
Unusual zoom levels sometimes expose layout rounding problems that look like clipping. Cheap to test and occasionally the whole answer.
5. Test a fresh Chrome profile
- Click your profile picture in the top-right corner and add a new profile.
- Continue without signing in, and load an affected page.
If the new profile renders correctly, something in your original profile, most likely an extension or a stored setting, is responsible. Your existing profile is not deleted by this test.
6. A note on chrome://flags
You will find advice online recommending you disable canvas or GPU rasterization flags for this. Flags are experimental, are renamed and removed between versions without warning, and can introduce their own rendering problems. We would not recommend changing them unless the steps above have failed and you are comfortable resetting them afterwards from the Reset all button at the top of chrome://flags.
If you need to read the page right now
Open it in Safari. Its text rendering is independent of Chrome’s, so any page affected by this will display normally there. That is the practical answer while you work through the steps above, rather than a fix in itself.
FAQ
Is this damaging my Mac or my fonts?
No. It is a display fault. Nothing is being altered on disk, and no font files are modified.
Why does Safari look fine?
Safari uses macOS text rendering directly, along a different path from Chrome’s. A fault in Chrome’s drawing does not affect it.
Will turning off graphics acceleration slow Chrome down?
A little, most noticeably in scrolling, video, and map-heavy sites. It is a good test, but restore it once you have identified the cause.
Should I reinstall Chrome?
Not before testing a new profile, which is quicker and tells you more. Reinstalling will not help if the cause is the graphics path.
Only one website looks wrong. Is that the same problem?
Probably not. A single affected site usually points at that site’s own fonts or stylesheet. This guide addresses clipping seen across many sites.
What to remember
Check the page in Safari first, since that one comparison tells you whether the fault is Chrome’s at all. If it is, turning off graphics acceleration will confirm the rendering path is responsible, and updating macOS and Chrome is the real fix rather than leaving acceleration disabled indefinitely.
