Rendering

Where to find it

1. Open your project.
2. Click Rendering in the project sidebar.

Every team member can open Rendering. Only team admins see the Delete repository files button.

How it works

Each time you publish, WCH fetches your pages from Webflow, rewrites them into static files, and stores the result as your staging build. Rendering is the list of everything in that build: HTML pages, and the stylesheets, scripts, images and other files they use.

The list has two parts:

• New pages: pages in your source sitemap that WCH has not built yet. This section only appears when there are some. Each row shows the page path and its Webflow URL.
• Existing pages: everything WCH has already built, shown as a folder tree. Click a folder to expand it. Large folders load in batches; click Load more at the bottom of a folder to see the rest.

Each existing row shows:

• Name: the page or file name.
• Source URL: a link to the page on your staging site.
• Uploaded: how long ago WCH last built it.
• Kind: HTML for pages, Folder for folders, and the file type for everything else, such as CSS or JS.

Finding a page

Type in the Search by name or URL field at the top. The list narrows to matching pages and files, and every folder in the results opens so you can see each match. Clear the field to go back to the full tree.

Publishing selected pages

You can rebuild a handful of pages without running Publish all pages.

1. Tick the checkbox next to each page you want. You can tick existing pages and New pages together.
2. A bar appears showing how many pages are selected. Click Publish selected.
3. WCH shows "Publishing selected pages..." and rebuilds those pages on your staging site.

Things to know:

• Staging only. Publish selected updates your staging site. It does not send anything to your destinations. Deploy from the Dashboard when staging looks right.
• HTML pages only. Checkboxes appear on HTML pages. Files, sitemap.xml, robots.txt, and pagination pages such as /blog/page/2/ cannot be selected. Pagination pages are rebuilt with the page they belong to.
• One publish at a time. Publish selected is disabled while a publish is running. WCH also refuses it while a production deployment is running, with the message "A production deployment is in progress. Wait for it to finish before publishing to staging."
• Caching applies. If caching is on, WCH can skip a selected page that has not changed in Webflow since its last build. See Cache.

Page details

Click any page or file to open its details panel on the right. It has three tabs.

Configure

Shows where the page came from and where it lives:

• Source: the Webflow URL WCH fetched.
• Staging URL: the page on your staging site.
• Last imported: when WCH last built it.
• Local path: the file path inside the build, for example /about/index.html.
• Type: the file type.

These fields are read-only. To change where a page is written, see Output path overrides.

Versions

Every time WCH builds a page, it saves a copy as a new version. The Version history list shows each one with when it was created and its file size. The ticked row is the version your staging site serves.

• View: opens that version's HTML in a new tab.
• Switch versions: click a row to make it the active version. WCH replaces the page on your staging site with that copy and shows "Version activated successfully".
• + Update: rebuilds this one page from Webflow and adds a new version. It works like Publish selected for a single page.

Switching versions changes your staging site only. The next time the page is published, WCH builds it fresh from Webflow and that new version becomes active. To roll back your live site, promote an earlier archive instead. See Archives.

Code

Shows the page as it appears in the current build, after WCH rewrote its links to point at local copies of assets:

• File hosted locally at: the page's path in the build.
• Page script: the scripts on the page. Click one to expand it and read its code.
• Page URLs: the local asset folders and the original URL of each downloaded file.
• The full HTML of the page.

Use it to check what WCH actually published when a page looks different from Webflow.

Removing a page

1. Click the page to open its details panel.
2. Click the delete icon at the top right of the panel.
3. Read the confirmation and click Delete.

WCH removes the page from the build and deletes all of its saved versions. The change reaches a destination the next time you deploy. WCH does not delete the file at your destinations, so a page already deployed stays there until you remove it. For S3, see Removing Dead Files During an S3 Publish.

If the page is still in your Webflow sitemap, it shows up under New pages and the next Publish all pages builds it again. To keep it out for good, remove or unpublish it in Webflow.

Delete repository files

Delete repository files removes your whole build. Every page and file on the Rendering page is deleted, along with all of their versions. Your staging site is empty until you publish again. This cannot be undone.

Use it to start a project's build from scratch, for example after large changes to the Webflow site structure.

1. At the bottom of the Rendering page, click Delete repository files.
2. Confirm by clicking Delete. WCH shows how many files it removed.
3. Go to the Dashboard and click Publish all pages to rebuild.

Delete repository files does not touch your archives or your destinations. Your live site keeps serving whatever you last deployed.

When staging is off

If Staging visibility is set to Off, Rendering still lists your pages, but the Source URL column, the checkboxes, Publish selected and + Update are hidden. Publish from the Dashboard instead. See Staging site.

Testing your changes

1. Tick one page and click Publish selected.
2. Open the page's Staging URL and check it.
3. Open the Code tab if something looks wrong, to see exactly what WCH built.
4. Once staging looks right, click Publish all pages on the Dashboard, then deploy.

Troubleshooting

• No checkbox next to a page: it is not an HTML page, it is a pagination page, or staging is off.
• Publish selected is greyed out: a publish is already running. Wait for it to finish.
• "Project is currently publishing.": another publish started first. Try again when it completes.
• A page is missing from the list: it may be under New pages instead. Tick it and click Publish selected, or run Publish all pages. For errors during a publish, see Publish errors and troubleshooting.