Integrate Adobe Fonts into a specific site

Integrate your client’s Adobe Fonts API token into their site to make their Adobe Font web projects available for that site.

We’re transitioning to a new UI, and are in the process of updating our Webflow University content.

In a separate lesson, we show you how to integrate Adobe Fonts into your Webflow Workspace to make your Adobe Fonts available in all your sites. But, if you’re building a website for a client and you want to use Adobe Fonts for that particular site, it’s wise to create an Adobe Fonts API token specifically for the client and integrate it into the site.

There are two reasons to adopt this approach:

Note: To integrate Adobe Fonts into any site, you’ll need a paid Workspace plan or paid site plan.

In this lesson, you’ll learn:

  1. How to get an Adobe Fonts API token
  2. How to integrate your API token into your site
  3. How to remove your API token from your site
  4. How to connect an Adobe web project to your site
  5. How to disconnect an Adobe web project from your site
  6. How to test your fonts in the Designer
  7. How to troubleshoot issues with the integration

How to get an Adobe Fonts API token

If your client has a Creative Cloud account (Adobe ID), ask them to send you their API token. If they don’t have a Creative Cloud account, ask them to set up their own free account, then send you their API token.

Alternatively, you can offer to set it up for them using their own credentials and then hand it over to them. This way, they’ll keep control of their fonts and you won’t have to manage those fonts within your own Creative Cloud account.

Set up the account yourself and get the API token

If you want to set up the account yourself:

  1. Create an Adobe Fonts account
  2. Create web projects with the fonts you want to use for your client’s site
  3. Visit the Adobe Fonts API tokens page and make a new API token
  4. Copy the API token

Ask your client to provide their Adobe Fonts API token

If you want your client to set up their own account and send you the API token, you can send them the following instructions:

  1. Create an Adobe Fonts account (if you don’t have one)
  2. Create web projects with the following fonts: [Provide the name of the fonts you want to use in their site]
  3. Visit the Adobe Fonts API tokens page and make a new API token
  4. Copy the API token and send it to me

How to integrate your API token into your site

Now that you have the API token, you can paste it into your Webflow site’s Adobe fonts settings. To add your API token to your site:

  1. Go to Site settings > Fonts tab > Adobe fonts
  2. Paste your Adobe Fonts API token into the field
  3. Click Save token

How to remove your API token from your site

If you want to remove an API token from your site:

  1. Go to Site settings > Fonts tab > Adobe fonts
  2. Delete the token
  3. Click Save token

How to connect an Adobe web project to your site

Once you’ve connected your Adobe account to your site through the API token, the Adobe web project that has all the fonts for your site will appear below the Adobe fonts section in Site settings.

To connect an Adobe web project to your site: 

  1. Go to Site settings > Fonts tab > Adobe fonts
  2. Select the web project you’d like to connect
  3. Click Save changes

How to disconnect an Adobe web project from your site

To remove an Adobe web project from your site:

  1. Go to Site settings > Fonts tab > Adobe fonts
  2. Select “None
  3. Click Save changes

How to test your fonts in the Designer

In the Designer, you’ll have full access to any fonts and font weights you added through your Adobe web project. 

You can find your Adobe fonts in the Style panel > Typography > Font. Your Adobe fonts can be found at the bottom of the fonts list, ordered alphabetically.

The Font dropdown is highlighted in the Typography section in the Style panel.

How to troubleshoot issues with the integration

Sometimes the Adobe Fonts integration fails to sync with Webflow. This can usually be resolved in a few small steps.

Some common issues include:

  • Fonts aren’t loading correctly in the Designer
  • Web projects aren’t loading correctly in Site settings
  • Web projects aren’t loading at all in Site settings
Important: Adobe Fonts are licensed through your Adobe Creative Cloud subscription. If you remove your web project from your Adobe Fonts library, or your Adobe account becomes inaccessible, your font selection might not load.
Note: Adobe’s network can take up to 10 minutes to update, so if you don’t see your web project, or updates in your web project, check back and refresh the page later. You can also disconnect the web project and reselect it to load the most updated information from Adobe’s network.

To troubleshoot these issues, check the following:

  • Verify that both Adobe and Webflow systems are up and running
  • ‍Verify that you’ve integrated the API token in the correct place
  • ‍Verify your Adobe Fonts API Token
  • ‍Verify that the correct web project is selected in your Site settings

Verify that Adobe and Webflow systems are up and running

Verify that you’ve integrated the API token in the correct place

Make sure you’ve added your Adobe Fonts API token to your site.

Verify your Adobe Fonts API token 

  1. Locate your Adobe Fonts API Token in Site settings > Fonts tab > Adobe fonts
  2. Visit the Adobe Fonts API tokens page
  3. Confirm that your Adobe Fonts API Token matches the API token you connected to your site

Verify that the correct web project is selected in your Site settings

  1. Go to Site settings > Fonts tab > Adobe fonts
  2. Check that the currently selected web project (the one with a border) is the correct one

Table of contents

Continue learning

Hmm…we couldn’t find any results for “search query”. Try a different search term or check out our community forum.

Search the forumReset the filter
Load more

Filter

Reset
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
Topics
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
Back to top