You're encountering a "Conflict" error when saving Adobe Fonts in Webflow, which usually indicates a mismatch or issue with your Adobe Fonts API token or selected project settings.
1. Check Your Adobe Fonts API Token
- Go to Adobe Fonts (fonts.adobe.com) and log in with your Adobe ID.
- Click your profile icon → My Adobe Fonts → API tokens.
- If you haven’t generated a token yet, create one.
- Copy the token and paste it into Webflow under Project Settings → Fonts → Adobe Fonts.
- Ensure you paste the correct, active token and there are no extra spaces.
2. Verify Project Name in Adobe Fonts
- In your Adobe Fonts account, check the web project name associated with your fonts.
- In Webflow, paste the exact project name (case-sensitive) into the Web Project Name field.
- A mismatch between the project name in Adobe and what you enter in Webflow often causes this error.
3. Ensure Font Project Includes Published Fonts
- Check that the Adobe Fonts web project includes fonts and is already published to Adobe’s CDN.
- If the project is empty or unpublished, Webflow cannot retrieve anything—triggering a conflict.
4. Try Disconnecting and Reconnecting
- In Webflow, remove the current Adobe Fonts API token, save the settings, then re-add it.
- Re-enter the correct token and web project name to refresh the connection.
5. Refresh Page and Clear Browser Cache
- Sometimes stale browser sessions cause this error.
- Clear your browser cache or open Webflow in an incognito tab and try adding the Adobe Fonts again.
Summary
To fix the Adobe Font "Conflict" error in Webflow, double-check that your API token is correct, your Web Project Name matches exactly, and your Adobe Fonts project is active and includes fonts. Remove and re-add the token if needed, and ensure your browser isn't caching old input.