The removing of Webflow from exported code is a Pro feature, yet the JavaScript file is named Webflow. How is this considered true white labelling if I plan on sending my zipped code to a client? Why is the Webflow name still on what you claim is “white labelled” code?
As far as I know there isn’t any white labeling of Webflow code available. The most you can get out of the box is to remove the made in Webflow comments from the HTML.
Once you’ve exported the code you can change the names of the files and change there references in the HTML.
It is different from the Whitelabel option per project, which costs an additional $5/$10 monthly. This removes or let you customize the frontend CMS Editor logo.
I am a paying pro member and was surprised to find references to Webflow still technically in the code upon export (in the various references as noted by @AlexN). So my only option is to manually remove webflow and the references to achieve complete white labelled code?
The white label feature has to do with the CMS right? So why should it matter if webflow is in the js file if you are hosting it on webflow? You cannot export a CMS site so this seems a bit confusing.
@DFink, he meant it on the level of exporting his site out and for his client to use. And he expected that if he were to use white-labeling, he should not see “Webflow” anywhere in file names or in code.
The Whitelabel term officially refers to the customization of the CMS Editor Branding, where your collaborators login to edit the content on your projects. This costs additional $5-10/mo on top of the hosting plan depending on the account type.
This feature is available to these users:
CMS hosting
Basic hosting
Remove Webflow from published/exported code
This is similar to Whitelabel, but we are not calling it Whitelabel to avoid confusion. Let’s call it a “Pro” option.