Export CMS Based Content

Add ability to export CMS based sites as static sites, across all CMS items.

  • Jason Zucchetto
  • Dec 16 2016
  • Nov 5, 2018

    Admin Response

    Our goal is to create a managed CMS solution that's easier to maintain for us, our users, and their clients. Converting the CMS to static assets removes those benefits so we are unlikely to build this feature.

    11/05/2018 Update:  We've shipped the ability to export all CMS content to a CSV file. (This went live in October!) Read more on our updates page.

  • Andrew Reaney commented
    January 18, 2017 01:26

    For me, this one goes far above any other wishlist item.

  • Pascal Olivet commented
    January 26, 2017 09:18

    Dear Webflow, I think it is a huge mistake not to consider this request.

    Although I agree Jason's solution here to export CMS content as static sites is terrible (sorry buddy), is is important to be able to get CMS content outside Webflow. This is better explained in the 2 Merged ideas.

    Why is this so important:

     - CMS content is often created in the Editor, by the final user of the site - so most of the time the final client, not the web designers)

     - It is not a normal user behaviour to create a backup of content added to CMS

     - No CMS export locks all the content in Webflow, which is a HUGE concern, both from a commercial point of view (you can't leave Webflow without risking losing your content) and from a technical point of view (Webflow is the sole entity storing that content - if there's a serious bug, there's nothing you can do...). For that second point, it also means Webflow is responsible for the content, so from a business perspective, you guys become responsible for it and I hope you are prepared for the risk this creates...

     - Because of the 3 point here-above, it's also a commercial hurdle for Webflow, as it will defer people from choosing your services if they can't keep control on content. But maybe this your strategy is not to go after content heavy site owners... I don' know...

     - For the same reason, it creates a commercial hurdle for us designers/agencies to get new customers onboard.

    I personally am not a trained designer, but a business and marketing person. I worked over 10 years in really small to very large e-businesses at management level, and I can assure you that on the Web, content is king! So don't hold it as hostage, but allow there creators to save it outside your platform! It is critical that it can be saved on another database!

     

    Thanks

  • Zen Kick commented
    January 26, 2017 13:59

    I think this is a huge mistake as well.

     

  • Sergie Magdalin commented
    January 26, 2017 18:07

    Pascal and David, I updated the admin response above, clarifying that Webflow will not hold your CMS content hostage. You will be able to export it as a CSV if you wish to make a backup or move it to a different platform. 

  • Pascal Olivet commented
    January 27, 2017 11:18

    Thanks for the update Sergie.

  • Chad Richardson commented
    February 02, 2017 21:08

    I would love a static CMS export to be available as well.  Utilizing the CMS can make the design process easier, faster, and more organized.  Many clients already have private hosting and they don't want to pay additional monthly fees.

  • Hector Muñoz Huerta commented
    February 11, 2017 13:24

    I purchased a CMS template to build a small portfolio site, I just needed to use the CMS functionality to generate about 8 portfolio pages or so. I had to use some site downloading tools and spend hours fixing the code to be able to host the site somewhere else because CMS hosting is too expensive for a small site that only used CMS functionality once.

    Not only did I lose time, you lost a hosting costumer.

  • Forrest O commented
    March 21, 2017 14:42

    Hosting seems like a separate product. CMS features seem to be included in the designer cost. Once I paid to use the designer, I expected my dynamic lists and pages to be included in the "Prepare Full Zip" build.

  • Amit Koren commented
    May 02, 2017 21:31

    I agree being able to export would be very valuable.  Any updates on timing for this?

  • Vangelis trikoupis commented
    May 08, 2017 22:08

    The benefits of CMS aren't directly correlated with the benefits of exporting this CMS dynamic content as static.

    The markup that is generated is static and far more easier for Webflow to release to us, just as we are now downloading a zip of the site, rather than have us try and workaround saving static instances of the pages.

    The benefit for Webflow is that I am able to choose any template to work with, even pay for CMS features but at the end of the day choose to export the static content as I only used the dynamic list for my static needs.

     

    Please reconsider this, it shouldn't be much work to do this

  • Russ Taylor commented
    August 19, 2017 08:24

    I vote to consider this option. Rather than a database consider using a flat file system.

  • Hector Muñoz Huerta commented
    September 22, 2017 22:38

    CMS hosting is too expensive if you only want to use the feature to build a static site that won't be constantly updated.

  • Dario Berrebi commented
    October 22, 2017 12:22

    Hi there, 

    Do you have any updates on this? Even just to give us a timeframe...

    I need to move export a good 60+ CMS items to a new webflow project, this would save me so much time!

  • Carly B. commented
    October 23, 2017 20:45

    Incredibly important. I don't want to be locked in to the initial structure I make for a collections list if I end up needing to make large changes to its structure over time. Being able to export data currently input into one collection list and import it back into another with an updated structure without having to do so one item at a time is a game changer.

  • Loan Depot commented
    October 30, 2017 21:12

    I cannot express enough how amazing it would be if we were able to design using the CMS engine and export statically. My team (corporate Instructional Design and Visual Communications) used Webflow to build a proprietary learning and product support site and we have had to do some workarounds to overcome the 100 static page issue, by using multiple projects, which creates way more work and planning than if we had the aforementioned. The CSV file does nothing to solve the issue we are experiencing.

  • Dexter commented
    February 19, 2018 21:37

    Just wanted to say the reason this is good for business is because if you have someone say "well..if I use this platform it will be difficult to get my content off later. Better skip it and try something else."

    The better argument is "you can switch if you need to, but if you stay on, there are certain benefits to webflow's CMS you can't get anywhere else"

  • Mac Dechmann commented
    February 23, 2018 17:08

    Yes it must be a solution to export it, if u want to host the page on your own server. u can export it to xml and integrate a xml reader in the exportet page-script, or integrate a api-viewer in the exported script. whatever, i need the CMS content in the exported scripts!!!!!

  • Jörn Klawan commented
    May 14, 2018 09:24

    What about a fully functional website export with with the cms items inside a json file? Just as static as before but you can design using collections and the site is working just as it does on staging domain. 

  • Jesper Fagerlund commented
    May 24, 2018 19:28

    We are currently building 3 sites for customers, who are daringly accepting to keep it on Webflow. Their no 1 and only mayor concern: what if Webflow ceases to exist? What about our content?  This is a no brainer.

  • Alexander Ayers commented
    July 27, 2018 14:57

    I need this so much... Please Webflow team

  • Michael Garske commented
    July 29, 2018 02:09

    This will be incredibly useful so I can create my CMS in webflow and backup externally.

  • Brandyss Adams commented
    August 05, 2018 12:59

    Where are we at with this? It's nearing 2 years backlogged...

    I'd like to point out that neither myself, nor my clients, really care to take their business elsewhere...BUT end user content, if not imported via CSV file, has no backup otherwise. For instance, my current client has an EXTENSIVE appointment database (over 1700 items in this year alone) and so all of these appointments created within the CMS are fragile and precarious...that's not a selling point and I am already shaking if the question ever becomes: can I download my data?

    Surely, I don't yet know how to explain to them that what goes in cannot come out :(

  • Eryc da Silva commented
    August 28, 2018 04:29

    I really wish there was a CMS to static HTML solution for those who want to go "server less". 

    Honestly wouldn't mind paying a higher rate as a Designer to be able to do this.

  • Filip Moerman commented
    September 04, 2018 11:47

    I also want that ability, because we make event pages for our clients and it would be good for them to have an excel sheet with all the data inside.

  • Rene Lopez commented
    September 04, 2018 14:03

    It would be great to have this. Meanwhile, I have to save each page individually.

  • Pataka Spacek commented
    September 16, 2018 11:42

    Adding my vote with a big "PLEASE!" Our product database contains information created, for various reasons, solely within Webflow (categories, edited descriptions, manual discounts etc.) It is crucial that we can export this content, for purposes of backup, reverse-updating the external database, creating printed material etc.). Sadly, even the Webflow API Tester tool seems not to be available any longer... :-( Thank you!