Nested h1 font size change in Chrome 140+

Learn why h1 headings render larger in Chrome 140 and later and how it affects Percy snapshots.

Before Chrome 140, an h1 heading nested inside sectioning elements such as section, article, aside, or nav rendered at h2 font size through the browser’s default stylesheet. Chrome 140 and later deprecated this behavior, so every h1 heading now renders at its full h1 size. Firefox and WebKit-based browsers follow the same behavior.

This change is visible on devices that run the newer browser versions, such as Samsung Galaxy S22 on Android 16, which uses Chrome 145. If your pages use nested h1 headings, Percy reports visual differences where the heading size increased, even though your code has not changed.

How to fix it?

• Review the flagged snapshots and approve the new baseline if the larger heading is expected.
• Set an explicit font size on nested h1 headings in your CSS to keep the earlier appearance.

This is expected browser behavior. For more information, see the Chrome Platform Status entry.

Need more support? Contact BrowserStack.

Reference Topic

• Percy Common - FAQs