With custom typefaces being all the rage in web development right now, I seem to come across at least one person every day who complains about the lack of font-embedding support in Google’s Chrome browser.

Chrome, being built on the WebKit rendering engine, which already has support for @font-face, likewise also already supports embedding fonts. The reason font embedding doesn't work 'out of the box' in Chrome is because it was disabled, citing a potential security vulnerability.

Screenshot of Google Chrome rendering a custom font inside a sample HTML page, from the A List Apart article "CSS @ Ten: The Next Big Thing"

Despite being disabled by default, the feature is still fully functional, and can be enabled easily. To enable web fonts, run the Chrome executable with the 'enable-remote-fonts' switch. For example, in Windows [XP] your shortcut will probably look something like this:

"C:\Documents and Settings\USER\Local Settings\Application Data\Google\Chrome\Application\chrome.exe" --enable-remote-fonts

Obviously you'll have to modify the path to suit your particular installation, but if you're modifying an existing shortcut or link to chrome that part should already be done for you. The important bit, in Windows shortcuts at least, is that the switch (the bit after the double-hyphen) goes outside the double quotes which enclose the path and filename.

If you're a linux or unix user, switches should be second nature to you. And if you're an OS X user, you're on your own. I have no idea how that works.

Update (2009.09.28 21:05):

Paul Irish wrote "Chrome and @font-face: It’s coming!" on his blog. He mentioned that in OS X, simply use Terminal to launch Chrome:

/Applications/Chromium.app/Contents/MacOS/Chromium --enable-remote-fonts