Clean asset links: Host assets on a site's Custom Domain and don't prepend the names with number ID strings

It would be great if you need to link to an uploaded Webflow resource (ie. a PDF or other) and have it on your own domain and not have the file name be prepended so "pitchscript.pdf" does not change to "872384029387403298wajlhewuhf_pitchscript.pdf". Especially since people want to host with Webflow fully & not have to put it on an external server.

  • Gira Desai
  • Jul 26 2017
  • Pam Sykes commented
    21 Dec 00:31

    Adding a small voice to the chorus here: As others have said, it feels really unprofessional to be sharing download links full of randomly generated text. This is just one of way too many problems with Webflow's CMS. I would never recommend Webflow to anyone else at this point.

  • Julian Witzel commented
    22 Oct 22:58

    It's been 7 years now and there is not even a tag on this topic yet? Even though this idea has even been merged 4 times already? Could you guys please look into that?

  • Guidea Admin commented
    02 Sep 03:44

    I've just downloaded hundreds of image files from my webflow site and they all have a 25-character numerical prefix added. If I make edits and re-upload them will webflow add another 25 characters? This seems really bad for SEO. Do we know what the barriers are to fixing this issue? It's bananas that there are threads going back years asking for WF to respond.

    Last night I paid for a tool to help me remove all the prefixes and give them all nice SEO-friendly file names before it dawned on me that y'all are going to change the names as soon as I re-upload them.

  • Eemil Jussila commented
    21 Aug 08:37

    THIS IS CRUCIAL

    As others have pointed out, PDF files need to be hosted on different platforms (creating additional costs) to maintain clean asset links under the same familiar domain name. In addition, tracking data like file views is also challenging.

    I hope this will change soon, ideally becoming a standard feature without extra fees.

  • Gordon Tax commented
    02 Aug 20:26

    Please fix this! It looks really unprofessional to have the random string in front of the file name, and it's kinda ridiculous to have this limitation on a paid hosting plan.

  • Daniel Acosta commented
    25 Jul 09:49

    This is urgent, please solve this.

  • Yunan Xing commented
    16 Jul 15:09

    It's 2024, and this hasn't been actioned....🥲 Please implement this soon Webflow

  • Will commented
    11 Jun 05:53

    Surely this has to be actioned by now Webflow... every other platform out there has no issues with retaining the file name for the download. This is one of the first things clients ask to be changed once their site is up... to which I have to advise it can't be...

  • Nicolas Lassaux commented
    17 May 14:40

    This would be soo much simpler. Cleaning a website and having an optimized landing page is almost impossible because of that

  • Richenda Devereux commented
    11 Apr 09:15

    Please implement this!

    Clients use our site to discover new case studies and publications. We offer full versions via download links on cms pages, and I hate to think of the user experience for them finding these junk PDF filenames on their desktop. It looks unprofessional and they are less likely to re-share with their colleagues in that form.

  • Julian Witzel commented
    05 Apr 16:24

    Any updates on this?

  • Yeshai Lang commented
    25 Mar 07:44

    This can be done with some custom code. Embed the following script after the "Download File" button element:
    <script>

    document.getElementById('downloadButton').addEventListener('click', function() {

    var fileNameWithPrefix = this.getAttribute('data-file');

    var fileName = fileNameWithPrefix.substring(fileNameWithPrefix.indexOf('_') + 1);


    // Decode the filename to replace '%20' with actual spaces

    fileName = decodeURIComponent(fileName);


    // Create a temporary link element

    var link = document.createElement('a');

    link.href = 'path_to_download/' + fileName; // Replace 'path_to_download/' with your actual download path

    link.setAttribute('download', fileName); // Set the download attribute to specify filename

    link.style.display = 'none';

    document.body.appendChild(link);


    // Trigger the download

    link.click();


    // Cleanup: remove the temporary link element

    document.body.removeChild(link);

    });

    </script>

    And create a custom element set as a button:
    <button id="downloadButton" data-file="{{wf {&quot;path&quot;:&quot;file-to-download&quot;,&quot;type&quot;:&quot;FileRef&quot;\} }}" class="button">Download File</button>
    replacing {{wf {&quot;path&quot;:&quot;file-to-download&quot;,&quot;type&quot;:&quot;FileRef&quot;\} }} with the relevant field from your cms

  • Duck Design Studio commented
    19 Mar 20:54

    I just wanted to emphasize how important this would be for Webflow users. We're looking forward to this update!

  • Max Blum commented
    21 Feb 01:22
    It looks like someone created a custom code snippet to solve this problem in Framer... Is this being prioritized here at Webflow or should I start experimenting with Framer for my next client load?
  • James Allen commented
    14 Feb 08:50

    As an enterprise customer, it's disappointing to see this has been requested since 2017 and has not been addressed yet.


    Please add this to your roadmap. File names should not be prepended with a random string of characters, and we should have the option to have files under our own custom domain name.

  • David Yap commented
    04 Jan 08:51

    Need this one very badly. Cant be showing webflow or other domain other than our client domain.

  • Drew Norman commented
    November 08, 2023 16:37

    We need exactly what Kevin has described below. Ay updates on when this will be in beta would be highly appreciated.

  • Asociacion Victoria Kent commented
    September 21, 2023 22:03

    lo veo totalmente fundamental, esto me limita hacer mucho. Me parece muy poco profesional tener los archivos con ese dominio.

  • Kevin Martins commented
    August 31, 2023 16:08

    THIS IS CRITICAL

    Businesses need this functionality to link directly to PDFs customers frequently access. We need the following features:

    • Asset URLs need to be customizable and come from our custom domain rather than the CDN domain. This is necessary for SEO, and security concerns (Customers might question wether the asset really belongs to the business if the URLs don't match).

    • Assets need the ability to be replaced whilst maintaining the same URL. Imagine posting the Asset link to external sources and then having to make a revision to the asset. Now you have to go and replace all the extrernal source links. (# of Assets × external sources × revisions and it starts getting ridiculous).

  • Brahim Sliti commented
    August 30, 2023 15:26

    Hey! New update since my last post on 22nd May: We were so disappointed in my company about this issue so we decided to build this simple and free tool https://cleanassetlink.com to have this issue solved, it's live now and working so well!!

  • Load older comments
  • +612