This article needs to be updated. Please update this article to reflect recent events or newly available information.(September 2015)
The following tables compare support for different font formats and support for CSS3 font resources for a number of layout engines. Web fonts were initially defined (but later dropped) from CSS2, then added into CSS3. The specification is supported by an increasing number of web browsers.
Rather than the names of web browsers and HTML to PDF converters, the names of the underlying engines are used. Some of the software and online converters that use the various engines are listed below.
Values indicate the level of support in the most recent version of the layout engine, or (if a version number is given) in the specified version. Version numbers without any other value indicate the version at which the layout engine first fully supported the feature.
Indicates that the layout engine fully supports this property/element when valid values are used.
Indicates that the property/element is completely ignored.
Indicates that the property/element is understood, but that not all values are supported. Supported values are implemented correctly.
Indicates that the property/element is understood, but that it is not implemented correctly in all cases.
Indicates that the property/element is understood, but supported under an alternate name. May be incomplete or buggy.
Indicates that the property/element is no longer supported.
CSS3 specified a mechanism for downloading and displaying fonts within a web page.[spec 1] This table compare support for that mechanism. Note that Embedded OpenType (EOT)[spec 2] font download does not bring in the entire OpenType font and therefore, the most prominent feature of Open Type, ligature support, does not come with EOT. Trident before version 5.0 supports only EOT. EOT is not sufficient for smartfonts that rely on ligatures.