I’m using the new Finsweet Extension / Remove Duplicate Styles and it is taking a loooong time to process even the smallest duplicate classes and it’s also causing webflow to crash.
As an example, I have 12 duplicate classes that have been processing for 24 hours and has crashed Webflow three times. I’ve retried another class with 2 duplicates and it has been running for over 4 hours so far.
It appears to go through every component and every section of every page used on the site - regardless of whether the class is even used on that page at all.
At this rate I will never remove all the duplicates from my site. Is there a way I can work around it?
Hi @Hiredgoon
Try use Webflow’s Native Duplicate Class Cleanup first, Webflow now has a built-in duplicate style tool that is: Faster, Safer, Much more stable
Open Style Manager, Click Filter then Show Duplicates. Merge manually starting with utility classes first. This often removes 60–80% of duplicates instantly.
Then use Finsweet only for edge cases.
You can also break the job into micro sessions. Instead of selecting many classes, remove one duplicate group at a time. Wait for it to finish, refresh Webflow Designer, then do the next. Never batch process multiple duplicates.
You could also try disable components temporarily. Components massively slow this tool. Temporary workaround, duplicate the site, convert components to regular elements, right click component then detach instance, run duplicate cleanup, rebuild components afterward if needed, this can reduce processing time by 80%
Also try work from smallest pages first. If you have; landing pages, legal pages, static pages, open one small page and run cleanup, let it finish then move up to bigger CMS pages. Webflow loads less DOM and therefore faster scanning.
Also make sure to publish before running the tool. Surprisingly this helps. Always save, publish, reload designer then run duplicate cleanup. It stabilizes memory usage.
1 Like
Thanks Jesse.
In the end it was much faster to go through all the unused classes and delete them manually, and then to use the Finsweet Extension tool to visualise what can be manually managed. I’m just so surprised that the extension tool goes through every element of every page, rather than just the places where the classes exist…
Thanks @Hiredgoon for the update!
