A website export can contain files that should never be published, while the server may contain CMS data or uploads that do not exist in the local export. Review the project filters and backup plan before the first production publish.
Include hidden files deliberately
Open Project Setup → Filters and use Include hidden files to control dotfiles such as .htaccess, .well-known, and .env.
Many websites require .htaccess or .well-known, so hidden files are included by default. Never publish a local .env file unless it is intentionally part of the production setup and contains no development secrets.
Exclude paths from publishing
Add a relative folder or file under Exclude paths from publish, or choose Add Folder… or Add File…. Common candidates include:
Local caches and temporary exports.
Source files that are not required by the live website.
Development configuration.
Logs and test output.
Large assets that are managed by another server-side workflow.
Excluded paths are removed from the publish package. The filter does not remove an item from an existing Webroot Backup and does not configure additional backup paths.
Treat server-only content separately
CMS data, customer uploads, generated files, and hosting configuration may exist only on the server. A local website export is not automatically a complete backup of those files.
Before a structural change:
Add important server folders outside the webroot under Project Setup → Transfer → Additional server paths.
Create a Webroot Backup.
Publish a controlled change.
Verify both the website and the server-managed content.
Beam Webroot Backups do not include databases. Back up each database separately with the database or hosting provider’s tools.
Archive safety
Beam accepts normal files and folders and rejects unsafe archive paths or symbolic-link entries during extraction. The exported site must contain a valid entry point such as index.html or index.php.
For recovery choices, see Webroot Backups, Published Releases, and rollback.