Bring Mac OS X Style Font Rendering to Windows with GDI++

happy guy

Even though I’ve never used Apple’s famed desktop OS, there’s one thing about Mac OS X that has always made love it – the font rendering. A lot of people don’t get what’s with all the fuss about fonts, but for me it’s always been the little things that matter.

Ever since ClearType was introduced a few years into Windows XP, font rendering on Windows has undergone a huge facelift. ClearType is quite cripsy and sharp, but that’s exactly what I don’t like about it. The fonts look like thin swords cutting through a piece of fabric that is your PC screen. Compare that to the font rendering on OS X, which is like this creamy blending thing that creates more impact on your eyes and…..okay I’ve no idea how to describe it, so let me just say it looks tons better! Here’s a side-by-side comparison of the two -

windows vs os x font rendering [source: lifehacker; click on image to view in full size]

Notice the difference?

  • Yes? Welcome to the camp! I don’t know which of the two you like, but for me it’s easily OS X.
  • No? It’s probably awesome you can’t make out the difference because then you won’t have to like one or the other!

Anyway, for those of you who do like the OS X rendering but are using Windows instead, there’s an easy way to get the former on your PC!

Enter GDI++. This tiny app, when activated, kills Windows’ ClearType font rendering and uses its own OS X-style rendering, which is based off the original gdi++.dll project.

To get started, download the GDI zip file from the link provided at the end of this post, extract the folder anywhere on your PC, and double-click the gditray.exe file to start the utility.

gdi

If the rendering doesn’t change immediately, right click on the gditray icon on your system tray, make sure ‘Enable’ is enabled, and click on ‘Apply Now’. Now, sit back and enjoy the magic!

gditray

If you want to make it start automatically with Windows, make a shortcut of the gditray.exe file and put it in the Startup folder.

gditray startup

Should you want your ClearType back, simply exit the gditray.exe file and everything will be back to normal.

Do note that GDI++ doesn’t work everywhere. For example, I can’t get it to work on Google Chrome and uTorrent, two of my favorite apps, for the love of it. The, err, chrome of Chrome gets rendered in gdi++, but not the webpages. Firefox has no problems.

Also, if you don’t run the gditray.exe file as administrator (right click > Run as administrator), it’ll naturally fail to render areas that require administrative privilege.

Overall though, I’m pretty impressed with GDI++. It does what it says, and it does that really well. Previously, the only way for me to enjoy the OS X style rendering was by using Apple’s Safari browser, which is otherwise a very clunky software on Windows. However with GDI++, I can enjoy the rendering system wide without taxing my processor in any manner (the gditray.exe process uses only about 1-3 MB of memory while running and almost zero CPU usage). Really, small things like this go a long way in making me a happier soul!

======================

Download GDI++ – Make Windows fonts look as smooth as Mac OS X fonts (look out for ‘Download GDI++’ in step 1).

download gdi

All credit for me discovering GDI++ goes to the awesome Lifehacker readers, with the app itself being covered at LH way back in March, 2009! Read the entire comment thread on Lifehacker here.

Ad

  • Pingback: Tweets that mention Bring Mac OS X Style Font Rendering to Windows with GDI++ | PC Tonic -- Topsy.com

  • http://www.gouthaman.wordpress.com/ Gouthaman

    Nice. This is something I’ve been searching for a lot lately. Gonna use GDI++, thanks heaps for sharing.

  • Oalexander

    It is wonderful. No more Window-watching without it. Note, it also comes with three presets, marked in Japanese meaning probably strong, medium and light. (right click tray icon, “Use preferences …”) There is also a “Tuner” (gdixxTuner.exe) shipping with it, which I find somewhat to awkward.Somebody with time may want to play with it, but back up original “ini” file before! Else, the prog is a no-brainer: I love it!

    • http://pctonic.net/ Ashutosh Mishra

      The program definitely has language problems, but it works with the default settings and that’s all that matters :)

  • Oalexander

    It is wonderful. No more Window-watching without it. Note, it also comes with three presets, marked in Japanese meaning probably strong, medium and light. (right click tray icon, “Use preferences …”) There is also a “Tuner” (gdixxTuner.exe) shipping with it, which I find somewhat to awkward.Somebody with time may want to play with it, but back up original “ini” file before! Else, the prog is a no-brainer: I love it!

    • http://pctonic.net/ Ashutosh Mishra

      The program definitely has language problems, but it works with the default settings and that’s all that matters :)

  • http://www.twitter.com/HotdogWithSauce Hotdog With Sauce

    I know I’m very late on sharing this with you, Ash but I figure better late than never.

    If you’re having problems getting GDI++ to render in Google Chrome, this is currently “normal action” by default. Google haven’t allowed this type of activity by default within the browser. Instead, if you add the command “–no sandbox” to the end of the program’s target path (check the properties for chrome.exe and you will find the target line there), it will allow fonts to be rendered on web pages. Be warned though, using this command line isn’t recommended for security purposes.

    Hopefully sometime soon Google will allow Chrome to safely allow this type of font rendering natively.

    • http://pctonic.net/ Ashutosh Mishra

      I have indeed tried the Chrome command line switch, and while it worked, I’d rather stay with my Windows fonts that remove sandboxing from Chrome! In fact, GDI++ is quite wonky with Windows Aero turned on, so I have removed it altogether. The Windows fonts look bad only when you’re using something with the OS X fonts, so I have uninstalled Safari too. Hopefully someone picks up the gdi++.dll project and sorts out all the bugs and stuff, but for now I am perfectly happy with ClearType fonts.

      Nevertheless, thanks for the comment! :)

  • http://www.twitter.com/HotdogWithSauce Hotdog With Sauce

    I know I’m very late on sharing this with you, Ash but I figure better late than never.

    If you’re having problems getting GDI++ to render in Google Chrome, this is currently “normal action” by default. Google haven’t allowed this type of activity by default within the browser. Instead, if you add the command “–no sandbox” to the end of the program’s target path (check the properties for chrome.exe and you will find the target line there), it will allow fonts to be rendered on web pages. Be warned though, using this command line isn’t recommended for security purposes.

    Hopefully sometime soon Google will allow Chrome to safely allow this type of font rendering natively.

    • http://pctonic.net/ Ashutosh Mishra

      I have indeed tried the Chrome command line switch, and while it worked, I’d rather stay with my Windows fonts that remove sandboxing from Chrome! In fact, GDI++ is quite wonky with Windows Aero turned on, so I have removed it altogether. The Windows fonts look bad only when you’re using something with the OS X fonts, so I have uninstalled Safari too. Hopefully someone picks up the gdi++.dll project and sorts out all the bugs and stuff, but for now I am perfectly happy with ClearType fonts.

      Nevertheless, thanks for the comment! :)

  • Voyager

    Hi, to put GDI++ working with Chrome WITHOUT disabling sandboxing, just go to te .INI of GDI (right-click on systray GDI icon -> Open INI), search for the field “[AllowModule]” and add CHROME.EXE
    And that’s it, it will “force” chrome to accept the rendering.

    Best regards,
    Pedro

    • http://pctonic.net/ Ashutosh Mishra

      Thanks for the tip! :)

  • Voyager

    Hi, to put GDI++ working with Chrome WITHOUT disabling sandboxing, just go to te .INI of GDI (right-click on systray GDI icon -> Open INI), search for the field “[AllowModule]” and add CHROME.EXE
    And that’s it, it will “force” chrome to accept the rendering.

    Best regards,
    Pedro

    • http://pctonic.net/ Ashutosh Mishra

      Thanks for the tip! :)