How to Create a Webflow CMS Content Freeze Archive Before a Redesign

A Webflow redesign is much safer when you first save a testable copy of what is public today. For a CMS-driven site, that means more than exporting a few articles: preserve the public routes, the rendered collection-item pages, and the assets that make them usable. You need a published Webflow URL and a place to keep the archive; you do not need to change DNS or replace the live site.

ExFlow’s Webflow exporter is a practical starting point because it can collect a published site as static HTML, CSS, JavaScript, media, and individual CMS pages. The important boundary is this: a static archive preserves what the browser receives; it does not reproduce services that need Webflow at request time, such as native form delivery, Ecommerce checkout, site search, protected pages, or the Webflow Editor.

1. Define the freeze date and the reader-critical routes

Write down the date and time of the freeze, the published domain, and the redesign branch or project it protects. Then make a short route list before you export. Do not start with every possible URL; start with the pages a reader, customer, or stakeholder would notice first.

For a typical Webflow CMS site, include the home page, the collection listing, and three collection items:

This sample is a release check, not proof that every URL is correct. If the archive is intended for legal retention, a client handoff, or a complete migration, expand the route list accordingly. The point is to have a named set you can test again after the redesign begins.

2. Export the published version, not the work-in-progress

Use the live custom domain or published .webflow.io URL. A content-freeze archive should represent what visitors could actually fetch on the selected date. In ExFlow, enable the files required for a real static copy: HTML pages, CSS, JavaScript, and images/media. Turn on Export all pages when you need the crawler to use the sitemap and internal links to reach public routes.

The Webflow exporter documents that it exports public pages, collection-item pages, generated stylesheets, runtime and custom scripts, and media referenced from the published site. It can write pages with .html extensions when that suits the destination host. Save the resulting ZIP with a stable name, such as site-freeze-2026-11-05/, rather than overwriting an earlier archive.

This is deliberately different from a design backup. A design backup helps you reopen the project in the builder; a static content freeze is the browser-visible reference you can inspect without relying on the original builder project. If your goal is a larger CMS migration, the route-audit method in this Webflow static-hosting guide is a useful next layer.

3. Record what the static copy cannot do

Create a plain EXCEPTIONS.md file next to the archive. This prevents a reviewer from mistaking a good-looking static copy for a full replacement of every server-backed feature.

Use this simple template:

Freeze date: 2026-11-05 Source: https://example.com Static checks: home, /articles/, three named article routes Working client-side behavior: navigation, tabs, sliders, lightboxes Replacement needed: contact form endpoint, search, checkout, protected pages Owner for each replacement: __________________

Webflow interactions can remain useful in a static export when their runtime and page data ship with the page, but verify them instead of assuming. Forms deserve a separate owner and an actual send test. If you are exporting Framer rather than Webflow, the same principle applies; this Framer form check shows why a form needs an explicit destination after static hosting.

4. Open the archive locally, then test it on a staging host

Unzip the archive and first open the home page. This quick pass catches obviously missing CSS, fonts, or relative paths. Then deploy the unchanged folder to a staging location that behaves like the intended host. A Git branch, an S3 bucket, FTP staging folder, or a static-host preview all work; ExFlow can also sync exports to Git, S3, FTP, or its hosting path.

Run the named routes from step 1 on desktop and on a narrow mobile viewport. For each one, check:

1. The URL resolves to the intended page rather than the live Webflow domain.
2. Navigation and internal links remain inside the archive.
3. Images, fonts, downloads, and background media load without broken requests.
4. Any slider, tab, lightbox, or animation you rely on still works.
5. The page title, description, canonical URL, and share image match the archive’s purpose.

If a page works locally but not on staging, look for host-specific route behavior first. A host that needs index.html folders will not behave the same as one serving literal .html files. Keep the export option and the host’s routing convention aligned. For a more exhaustive deployment review, see how to QA a Webflow static export before changing hosting.

5. Make the archive useful to the redesign team

Keep the ZIP, EXCEPTIONS.md, and a short route receipt together. If you use Git, commit the exported directory in a clearly named branch or repository so the freeze has a date and a visible change history. Avoid editing the freeze to make it prettier; it should stay a faithful reference. Put proposed redirect rules, revised copy, and replacement integrations in a separate redesign workspace.

When the redesign is ready, repeat the three-item sample against the new site. Compare the old and new routes, not just the home page. That makes missing archive content, altered slugs, and dropped media visible before visitors find them. The related workflow for exporting a Webflow CMS site to static HTML before a redesign is useful when you need a broader migration checklist.

Keep the freeze small enough to verify

A Webflow CMS content freeze archive is successful when a teammate can open the saved public routes, understand what is intentionally absent, and trace the copy back to a date. Start by running a Webflow export in ExFlow, test the named route set on staging, then store the ZIP and exception note before the redesign changes the reference point.

ExFlow also has dedicated Framer and Squarespace exporters, but keep this archive platform-specific: a Webflow content freeze should be tested against Webflow’s published output and your chosen host’s routing rules.