---
title: Still Using PostScript Type 1 Fonts? Really?
description: Still Using PostScript Type 1 Fonts? Really? We originally posted this article in 2011 and it's even more relevant today!
---

[Technology Guidance for Business Leaders | Ntiva Blog ](https://www.ntiva.com/blog)

# [Still Using PostScript Type 1 Fonts? Really?](https://www.ntiva.com/blog/still-using-postscript-type-1-fonts)

 Written by [Ben Greiner](https://www.ntiva.com/blog/author/ben-greiner) | Feb 28, 2018 5:00:00 AM

Are you still using postscript type 1 fonts?

We originally posted this article in 2011 and it's even more relevant today (in 2018)!

2021 UPDATE: [Adobe is Ending Support for Type 1 Fonts](https://creativepro.com/adobe-is-ending-support-for-type-1-fonts/)

Font issues among Creative Professionals can range from minor annoyances (Warning: Helvetica conflict at startup) to major problems that cost thousands of dollars (Oops: 10,000 books were affected by text reflow).

We work with more than 500 heavy font users and we’re confident we can fix — or explain — every font issue that’s presented to our Support Desk. However, we’ve noticed a growing font problem that has one very clear solution. Unfortunately, it’s a solution few seem eager to follow.

As Thomas Phinney from Adobe pointed out in 2005: 

People expect their fonts to continue to work forever. But when thinking about Type 1 eventually going away, it’s worth keeping in mind the value that customers have gotten from their Type 1 fonts over the years. What other software do you have that you bought in the late 1980s that still works today? It’s amazing that these things have had such a long lifespan. 

Of course, a lot of people don’t think of fonts as software, but that’s really what they are: little plug-ins to your system software. 

If you’re experiencing ongoing font issues, especially in Mac OS X 10.6 Snow Leopard, take a look at your fonts and see if they are PostScript. Most of the font issues we see today are related to using PostScript Type 1 fonts from the early to mid-1990s (15-20 years ago. A century in techno-years!)

If you can prove you own the font, it’s sometimes possible to contact the font developer and ask for a free PostScript update. This might solve the problem. If you don’t own the font then the only option is to buy new — and buy OpenType. There are many advantages to buying OpenType (see [OpenType Q&A](https://helpx.adobe.com/fonts/using/adobe-type-resources-faq.html) for details).

Replace your PostScript fonts with [OpenType](https://www.adobe.com/products/fontfolio.html). Your workday will become more enjoyable and you'll love your fonts again. :)

***NOTE**: Microsoft stopped supporting Type 1 fonts in Office 2013 for Windows and Office 2016 for Mac. Upgrading to OpenType is the best — and only — solution.*

[View full post](https://www.ntiva.com/blog/still-using-postscript-type-1-fonts)

```json
{
  "@context" : "http://schema.org",
  "@type" : "BlogPosting",
  "author" : {
    "@type" : "Person",
    "name" : "Ben Greiner"
  },
  "dateModified" : "2024-07-31T15:04:13.551Z",
  "datePublished" : "2018-02-28T05:00:00Z",
  "headline" : "Still Using PostScript Type 1 Fonts? Really?",
  "image" : {
    "@type" : "ImageObject",
    "height" : 403,
    "url" : "https://go.ntiva.com/hubfs/PostScript-Fonts-1.png",
    "width" : 800
  },
  "mainEntityOfPage" : "https://www.ntiva.com/blog/still-using-postscript-type-1-fonts",
  "publisher" : {
    "@type" : "Organization",
    "logo" : {
      "@type" : "ImageObject",
      "height" : 60.0,
      "url" : "https://go.ntiva.com/hubfs/Logo%20Default%20NO%20TAGLINE.png",
      "width" : 237.15253
    },
    "name" : "Technology Guidance for Business Leaders | Ntiva Blog"
  }
}
```