How do i remove TypeKit?

Design help Webflow integrations
1

I’m trying to remove Adobe Typekit from our site. Adobe fonts API token has been removed but the resources are still being loaded. Not sure what else i can do?

2

Hey Brian,

That’s a common (and frustrating) caching issue with Webflow integrations. Removing the API key is the right first step, but the font resources can be ‘sticky’ because they might be referenced elsewhere or cached on the server.

Here’s a systematic checklist to fully remove them:

  1. Check Project Font Settings: Go to your Project Settings > Fonts tab. Make sure the Adobe Fonts integration is disconnected there and that no fonts from Typekit are listed under the “Custom Fonts” section.

  2. Audit Your Styles: Go back into the Designer and check your global styles (like All H1 Headings, All Paragraphs, etc.). Ensure none of them are still set to use a Typekit font. If one is, switch it to a different font.

  3. Full Republish (The Key Step): Publish your site to all domains again (e.g., both the .webflow.io and your custom domain). This step is crucial as it forces Webflow’s servers to regenerate the site’s CSS and clear out old dependencies from the CDN.

  4. Clear Browser Cache: After republishing, clear your own browser cache or check the site in an incognito window to ensure you’re not seeing a locally cached version.

Usually, step #3 is the one that solves it. Let me know if that clears it up for you.

3

Thanks for responding @Lenox_Roy! Unfortunately I have carefully gone through all 4 of those steps and the font is still there.

  1. The only fonts under Project Settings are fonts I’ve uploaded
  2. I have verified all of my css classes are using my new fonts (only a handful)
  3. I’ve republished to all domains.
  4. I’ve both cleared cached and tried incognito mode.

I’m at a loss :frowning:

4

Thanks for the detailed follow-up, and my apologies that the standard checklist didn’t resolve it. That’s a frustrating situation to be in, especially after you’ve done all the right steps. Let’s dig deeper.

When the usual suspects in the Webflow UI are cleared, the culprit is almost always hiding in one other place: custom code.

Sometimes, a script or a <link> tag for the font is added directly to the site’s code, which bypasses the standard Font settings in the Designer. Could you check two specific areas for this?

  1. Global Custom Code: Go to Project Settings > Custom Code. Look carefully in both the Head Code and Footer Code sections for any line of code that contains the words typekit or use.typekit.net.

  2. Page-Specific Custom Code: If there’s nothing in the global settings, check the custom code settings for your individual pages (especially the homepage) inside the Designer’s Page panel.

If there’s nothing in the custom code either, the next step would be for me to take a direct look. Would you be able to share your project’s read-only link? That would allow me to use the browser’s developer tools to see exactly what is calling that font resource.

We’ll get to the bottom of this. These things are usually just one stubborn line of code hiding in plain sight.

5

Double-check the site’s custom code (Project Settings > Custom Code and Embed elements in Designer) , leftover <link> or @import calls to use.typekit.net can keep loading it even after the integration’s gone. Had to strip those manually on a client build before it cleared.

6

I’ve looked through the custom code for the site and each page. For the most part it’s empty and I’m not seeing anything that should link to TypeKit specifically. Here is a readonly link

7

Okay, I’ve had a chance to go through the read-only link you shared.

You were right—your own checks were spot on. After a full search, I can confirm the Typekit code is not in your Project Settings, Page Settings, or any HTML Embeds.

This points to a rare but known Webflow issue: a “ghost integration.” Essentially, even though you disconnected Adobe Fonts in the UI, a reference to it has remained stuck on Webflow’s servers. A standard republish can’t clear this kind of residual data.

At this point, the only solution is to contact Webflow Support, as their engineers are the only ones who can purge this from your project’s backend.

When you contact them, I’d recommend mentioning that you’ve already confirmed there’s no custom code calling the script and that it appears to be a server-side “ghost integration.” Using that specific term might help them resolve it faster.

Hope they get it sorted for you quickly!

8

Thank you for taking the time to confirm it! Was starting to feel like I was loosing my mind. I’ll contact Webflow support.

9

@Vaultside
If a font is referenced in any style within your site, Webflow will load the font at build time. The solution I always use to resolve this issue is turn off CSS per page if on, so I can get a monolithic CSS file I can open in dev tools when I inspect on a published site and then to a search for the font name. Each found occurrence will indicate what style uses the font. Then you can locate those in the designer and change them accordingly.