Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form
Trusted by teams at
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form
Integrate your client's Adobe Fonts API token into their project to make their Adobe font web projects available for that project.
Note: We’re transitioning to Workspaces, and are in the process of updating our content. Visit the Workspaces blog post to read more about these updates and changes, or visit our updated lesson about how to integrate Adobe Fonts into a specific site. You can also learn how to check if your account is on Workspaces.
In a separate lesson, we show you how to integrate Adobe Fonts into your Webflow accounts to make your Adobe Fonts available in all your projects. However, if you’re building a website for a client, and you want to use Adobe Fonts for that project, it’s wiser to create an Adobe Fonts API token specifically for the client and integrate it into the project.
Among the many reasons to adopt this approach is the fact that Adobe will begin requiring clients to have their own Adobe accounts starting in 2020. Learn more about Adobe Font licensing [↗]. Another important reason is that your client will own their own font kits, and if they want their project transferred, the handoff will be much easier.
To integrate Adobe Fonts into any project, you need a site plan or a paid account plan.
If your client has a Creative Cloud account (Adobe ID) [↗], ask them to send you their API token. If they don’t, ask them to set up their own free account, then send you their token.
Alternatively, you can offer to set it up for them using their own credentials and then hand it over to them. That way, they get to keep control of their fonts, without you needing to manage those fonts within your own account.
If you want to set up the account yourself:
If you want your client to set up their own account and send you the API token, send them the following instructions:
Now, that you have the API token, you can paste it into your Webflow project’s Adobe Fonts integration settings.
If you wish to remove an API token from a project, delete the token and press "save token."
Once you’ve connected your Adobe account to your project, the Adobe web project that has all the fonts for this project will appear below your Adobe Fonts settings. Select the web project and save the changes.
To remove a web project from your project’s font list, choose "None" and save changes.
In the Designer, you’ll have full access to any fonts and font weights you added through your Adobe web project. Just browse for the font you need in the Style panel (S) → Typography section. The fonts list is ordered alphabetically.
If you’re using your own Adobe Fonts API for client sites, you’ll need to migrate client fonts to their own Adobe accounts before Adobe updates their terms of use on 1 January, 2020.
Learn more: About Adobe Font licensing [↗]
To comply with the new Adobe Fonts terms, you'll need to add separate Adobe Fonts API tokens for each client project. Follow the guide above to:
Sometimes Adobe Fonts integrations can fail to sync with Webflow and can usually be resolved in a few small steps.
Common issues:
Must know
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.
For most of these cases, check the following:
Go to the Project settings of the project you are troubleshooting. Open the Fonts settings page and scroll to the Adobe Fonts section. Make sure that the API token is added and saved.
Visit the Adobe Fonts API tokens [↗] page and confirm that the Adobe Fonts API Token is 100% correct.
Go to your project’s Fonts settings page and check that the currently selected web project (the one with a blue border) is the correct one.
