FontCreator 7.0 is a major new version, so owners of earlier versions will need to pay for an upgrade. The latest version adds several long-awaited features that will make this a must-have upgrade for keen font designers. Web Designers may be tempted to create their own fonts now that FontCreator supports the Web Open Font Format (WOFF) • Test Page (View in Firefox)
Professional users who need high-end features (highlighted by **), and Home users, will appreciate the improvements to their fonts that are now possible with automatic hinting. All users will benefit from the improved overview, extra features, bug fixes, and simplified interface.
Free help is available on the active support forum, even for the unregistered 30-day trial version. The glyph overview, the menus and several dialogues have been removed or reorganised so please take the time to study the interface changes before asking, “Where is the Format Menu?” Or “What happened to the Platform Manager?” Also check for Updates from the Help menu before reporting problems.
The help file is available online, so you can get a good idea about what features are available before downloading the free trial version (this exports a limited character set of A-Z, a-z, 0-9, just enough for testing the font).
Released 25th April 2013
Check for updates for Maintenance Releases
Download Page • Version Comparison Chart
Released 8th November 2011
FontCreator now uses Project files instead of working only with TrueType or OpenType fonts directly. Each project can have its own set of ruler guides, notes, OpenType feature script, and export settings. You can open TrueType or OpenType fonts as before, then save them as a project file before starting work, leaving the original files untouched. Select the desired Export Options before exporting your project as a TTF, OTF, or WOFF font file.

Use Export from the File menu to export the project to a TrueType or OpenType font or to a Web Font, choosing whether to include hinting and/or OpenType layout features. The default feature script includes some common features, but custom scripts can be saved with the project and used to add more features. See the next section on adding OpenType features. Exporting a font only takes a few seconds.
Users of PagePlus and DrawPlus who read this review may already be familiar with using OpenType features, because they have been supported since PagePlus X5 was released in October 2010. Until now, adding OpenType features to fonts created with FontCreator required third-party tools like VOLT or the OpenType Compiler. This was beyond the ability of many users.

FontCreator now has built-in support for scripts to add OpenType features. The built-in editor has line numbering, and can be customised to use a font and colours of your choice. The font size can also be zoomed directly using the mouse scroll-wheel. The Professional Edition (but not the Standard Edition) can import scripts from existing fonts, which lets you see how features are designed. This first release does not support all Layout Features yet, some fonts may generate errors, as shown above when importing a script from Adobe’s SourceSansPro.
Although there is a lot to learn about OpenType features, once you have created a script to suit your fonts, its a simple process to build an OpenType font from a TrueType version. If there are any syntax errors in compiling a script, the messages will help you to debug your script or fix the postscript names in your fonts to match the script. As with all coding, syntax has to be 100% correct — miss a semicolon, or use the wrong capitalisation, and the script will fail to run. Below are a few examples of features you might like to add. My scripts use meaningful postscript names to make them easier to read and edit — they will need editing if you want to use the postscript names generated by FontCreator. <Omit the comments in angled brackets>.
feature Ligatures liga { <Feature name and OpenType layout tag “liga”.>
lookup ligaSub; <Lookup table to use for this feature.>
} lookup ligaSub { <Feature definition is {within braces}, lookup table name, { begins lookup>
sub f f i -> ffi; <If user types f, f, i, then substitute ligature ffi.>
sub f f l -> ffl; <“f” and “l” are the postscript names for lowercase “f” and “l”.>
sub f f -> ff; <“ff” is the postscript name for the ligature “ff”.>
sub f i -> fi; <If user types f, i, then substitute ligature fi.>
sub f l -> fl; <If user types f, l, then substitute ligature fl.>
} <End of lookup table. Lookup table is within {braces}.>
feature ScientificInferiors sinf { <Feature definition, layout tag>
lookup ScientificInferiors;
}
lookup ScientificInferiors {
sub zero -> zero.sinf; <If user types 0 substitute a scientific inferior zero.>
sub one -> one.sinf; <“one.sinf” is the postscript name of the glyph to substitute.>
sub two -> two.sinf; <“two” is the default postscript name for digit 2.>
sub three -> three.sinf; <“.sinf” is the name suffix I chose for scientific inferiors>.
sub four -> four.sinf; <There is no rule that says one must use the feature tag as a suffix.>
sub five -> five.sinf; <It is just a convention that makes the script easier to understand.>
sub six -> six.sinf;
sub seven -> seven.sinf;
sub eight -> eight.sinf;
sub nine -> nine.sinf;
sub plus -> plus.sinf;
sub minus -> minus.sinf;
sub equal -> equals.sinf;
sub parenleft -> parenleft.sinf;
sub parenright -> parenright.sinf; <Substitute a subscripted right parenthesis.>
}
feature Ordinals ordn { <Feature name and layout tag.>
lookup Ordinals;
}
group @Ordinals [zero one two three four five six seven eight nine A.sups B.sups C.sups D.sups E.sups F.sups G.sups H.sups I.sups J.sups K.sups L.sups M.sups N.sups O.sups P.sups Q.sups R.sups S.sups T.sups U.sups V.sups W.sups X.sups Y.sups Z.sups a.sups b.sups c.sups d.sups e.sups f.sups g.sups h.sups i.sups j.sups k.sups l.sups m.sups n.sups o.sups p.sups q.sups r.sups s.sups t.sups u.sups v.sups w.sups x.sups y.sups z.sups]; <Glyphs to be followed by ordinals.>
group @Alphas [A B C D E F G H I J K L M N O P Q R S T U V W X Y Z a b c d e f g h i j k l m n o p q r s t u v w x y z]; <Glyphs to be used as ordinals.>
lookup Ordinals{
context (@Ordinals) @Alphas; <If alpha glyph follows a glyph in ordinals, then …>
sub 0 Super; <In the above context, use this lookup table.>
} lookup Super {
sub A -> A.sups; <If user types A after a digit or after an ordinal substitute superscript A.>
…. <Repeat sub line for A through to Z and a to z, and more if required, e.g. è ú etc.>
sub Z -> Z.sups;
sub a -> a.sups;
sub z -> z.sups;
}
This contextual lookup Ordinals feature first checks to see if a digit has been typed. If it has, then it checks to see if an alpha character is typed next. If not it does nothing, so 123 remains as usual. However if the user types 1s, the Ordinals feature superscripts the s. If the user continues to type “t” or any other alpha characters, they are all superscripted. However, as soon as the user types a space, or some punctuation, any following characters are normal again.
Ordinals in Adobe fonts (e.g. SourceSansPro) and Microsoft fonts (e.g. Calibri) are implemented differently. If the user types a digit or lowercase alpha character and the Ordinals feature is enabled, all are substituted with superscripts. You can decide how you want to implement this feature, but I recommend the former method because it means that the ordinals feature can be enabled as part of the paragraph style for body text, and then ordinals are automatic.
feature StylisticAlternates salt { <Feature name and tag.>
lookup StylisticAlternates;
} lookup StylisticAlternates {
sub asterisk -> [asterisk asteriskmath uni2051 uni2042 uni203B];
sub plus -> [plus uni2795 uni271A uni271B uni271C];
sub at -> [at uni260E uni260F uni2121 uni213B];
sub copyright -> [copyright uni2117 uniF000 estimated uni2139];
sub multiply -> [multiply uni2715 uni2716 uni2717 uni2718];
sub dagger -> [dagger uni2622 uni2623 uni26A1 uni2620];
sub daggerdbl -> [daggerdbl uni26A0 uni2691 uni26B0 uni26B1];
sub bullet -> [bullet uni204D uni2023 uni2767 uni2712];
sub circle -> [circle fullmoon waninggibbousmoon lastquartermoon waningcrescentmoon];
sub blackcircle -> [blackcircle newmoon waxingcrescentmoon firstquartermoon waxinggibbousmoon];
sub uni2600 -> [uni2600 sunrise uni26C5 uni2602 uni2603];
}
This feature requires intervention by the user. After selecting an asterisk, the user can choose from any of the five symbols from asteriskmath to Unicode character 273B, which is a Dingbat. If the user selects a plus sign they can choose from a different set of five cross-like symbols.
For each “sub” line the first glyph is repeated, which is Stylistic Set 0 (the original glyph), followed by five alternative glyphs for the user to choose from. You may add up to 99 Stylistic sets.
Web Fonts (WOFF format) are a compressed TrueType font format designed for embedding on web pages. They allow web designers the freedom to use fonts that are not Websafe since the fonts don’t need to be installed on the site visitors’ computers.
FontCreator 7 supports the WOFF format, and shows a preview of the font in your default web browser. If your browser supports OpenType features in CSS (Internet Explorer E10, Chrome12 or later, FF4 or later, and the Latest version of Safari), then this local HTML preview page can be used to test OpenType features without actually installing the fonts. You can quickly check that the features are working as intended, before finalising the OpenType features script and installing the OpenType version of the font for testing in Windows applications.

The above preview demonstrates some of the features in my own font Jivita Regular. By checking and unchecking the OpenType Features in the panel on the right, you can see how the features interact. For example, if fractions are enabled, Ordinals won’t work as expected, or Discretionary Ligatures will override Petite Capitals. The input text can be modified by typing (or by editing wofftest.js at your own risk), and the size changed from the font size drop list. The colour of the preview text can be changed, and some preset text samples can be selected from the Quick Pick drop list. Not all OpenType features are supported by CSS, but the preview is enough to test most common features.
FontCreator 7 can also open existing Web Fonts for editing. Use the Professional Edition to add OpenType features.
New to FontCreator 7 is the option to generate side-bearings for the font automatically. This may take some time on slower computers as a lot of processing is involved, but it only needs to be done once after editing the glyph outlines. Getting character spacing just right is one of the most time-consuming and difficult tasks when designing fonts. Kerning should only be done after finalising the side-bearings.
Professional font designers who are importing vector images into FontCreator from Adobe Illustrator or CorelDraw will find it well worth the extra price over the Standard Edition just for the time that this saves. Since they will have faster computers than mine, it should take only about 15 minutes to process a font. The default setting of 27 seems to give rather too much spacing in my limited tests. Try a value of 24 or 23 and see if that is better. Optical metrics are added to the undo history, so you can try progressively smaller or larger values before deciding on the value that suits your font.


Other fonts may need different values. I haven’t tested it much yet as it takes nearly 30 minutes to run on my PC.
Just leave the checkbox enabled and its done automatically on exporting fonts. Now your fonts will look better on screen at small sizes, without the spindly appearance cause by “dropout” where thin strokes disappear. Except for complex or large fonts, it takes only a few seconds, but it does increase the size of font files (in my tests by about 16-25%).
The glyph overview has been completely redesigned. A resizable panel on the left of the overview allows fonts to be filtered by glyph type or character set. Clicking the thumb button on the splitter will dock the panel when its not in use, and shortcut Ctrl L will show it again. Shortcuts Ctrl J and Ctrl K will display code-points in Decimal or Hex.
The Tab key will focus the panel even if it is closed, then the cursor keys can be used to display the previous or next character set. Glyphs can be grouped by Unicode blocks or by width, and sorted by glyph index, name, or width in ascending or descending order using the buttons on the Overview’s toolbar.
The Find function will locate a single glyph using its mapping or glyph name, or display a range of glyphs from their mappings, e.g. Find “58048-58090” will display the glyphs as in the screen shot. These are the mappings that I use for OldStyle numerals, Case-sensitive Forms, and Initial Capitals.
One of five tags will underline the glyph caption in a different colour. Right-click on a glyph in the overview to access the tag submenu.
Zoom in or out using shortcut keys (Numpad +/-) or the font size drop list on the toolbar. Sort by name, index, advance width, or side-bearings, in ascending or descending order.

A new Notes Toolbar (Shortcut F2) is a convenient place to record changes made, and list things to be done for each font project.
This is new, and replaces the Glyph Properties dialogue. Show/hide it with the F3 Shortcut. Use the buttons to set the postscript name from the glyph mapping code-point, or to set the code-point from the postscript name.
For a new blank glyph, use the “Select Unicode Character” button to select a code-point
from a list of Unicode Character Names for each Unicode Character set.
Some obsolete items have been removed and items on the Format menu have been moved. The Font Properties dialogue replaces the Format Settings dialogue. The Font Information dialogue replaces the previous Font Properties dialogue.

Released 8th November 2011
Beginners especially, but also experienced users, will like the new Free Draw tool.
This paintbrush allows users to paint lines of a fixed width with the mouse, holding
down the shift key to constrain strokes to horizontal or vertical straight lines.
Stop painting, momentarily release the shift key, and start painting again to change
direction. Click “Delete last stroke” to undo any errors, click “Convert to contours”
to complete the drawing, or dismiss the Free Draw dialogue to cancel.
The new contours can easily be joined with existing contours using the Professional Edition with the “Get union of contours” button. it is also possible using the Home Edition with the “Join contours” function on the right-click menu, but it is not nearly as easy.
After drawing the contours in one glyph it is possible to scroll to other glyphs using the toolbar left/right arrows, before converting the brush strokes to contours. This might be useful, for example, to use an existing glyph as a template to draw the contours in the right position and the right size before creating them in a new glyph or adding them to a different glyph, or for creating accents for use with composite glyphs.
The default text sample for the Test Font window now includes all of the glyphs that are added to a New Font by default. Right-click on the Test Font window to edit any of the samples, add new samples, or change the order of the list.
The help file for FontCreator 6.5 is still available online.
Released 13th October 2010
Released 25th March 2010
This latest minor update is free for existing users of version 6.0 so updating is recommended. Some bug fixes and a few minor improvements. Zooming with the scrollwheel is a great time-saver when editing glyphs, and the new optional tab bar will help some users who work with multiple fonts.
![]()
Released June, 2009
What users should notice with the new vector import is much greater speed, and fewer nodes than if tracing bitmaps. Because EPS and AI images are already vectors, there is much less processing to be done, so even a complex symbol will import in seconds. There are some limitations though — if illustrations contain intersecting contours, FontCreator won’t be able to interpret the contour direction, so some manual corrections may be needed. However, most font shapes should not present difficulties. Complex symbols are always likely to cause problems in fonts.
PDF is another format that uses vectors. Almost any illustration program can output curves to the PDF format. Just drag and drop them from Windows Explorer, or use the Import Image dialogue. Vector images will import directly if selected in the Import Image dialogue — bitmaps will show a preview with options to select grey threshold, smoothing, etc.
Drag and DropDrag and drop of multiple images files provides a huge productivity boost. No more task switching back and forth to an image program to copy the next glyph.
Drag a whole alphabet of single image files into glyph A, and take a break while FontCreator imports them one at a time into each adjacent glyph.
If they are high resolution bitmaps, you might have time for lunch, but if they are EPS, AI, or PDF files, you won’t even have time to make coffee.
In my test, it took about three seconds to import twenty-six PDF files. That compares to about five minutes for twenty six medium resolution bitmaps.
Although they are vector images, Windows Metafiles will be traced as bitmaps.
A background image can be used as a guide when drawing or editing similar glyphs. If you are making changes to the design of a glyph, it helps to have a record of the original design before you started editing it. You can now copy the current glyph to the background image with one click.
Released July, 2007
Released May 30, 2006
Released January 12, 2005
Released August 17, 2004
Released December 1, 2003