Add ability to export CMS based sites as static sites, across all CMS items.
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.
Guest comment on "18 Feb, 2022 09:12pm" contains a virus link. Site might have closed and owned by malicious people.
You can finally export CMS Based Content or static with Stacket: https://stacket.app/ . It allows you to continue to design your Website in Webflow, but export it somewhere else.
It's 2021 and we still need this update, as community that relies on Webflow it would be a great time saver having this feature.
Agreed. My client has a medium size business and their hosting and emails are all tied together with another provider. Why can we not just export these pages?
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.
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!
It would be great to have this. Meanwhile, I have to save each page individually.
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.
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.
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 :(
This will be incredibly useful so I can create my CMS in webflow and backup externally.
I need this so much... Please Webflow team
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.
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.
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!!!!!
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"
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.
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.
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!
CMS hosting is too expensive if you only want to use the feature to build a static site that won't be constantly updated.