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.

  • Szymon Zurek commented
    31 Jan 07:39am

    I can't convice all clients to sign up with Webflow. Some want to have their own hosting. Building websites with the CMS is so much faster. PLEASE just let us have the option to export static pages.

  • Pataka Spacek commented
    16 Sep, 2018 11:42am

    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!

  • Rene Lopez commented
    4 Sep, 2018 02:03pm

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

  • Filip Moerman commented
    4 Sep, 2018 11:47am

    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.

  • Eryc da Silva commented
    28 Aug, 2018 04:29am

    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.

  • Brandyss Adams commented
    5 Aug, 2018 12:59pm

    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 :(

  • Michael Garske commented
    29 Jul, 2018 02:09am

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

  • Alexander Ayers commented
    27 Jul, 2018 02:57pm

    I need this so much... Please Webflow team

  • Jesper Fagerlund commented
    24 May, 2018 07:28pm

    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.

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

    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. 

  • Mac Dechmann commented
    23 Feb, 2018 05:08pm

    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!!!!!

  • Dexter commented
    19 Feb, 2018 09:37pm

    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"

  • Loan Depot commented
    30 Oct, 2017 09:12pm

    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.

  • Carly B. commented
    23 Oct, 2017 08:45pm

    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.

  • Dario Berrebi commented
    22 Oct, 2017 12:22pm

    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!

  • Hector Muñoz Huerta commented
    22 Sep, 2017 10:38pm

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

  • Russ Taylor commented
    19 Aug, 2017 08:24am

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

  • Vangelis trikoupis commented
    8 May, 2017 10:08pm

    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

  • Amit Koren commented
    2 May, 2017 09:31pm

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

  • Forrest O commented
    21 Mar, 2017 02:42pm

    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.

  • Load older comments
  • and 243 more