Crate font_kit

source ·
Expand description

font-kit provides a common interface to the various system font libraries and provides services such as finding fonts on the system, performing nearest-font matching, and rasterizing glyphs.


use font_kit::canvas::{Canvas, Format, RasterizationOptions};
use font_kit::family_name::FamilyName;
use font_kit::hinting::HintingOptions;
use font_kit::properties::Properties;
use font_kit::source::SystemSource;
use pathfinder_geometry::transform2d::Transform2F;
use pathfinder_geometry::vector::{Vector2F, Vector2I};

let font = SystemSource::new().select_best_match(&[FamilyName::SansSerif],
let glyph_id = font.glyph_for_char('A').unwrap();
let mut canvas = Canvas::new(Vector2I::splat(32), Format::A8);
font.rasterize_glyph(&mut canvas,
                     Transform2F::from_translation(Vector2F::new(0.0, 32.0)),


font-kit delegates to system libraries to perform tasks. It has two types of backends: a source and a loader. Sources are platform font databases; they allow lookup of installed fonts by name or attributes. Loaders are font loading libraries; they allow font files (TTF, OTF, etc.) to be loaded from a file on disk or from bytes in memory. Sources and loaders can be freely intermixed at runtime; fonts can be looked up via DirectWrite and rendered via FreeType, for example.

Available loaders:

  • Core Text (macOS): The system font loader on macOS. Does not do hinting except when bilevel rendering is in use.

  • DirectWrite (Windows): The newer system framework for text rendering on Windows. Does vertical hinting but not full hinting.

  • FreeType (cross-platform): A full-featured font rendering framework.

Available sources:

  • Core Text (macOS): The system font database on macOS.

  • DirectWrite (Windows): The newer API to query the system font database on Windows.

  • Fontconfig (cross-platform): A technically platform-neutral, but in practice Unix-specific, API to query and match fonts.

  • Filesystem (cross-platform): A simple source that reads fonts from a path on disk. This is the default on Android and OpenHarmony.

  • Memory (cross-platform): A source that reads from a fixed set of fonts in memory.

  • Multi (cross-platform): A source that allows multiple sources to be queried at once.

On Windows and macOS, the FreeType loader and the Fontconfig source are not built by default. To build them, use the loader-freetype and source-fontconfig Cargo features respectively. If you want them to be the default, instead use the loader-freetype-default and source-fontconfig-default Cargo features respectively. Beware that source-fontconfig-default is rarely what you want on those two platforms!


font-kit is capable of doing the following:

  • Loading fonts from files or memory.

  • Determining whether files on disk or in memory represent fonts.

  • Interoperating with native font APIs.

  • Querying various metadata about fonts.

  • Doing simple glyph-to-character mapping. (For more complex use cases, a shaper is required; proper shaping is beyond the scope of font-kit.)

  • Reading unhinted or hinted vector outlines from glyphs.

  • Calculating glyph and font metrics.

  • Looking up glyph advances and origins.

  • Rasterizing glyphs using the native rasterizer, optionally using hinting. (Custom rasterizers, such as Pathfinder, can be used in conjunction with the outline API.)

  • Looking up all fonts on the system.

  • Searching for specific fonts by family or PostScript name.

  • Performing font matching according to the CSS Fonts Module Level 3 specification.


font-kit is licensed under the same terms as Rust itself.


  • An in-memory bitmap surface for glyph rasterization.
  • Various types of errors that font-kit can return.
  • Defines a set of faces that vary in weight, width or slope.
  • Encapsulates the information needed to locate and open the fonts in a family.
  • A possible value for the font-family CSS property.
  • The type of a font file: either a single font or a TrueType/OpenType collection.
  • A font face loaded into memory.
  • Encapsulates the information needed to locate and open a font.
  • Specifies how hinting (grid fitting) is to be performed (or not performed) for a glyph.
  • Provides a common interface to the platform-specific API that loads, parses, and rasterizes fonts.
  • The different system services that can load and rasterize fonts.
  • Various metrics that apply to the entire font.
  • Bézier paths.
  • Properties that specify which font in a family to use: e.g. style, weight, and stretchiness.
  • A database of installed fonts that can be queried.
  • Various databases of installed fonts that can be queried.