FreeType is a software font engine that is designed to be small, efficient, highly customizable, and portable while capable of producing high-quality output (glyph images). It can be used in graphics libraries, display servers, font conversion tools, text image generation tools, and many other products as well.
Note that FreeType is a font service and doesn't provide APIs to perform higher-level features like text layout or graphics processing (e.g., colored text rendering, ‘hollowing’, etc.). However, it greatly simplifies these tasks by providing a simple, easy to use, and uniform interface to access the content of font files.
Please note that ‘FreeType’ is also called ‘FreeType 2’, to distinguish it from the old, deprecated ‘FreeType 1’ library, a predecessor no longer maintained and supported.
The following is a non-exhaustive list of features provided by FreeType.
FreeType provides a simple and easy-to-use API to access font content in a uniform way, independently of the file format. Additionally, some format-specific APIs can be used to access special data in the font file.
The design of FreeType is based on modules that can be either linked statically to the library at compile time, or loaded on demand at runtime. Modules are used to support specific font formats, or even new glyph image formats!
FreeType was written with embedded systems in mind. This means that it doesn't use static writable data (i.e., it can be run from ROM directly), and that client applications can provide their own memory manager and I/O stream implementation. The latter allows you to easily read from ROM-based, compressed or remote font files with the same API. Several stream implementations can be used concurrently with a single FreeType instance.
You can also reduce the size of the FreeType code by only compiling the modules you need for your embedded project or environment.
By default, FreeType supports the following font formats.
From a given glyph outline, FreeType is capable of producing a high-quality monochrome bitmap, or anti-aliased pixmap, using 256 levels of ‘gray’.
FreeType supports all the character mappings defined by the TrueType and OpenType specifications. It is also capable of automatically synthetizing a Unicode charmap from Type 1 fonts, avoiding painful ‘encoding translation’ problems common with this format (of course, original encodings are also available in the case where you need them).
The FreeType core API provides simple functions to access advanced information like glyph names or kerning data.
A full-featured and efficient TrueType bytecode interpreter. The engine is able to produce excellent output at small point sizes. This component has been extremely difficult to get right, due to the ambiguous and misleading TrueType specification. However, we now match the results of the Windows bytecode engine.
For those who don't need or want to use the bytecode interpreter for TrueType fonts, we developed our own automatic hinter module. It is also used by other scalable formats.
Due to its modular design, it is easy to enhance the library, providing additional format-specific information through optional APIs (as an example, an optional API is provided to retrieve SFNT tables from TrueType and OpenType fonts).
FreeType provides its own caching subsystem. It can be used to cache either face instances or glyph images efficiently.
A bundle of demo programs demonstrate the usage of FreeType; look for the ‘ft2demos-x.x.x’ archive (or ‘ftdmoxxx’ in case you are on a Windows platform) at the locations given here. ‘x.x.x’ (or ‘xxx’) gives the version number, for example ‘2.4.10’ or ‘2410’.
FreeType is written in industry-standard ANSI C and should compile easily with any compliant C or C++ compiler. We have even taken great care to eliminate all warnings when compiling with popular compilers like gcc, Visual C++, and Borland C++.
Apart from a standard ANSI C library, FreeType doesn't have any external dependencies and can be compiled and installed on its own on any kind of system. Some modules need external libraries (e.g., for handling fonts compressed with gzip or bz2), however, they are optional and can be disabled.
All patents related to the TrueType bytecode interpreter have expired since May 2010. More information regarding this topic is available at our patents page.
Last update: 2-Jul-2013