MUE SyncFeaturesHow It WorksSetupDocsFAQDownload

What Gets Synced

Exactly what flows between artists and what never does.

One of the most useful things about MUE Sync is that it syncs your whole project safely instead of forcing you to pick individual files.

What gets synced

What is always skipped

TypeWhy
Intermediate/, Binaries/Generated build output. Syncing it corrupts builds and causes churn.
Saved/, DerivedDataCache/Local caches and editor state, not shared work.
.git/, .vs/VCS metadata and IDE state.
node_modules/Dependency folders (not usually in a UE project, but excluded anyway).
Build/, Deployed/, obj/Build artifacts.
.sln, .vcxproj*, .userSolution/project files that are machine specific.
.pdb, .obj, .tlog, .idb, .ipdb, .iobjCompiler/debugger artifacts.
.log, .tmp, .bakTransient or backup files.

Allowlist mode (power users)

By default, everything except the denylist syncs. If you set MUE_ASSET_EXT to a comma-separated list (for example .uasset,.umap), the agent switches to allowlist mode and sends only files with those extensions. This is a legacy option; most teams should leave it empty and rely on the denylist.

Why both exist: the denylist approach gives a true "sync everything" experience with safety, while allowlist mode is there for highly controlled pipelines that only want specific asset types to move.

How an incoming file is handled

  1. Received over a P2P socket with a metadata header.
  2. Written to a temp file in Content/.mue-sync-incoming/.
  3. SHA-256 compared with the sender's hash. Mismatch = file dropped.
  4. Renamed into its real project-relative location (atomic).
  5. For assets, a marker is appended for the optional UE hot-reload plugin.