Home >Web Front-end >CSS Tutorial >How to Prioritize Local Fonts in @font-face Rules to Avoid Unnecessary Downloads?
@font-face is a powerful tool for integrating custom fonts into web pages. However, it can be frustrating when the browser downloads the font even if it is already installed on the user's system.
When you define a @font-face rule, you specify multiple source files. The browser will typically download all these files and install the font. By default, locally installed fonts are not taken into consideration.
To prevent unnecessary downloads, you can prioritize local files in your @font-face rule. Here's the syntax:
<code class="css">@font-face { font-family: 'MyFont'; src: local('MyFont'), url('MyFont.ttf'); }</code>
In this example, the browser will first check if the font named 'MyFont' is locally installed. If it is, the local version will be used. Otherwise, the browser will download and install the font from the specified URL.
The method described above is a simple way to prioritize local files. However, in some cases, the browser may still download the font even if it is installed. To address this, you can use a more elaborate approach:
<code class="css">@font-face { font-family: 'Green Sans Web'; src: local('Green Web'), local('GreenWeb-Regular'), url('GreenWeb.ttf'); }</code>
This rule defines two local names for the font: 'Green Web' and 'GreenWeb-Regular'. When resolving the font, the browser will first check for either of these local names. If a match is found, the local font will be used. If not, the browser will resort to downloading the font.
By following these techniques, you can ensure that your @font-face rules prioritizes local fonts, reducing unnecessary downloads and enhancing the user experience.
The above is the detailed content of How to Prioritize Local Fonts in @font-face Rules to Avoid Unnecessary Downloads?. For more information, please follow other related articles on the PHP Chinese website!