67d481c6ce
* Noto Serif HK: aligned subsets with Noto Sans HK * Noto Serif JP: Aligned subsets with Noto Sans JP * Noto Serif KR: Aligned subsets with Noto Sans KR * Noto Serif SC: Aligned subsets with Noto Sans SC * Noto Serif TC: Aligned subsets with Noto Sans TC |
||
|---|---|---|
| .ci | ||
| .github | ||
| apache | ||
| axisregistry | ||
| catalog | ||
| cc-by-sa | ||
| lang | ||
| ofl | ||
| ufl | ||
| .gitattributes | ||
| .gitignore | ||
| .gitmodules | ||
| AUTHORS.txt | ||
| CODE_OF_CONDUCT.md | ||
| CONTRIBUTING.md | ||
| CONTRIBUTORS | ||
| README.md | ||
| to_production.txt | ||
| to_sandbox.txt | ||
| TRIVIA.md | ||
Google Fonts Files
This project mainly contains the binary font files served by Google Fonts (fonts.google.com)
The top-level directories indicate the license of all files found within them. Subdirectories are named according to the family name of the fonts within.
Each family subdirectory contains the .ttf font files served by Google Fonts, plus a METADATA.pb file with metadata for the family (such as information on the project designer(s), genre category, and license - learn more) and a DESCRIPTION.en_us.html with a description of the family in US English.
The /catalog subdirectory contains additional metadata, such as profile texts and portrait/avatar images of font designers, and this is open for contributions and corrections from anyone via Github.
The /axisregistry subdirectory contains metadata for the GF Axis Registry, containing information on variable font axes that can be found in the collection, including experimental axes.
Bug Reports and Improvement Requests
If you find a problem with a font file or have a request for the future development of a font project, please create a new issue in this project's issue tracker.
Contributor Code of Conduct
However you choose to contribute, please abide by our code of conduct to keep our community a healthy and welcoming place.
Self Host Fonts Available From Google Fonts
Since all the fonts available here are licensed with permission to redistribute, subject to the license terms, you can self-host using a variety of third-party projects.
One popular service is Fontsource, which offers bundled NPM packages.
Local installation package managers
For Linux, macOS, FreeBSD, or HaikuOS you can also use fnt, to install single fonts. For RPM, DEB based systems, feel free to try the linked URLs for individual fonts. Others can also use the webservice.
Download All Google Fonts
You can download all Google Fonts in a simple ZIP snapshot (over 600MB) from https://github.com/google/fonts/archive/main.zip
Sync With Git
You can also sync the collection with git so that you can update by only fetching what has changed. To learn how to use git, Github provides illustrated guides and a youtube channel, and an interactive learning lab. Free, open-source git applications are available for Windows and Mac OS X.
License
It is important to always read the license for every font that you use. Each font family directory contains the appropriate license file for the fonts in that directory. The fonts files themselves also contain licensing and authorship metadata.
Most of the fonts in the collection use the SIL Open Font License, v1.1. Some fonts use the Apache 2 license. The Ubuntu fonts use the Ubuntu Font License v1.0.
The SIL Open Font License has an option for copyright holders to include a Reserved Font Name requirement, and this option is used with some of the fonts. If you modify those fonts, please take care of this important detail.
Source Files
Source files for each family are often available from the designer, or from github.com/googlefonts
These fonts are usually the result of collaborative projects, where you are invited to discuss issues with the designers and even contribute to their ongoing development.
When customizing or remixing fonts, please do contact the designers to understand what they might need in order to include your improvements.
Most of all: Enjoy the fonts!
– The Google Fonts team