Whitelabel on assets src url (upload images, javascript, frameworks)

I think the whitelabel option should rewrite src


<img src="https://uploads-ssl.webflow.com...


<img src="https://uploads-ssl.mydomain.com...

or something more generic like

<img src="https://uploads-ssl.webassets.com (an alias like webform.io to hide webflow brand)


The same for the Webflow object inside the main JS app.

is this something doable?



  • Andrea Brai
  • Feb 1 2018
  • Shipped
  • Mar 28, 2019

    Admin response

    Hi all - this is live: now when you enable whitelabeling for a site, your assets will live at a generic, unbranded URL (something like https://assets.website-files.com/randomfilename, instead of https://uploads-ssl.webflow.com/randomfilename).

    For existing projects, be sure to republish that site to ensure your images serve at an unbranded URL.

  • Calvin Ulery commented
    13 Oct, 2021 02:44pm

    How do you enable whitelabeling?

  • Jabe Brown commented
    29 Sep, 2021 12:38am

    This doesn't really solve the problem. If I have an asset that others link to, all the link juice flows to webflow, not my site. This is an SEO nightmare.

    This should absolutely be a top priority to implement.

  • Christian Gilbang commented
    2 Feb, 2021 05:22pm

    Is this still available?

    I have a pro account with the Editor white labeling enabled. But my assets still display as 'uploads.weflow...' in the URL.

  • Jose Macías Fernández commented
    29 Nov, 2020 02:45pm

    Are we still unable to use our own URLs for assets?

  • Martin Soler commented
    10 May, 2019 01:58pm

    We need our own URLs. It is cosmetically better to have non-webflow url but it doesn't solve real issues such as whitelisting of sites through strict firewalls, such as China or corporate firewalls. 

  • Windward Studios commented
    28 Mar, 2019 10:06pm

    Maybe I'm missing something here. What/how is this set up? 

    Can we specify the "unbranded" URL? If so, how?

    thanks - dave

  • Martin Soler commented
    15 Mar, 2019 03:36pm

    This would also help solve hosting speed in China. If a URL has received the right authorizations in China it can be cached there. But as our content is hosted on a webflow URL and Webflow doesn't have an ICP code our site is extremely slow in China. 

  • Miek Thompson commented
    6 Mar, 2019 02:56am

    Please incorporate this along with to FTP feature!

  • Gareth Higham commented
    28 Feb, 2019 06:12pm


  • Robbie Lo commented
    28 Feb, 2019 05:53pm

    This would mean we could do a lot of great things with CDNs and speed things up a lot 

  • Andrew Tokeley commented
    30 Jan, 2019 09:07pm

    Webflow, you are doing so much right, but...

    I can understand why hosting these files on your own domain might is easier, but it's a really unprofessional look for anyone building a site with downloads or the like.

    Can you provide some feedback, so we can set expectations with clients or even decide whether Webflow is the right fit?


  • Windward Studios commented
    20 Jan, 2019 02:30pm

    Please do this in conjunction with WEBFLOW-I-1057

  • Martin Volek commented
    1 Nov, 2018 12:12pm

    When the white label for assets will be implemented? Thanks!

  • Micheal Reno commented
    16 Aug, 2018 03:59am

    For those who export their static sites, you can have all Webflow references removed automatically by using https://jinglebell.io ! And obviously the assets file paths will be custom because you're using your own hosting under your own domain!

  • Gareth Higham commented
    12 Aug, 2018 07:58pm

    Yes. for sure. 

  • Julianne Aziz commented
    14 Jun, 2018 04:17pm

    If i am paying for white-label service than I should have it covered all the way! PLEASE have this be fixed ASAP. There is a reason why we are doing white labeling on our end! 





  • Michael Naylor commented
    31 May, 2018 07:45am

    As suggested in https://wishlist.webflow.com/ideas/WEBFLOW-I-1173 the file name should be a simple extension of the route domain: https://domain.com/files/file.example or a clean, simple subdomain: https://files.domain.com/file.txt, https://assets.domain.com/file.txt ext

    Please set it up in whichever way that allows files to be password protected/exclusively accessible through login of a password protected page.

  • Oliver Mcquitty commented
    30 May, 2018 08:43am

    Couldn't agree more!

  • Gabriel Fray commented
    27 Mar, 2018 06:21pm

    +1 very important!!!

  • Andrea Brai commented
    27 Mar, 2018 06:08pm

    hi guys! any news about this idea? It shouldn't be so hard to develop... please consider adding it on top of roadmap! thanks

  • Load older comments
  • +58