Ai Identifying Ghost Classes Due to Webflow Variable Limitations

·Feb 15, 2026 09:06 PM·

Hi Lumers, Can anyone share any experiences in dealing with this issue: My Ai says these are ghost classes "The core issue is that Webflow doesn't allow retroactive variable connections — each variable has a unique hidden ID, so even recreating variables with the same name doesn't fix it. Relume It's a known limitation of how Webflow handles variable references internally" What did I do wrong? Surely you should be able to delete variables?

3 comments

· Sorted by Oldest

Matt J.
·
·
Steve B. happy to jump in here. I would need a bit more context and probably a webflow read-only link in order to better understand what might be going on here as it could be several things. But to answer the one direct question about deleting variables - deleting any of the color scheme 1 variables will throw errors, so in short, no its best not to delete the variables that exist in the style guide to start. You can add variables, and after an import of a style guide, you could start modifying some of the other color scheme variables sure. Like maybe you decided to not have color scheme 6 anymore, you could delete those and there would be no issue. However, because of how color schemes work and are setup in Webflow, color scheme 1 variables are a foundational piece and should not be deleted to avoid errors.
Jack G.
·
·
Does that go for projects that don't use relume as well? That you shouldn't delete base color variables?
Matt J.
·
·
Jack G. yeah probably - if the variables were used in the project and you delete them it could cause the some unwanted errors. In most cases though Webflow gives you a way to restore that variable and reconnect it all in one click, so its not as destructive as deleting the base variables prior to an import using our app in our style guide.