Documentation Ligatures

Sublime Text supports ligatures for symbols since build 3146. Build 3158 added options to the font_options setting to provide control over ligatures.


In the default configuration, Sublime Text will use ligatures for sequences of symbols within the ASCII range. The ligatures must be part of the clig, liga or calt OpenType tables of the font for them to be used. Additionally, the sequence of characters that compromise the ligature must all be part of the same token, as defined by the syntax being used to display the file.

To use ligatures from the dlig OpenType table, the font_options setting must have the string "dlig" added. The font_options setting also allows for disabling ligatures from the clig, liga or calt tables by adding the respective "no_clig", "no_liga" or "no_calt" strings.


If ligatures are not displaying, please check the following:

  • Check to see what unicode characters make up the ligature. Sublime Text currently only supports ligatures comprised from the following characters: !, ", #, $, %, &, ', (, ), *, +, ,, -, ., /, :, ;, <, =, >, ?, @, [, \, ], ^, _, `, {, |, }, ~.
  • Make sure Sublime Text build 3146 or newer is installed. If trying to use font_options to control ligatures, ensure build 3158 or newer is installed.
  • See if the ligatures appear when using the "Plain Text" syntax for the file. If so, the syntax is likely breaking the symbols into distinct tokens, preventing a ligature from being used.
  • If using Sublime Text on Linux, check and see what version of Pango is installed. Pango 1.38, released in 2015, is required to specify the font_options to control liagures.