What is the difference between a project backup and a publishing export?
A source-project ZIP is intended for reimporting and continued editing. A publishing export is intended to run or deploy the finished work and may not preserve the editor’s source structure.
A source-project ZIP is intended for reimporting and continued editing. A publishing export is intended to run or deploy the finished work and may not preserve the editor’s source structure.
Important details
- Confirm the actual state of the current project, browser, device, account, or external service.
- Preserve an editable backup before migration, deletion, replacement, or publication.
- Test the workflow with a small non-critical project first.
Recommended approach
- Identify which copy is the editable source and where it is stored.
- Export a recoverable backup before any destructive or cross-device action.
- Check the permissions, data scope, cost, and retention rules of third-party services.
- Perform the operation on the smallest useful scope.
- Reopen, reimport, preview, or run the result to verify it independently.
Common misconceptions
- Browser-local storage is the same as account-based automatic sync.
- A deployment bundle is always equivalent to an editable source project.
- A success notification proves that restoration or production playback works.
- Every browser, AI model, and hosting environment behaves identically.