Backups
Which Unity project folders a backup must include for Round Trip, and where to set up File History or Time Machine.
On this page
Version control is the day-to-day protection: Unity Version Control or Git, compared on Choose your strategy. A backup is a second, independent copy for the day the computer or the repository is lost. It does not replace committing.
What to back up
Section titled “What to back up”| Folder | Back it up |
|---|---|
Assets, with every .meta file |
Yes. A lost .meta file breaks every reference to its asset. |
Packages |
Yes |
ProjectSettings, including RoundTripSettings.asset |
Yes |
RoundTrip |
Yes, when Layout Scope is Shared |
UserSettings |
Optional: your editor layout and personal Round Trip layouts |
Library, Temp, Logs, obj, builds |
No. Unity regenerates them; they only waste space. |
Local packages that Packages/manifest.json references with a file: path outside the project folder are not inside the project: back those folders up too.
Where to set it up
Section titled “Where to set it up”- Windows: File History. Include the project folder in a library if it is outside Documents. When restoring, use Restore to and a new folder rather than restoring over the project.
- Mac: Time Machine. Exclude
Library,Temp,Logsandobjunder Options (Exclude files). - A one-off: zip the folders in the table, name the archive with the date, and keep it on another drive or in cloud storage. Without
Libraryit stays small.
Open a restored copy with Add > Add project from disk in Unity Hub; Unity rebuilds Library on first open. Keep the live project out of cloud-synced folders such as OneDrive, Dropbox and iCloud Drive: Unity’s project guidance warns that sync conflicts can corrupt a project.