3 Replies Latest reply on Nov 16, 2017 6:23 AM by donaldw90835656

    How to exclude marketplace fonts..

    JvR from Eindhoven Level 1



      Is there an option to exclude marketplace fonts from the list on Typekit? So that I just see the fonts that are included in my CC-subscription?




        • 1. Re: How to exclude marketplace fonts..
          Liz, Typekit Support Adobe Employee

          Hi Jacco,


          The My Library tab on typekit.com is only the font families that are included in your current subscription (plus anything you have already purchased from Typekit Marketplace).


          Screen Shot 2017-04-24 at 11.54.38 AM.png


          For font families the have a mix of subscription and Marketplace weights and styles, you can also use the filtering menu on the family page to show only the fonts you can currently sync, add to a website, or both.  Here's an example from the Nimbus Sans family page: there are 43 fonts available, but I can filter the page to the 15 I am able to sync right now.


          Screen Shot 2017-04-24 at 11.56.35 AM.png

          Screen Shot 2017-04-24 at 11.56.38 AM.png


          I am sorry that this wasn't more clear on our website, and have shared your comments with our team so we can work on improving it.  I hope that this helps; let me know if you have any other questions,

          -- liz

          1 person found this helpful
          • 2. Re: How to exclude marketplace fonts..
            JvR from Eindhoven Level 1

            Hello Liz,


            Thanks! This solved my problem.



            • 3. Re: How to exclude marketplace fonts..

              This is helpful for the Browse method, but when using search, there's no similar filter available. I often use the search function (as I imagine most subscribers do frequently), and there's no way to quickly exclude fonts that cannot be synced. That same filter array from the Browse path should be available in Search as well. The addition of the Marketplace is a good move to support type foundries, but it has made using the Typekit service far more messy than it was previously.