Divi Font Weights: Check the Selected Face and Browser Result

By Dave TanguayPublished Updated Editorial draft

Quick Answer

When a Divi heading’s weight looks wrong, check the selected family and weight, the applied CSS, the available font files and the browser’s actual rendered face. A Bold selection does not prove that a particular bold file loaded. Separate missing files, fallback fonts, synthesized weight and shared-setting overrides before changing the site’s typography.

Two headings can share a family name and still render differently. Begin with one specific heading, its page and the intended reference rather than replacing every font across the website.

Record what the Divi field requests

The current Divi 5 Heading Text guide lists font family and font weight as separate settings. It also describes variable-font controls when supported. Record the actual selected values and applicable responsive state.

Identify whether a preset, variable, template or local override supplies the value. Preserve those references before a proposed correction. A family variable and a weight setting can have different sources.

Compare the request with the browser result

Evidence Question to investigate
Builder selection Which family and weight does the relevant module request?
Applied CSS Which declarations win in the actual page and state?
Font resources Which files or variable-font ranges are configured for that family?
Loading result Did the intended resources load successfully for this browser visit?
Rendered face Which font does the browser report using for the inspected text?

Have the developer inspect those layers together. A successful file request alone does not establish that the inspected heading uses it. Likewise, a computed weight value records the style request without proving that a separate file with that weight was selected.

Check missing variants and synthesized weight

MDN’s font-synthesis reference explains browser synthesis of missing variants such as bold or italic and the controls that affect it. Review the actual font resources and CSS before describing the result as the font designer’s supplied bold face.

For a static font, verify the supplied styles and their configured mapping. For a variable font, verify its supported axes and ranges rather than assuming every family supports every requested weight. Do not force one site’s arbitrary numeric range onto another font.

A synthesized appearance is one possibility, not a diagnosis from a screenshot. A fallback family or overriding rule can also explain a mismatch. Keep the evidence for each possibility separate.

Make a bounded correction and inspect it again

After the owner approves a correction, update the relevant file mapping, field or shared reference within the defined scope. Preserve licensed source files and use the provider’s documented delivery requirements. Do not expand a one-heading repair into a site-wide replacement without reviewing its effects.

Recheck the same text, browser state and actual rendered face. Then inspect affected shared locations and representative narrow layouts. A different weight can change line wrapping and spacing even when the family name remains the same.

The font-variable replacement guide addresses shared family assignments. The font-size rules guide addresses sizing. Keep the accepted diagnosis and typography reference with the WordPress design handoff.

Key Takeaways

  • Start with one heading and a defined expected appearance.
  • Inspect selection, CSS, files, loading and rendered face separately.
  • Check fallback and synthesis before choosing a remedy.
  • Recheck affected shared locations after an approved correction.

Frequently Asked Questions

Does selecting Bold prove the bold font file loaded?

No. Inspect the applied style, available resources and browser’s actual rendered font together.

Does a variable font support every possible weight?

Verify that font’s documented axes and ranges. The presence of a variable-font control does not establish unlimited support.

Should I replace the whole font family to fix one heading?

Identify the failing layer first. A file mapping, override or other local issue may explain the mismatch without requiring a broader family change.

Archives