Beam offers manual and automatic publishing workflows. For routine updates, Publish Changes is the recommended starting point.
Publish Changes
Publish Changes compares the local export with the current Beam release on the server. It uploads changed files and deletions and is usually much faster after the first publish. If a complete release is required, Beam can fall back to a full archive.
Publish All Files
Publish All Files sends a complete archive. Use it after a major folder restructure, when the release history is no longer a reliable comparison point, or when support specifically asks for a full republish.
Backup-assisted publishing
The Publish menu also provides Create Webroot Backup, Webroot Backup + Publish, and a full-file backup-and-publish workflow. Create a backup before a risky release or a major structural change.
Enable Hotfolder publishing
Open Project Setup → Transfer.
Enable Hotfolder.
Choose the automatic publish mode. Publish Changes is the safer and faster default for regular work.
Export the website into the configured local source folder.
Beam waits for the exported files to settle, then starts the publish automatically. If files change while a publish is already running, Beam queues the next Hotfolder publish. Manual publish actions remain available while Hotfolder is enabled.
How the transfer works
Beam creates one release archive and uploads it in resumable chunks. If a connection is interrupted, use Resume instead of starting the entire transfer again. Leave Chunk Size and Parallel Chunks at their balanced defaults unless repeated retries require careful tuning.
After every publish
A completed transfer is not a substitute for checking the live result. Open the website and verify navigation, forms, assets, and any server-generated content. Before enabling cleanup or deletion behavior, read Preserving server content with filters and protected paths.