Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Fix the driver behind crashes, sound loss and screen glitches3Repair Windows errors before they cause bigger problemsTo use a custom web font across browsers, declare it with @font-face, list compatible font files in order, then use its declared family name in a regular font-family stack. For modern sites, WOFF2 is usually the best starting format; add older formats only if your audience still uses browsers that need them.
Declare the font with @font-face
A valid @font-face rule needs a font-family name and a src descriptor pointing to the font resource. The name is a label you choose; use that same name in your page’s font stack.
@font-face {
font-family: "My Web Font";
src: url("my-font.woff2") format("woff2"),
url("my-font.woff") format("woff");
font-weight: 400;
font-style: normal;
}
body {
font-family: "My Web Font", system-ui, sans-serif;
}Browsers try the sources in declaration order and use a format they support. Keep the system fonts at the end of the stack so text remains readable if the custom font cannot load. See MDN’s @font-face reference for current descriptor and source syntax.
Which font formats do you need?
For current browser support, WOFF2 is generally the best web-delivery default. It compresses more efficiently than older WOFF and OpenType formats and is broadly supported by modern browsers. WOFF can serve as a fallback for older browsers in your support target; include still older formats only when your audience requires them.
#1 Best Overall
- HTML CSS Design and Build Web Sites
- Comes with secure packaging
- It can be a gift option
| Format | When to consider it |
|---|---|
| WOFF2 | Default choice for modern browsers; efficient compression and broad current support, according to MDN. |
| WOFF | Fallback where older browser support is part of the project’s requirements. |
| EOT | Legacy Internet Explorer support through IE8, as described in the historical browser matrix in SitePoint’s tutorial. |
| SVG font | Legacy iOS Safari 3.2–4.1, as described in the SitePoint tutorial. |
| TrueType (TTF) | Legacy Android default browser support, as described in the SitePoint tutorial. |
Those older browser versions are historical targets, not a checklist every current website needs to satisfy. The SitePoint tutorial’s matrix reflects the browser generations it addresses; use it only if your support policy includes those versions.
Order sources for the browsers you support
A source list can include a locally installed face before remote files, followed by URLs in a deliberate order. A browser uses the local face if it finds it; otherwise it can fetch a remote resource. Format hints help the browser identify the file type.
Rank #2
- Brand: Wiley
- Set of 2 Volumes
- A handy two-book set that uniquely combines related technologies Highly visual format and accessible language makes these books highly effective learning tools Perfect for beginning web designers and front-end developers
@font-face {
font-family: "My Web Font";
src: local("My Web Font"),
url("my-font.woff2") format("woff2"),
url("my-font.woff") format("woff");
font-weight: 400;
font-style: normal;
}If your compatibility policy truly includes the legacy formats in the table, add those files to the source list as needed. Do not ship them automatically: each extra asset adds hosting and maintenance work, and modern browsers generally do not need that historical coverage. MDN documents the source descriptor and format hints.
Describe weight, style, and character coverage
The descriptors in @font-face tell the browser which variation a file represents. Declare the weight and style accurately, then request the matching values where you use the family. If you provide separate regular, bold, or italic files, define a face for each variant rather than labeling every file as regular.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallOutdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchfont-weightidentifies the weight, such as400for regular.font-styleidentifies normal, italic, or another supported style.font-stretchidentifies the face’s width variant when relevant.
Use unicode-range when a font file supplies only a subset of characters. For example, a face intended only for the ampersand can specify unicode-range: U+0026;. This can avoid downloading glyphs a page does not need, but only when your font files and usage are subsetted accordingly. See MDN’s descriptor documentation.
Make cross-origin font files load
Fonts loaded from a different origin than the stylesheet or site are subject to cross-origin restrictions. If your CSS points to a font hosted on another domain, configure the font server to allow the relevant cross-origin request with HTTP access controls (CORS). A font URL that works when opened directly may still fail when a browser requests it from your site.
Also configure the server to return a suitable MIME type. MDN lists font/ttf for TrueType, font/otf for OpenType, font/woff for WOFF, and font/woff2 for WOFF2. Check the browser’s network and console panels if the face does not appear: they can help distinguish a missing file, CORS denial, or server response problem. See MDN’s font-face guidance.
Reduce font-loading cost without hiding text
Web fonts add bytes and may delay the moment a page’s text appears in its intended typeface. Keep delivery purposeful: send only the character sets and weights the site uses, compress files, and avoid loading many font families. Always retain a system fallback so content remains legible when a font is slow or unavailable.
- Subset fonts for the languages and characters your pages actually need.
- Limit the number of families and weight variants requested.
- Choose a deliberate font-loading strategy that balances fast visible text with the intended design.
- Test on the browsers and devices important to your audience, including slow connections.
- Review readability and accessibility, and confirm the font license permits web embedding.
Self-hosting or using a hosted font service?
These approaches trade control for convenience. A hosted service may reduce setup work, while self-hosting gives you direct control over the font files and delivery configuration.
| Approach | Advantages | Trade-offs |
|---|---|---|
| Self-host font files | Control over assets, hosting, and configuration. | You must manage server settings, bandwidth, file formats, and licensing. |
| Hosted font service | Less setup around serving font files. | Your site depends on the provider and its service availability and terms. |
Whichever route you choose, check cross-origin behavior, load only the variants you need, and verify that the license allows your intended web use. Google Fonts is one hosted option; the earlier SitePoint tutorial also describes Font Squirrel’s generator as a way to create alternative formats and CSS from a font file. Confirm current service capabilities and font licensing before relying on either.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
