How to sync a local folder to a network drive safely
To sync a local Windows folder to a network drive, choose the local folder as the source and a mapped drive or UNC folder as the target. Compare first, check overwrites and deletions, then confirm the one-way sync. LibSync backs up existing target files before overwriting or deleting them; it does not run automatic two-way sync.
Reviewed:
Define the direction before the tool
- Choose one authoritative source; LibSync is not an automatic two-way conflict resolver.
- Use a mapped network drive or UNC path that the current Windows account can access.
- Review new, changed, renamed and target-only files before confirming the run.
- Keep the backup folder separate from source and targets and monitor its retention.
LibSync creates reusable Windows profiles, compares source and targets, and backs up files before overwrite or deletion. View LibSync
Example: publish approved templates to the team folder
Suppose your local Templates folder contains the approved files and the team uses a Templates folder on a mapped network drive. Set the local folder as the source and the shared folder as the target. Keep the backup in a separate location.
Preview a small sample first. A template present only on the shared drive needs a deliberate decision: keep it, bring it back to the source, or remove it after review. Confirm the direction and deletion setting before running the sync.
Source, target and permissions
The source contains the version you intend to distribute. A target is the network folder that should match that source after approved changes. LibSync profiles can contain more than one target, but the flow still goes from the single source outward.
Test the same Windows account that will run the sync. It needs read access to the source and sufficient rights to create, update, rename or delete files at each target according to the chosen settings. A reachable share in Explorer is a useful first check, not a substitute for preview.
Why comparison matters on a network share
Blindly copying a folder can overwrite a newer target file or leave old files behind without explanation. A comparison shows which relative paths are added, modified, renamed or present only at the target. LibSync calculates that plan before it writes.
Target-only files need a policy. With deletion sync enabled they are included in the confirmation and removed during the run. With it disabled they appear as orphans so you can skip, delete, copy back to the source or rename them. Copy-back is an explicit orphan action, not two-way synchronization.
Backups are change backups, not a full archive
Before LibSync overwrites or deletes a file, it copies that existing file into the current backup run. New target files have no previous version to back up. The result is a recoverable record of changed and deleted items, not a complete duplicate of the source.
Choose a backup root with enough space and outside the paths being synchronized. Profiles default to a 30-day retention period; set and review that period according to your organisation's recovery needs.
Configure the first sync
Start with a small representative folder until the direction and permissions are proven.
- 1
Select the authoritative local folder
Remove temporary material and confirm that this source contains the approved versions.
- 2
Add the network target
Use the mapped drive or UNC path and verify access with the same Windows account.
- 3
Choose a separate backup root
Do not place backups inside the source, a target or the optional staging path.
- 4
Set exclusions and deletion policy
Exclude unwanted file extensions and decide whether target-only files may be deleted.
- 5
Preview and investigate surprises
Check counts, paths and unusual changes. Cancel the run if the source looks empty or the share state is unexpected.
- 6
Run manually and verify
Confirm the reviewed plan, inspect the summary and open a few target files after completion.
Network sync checklist
- The source-of-truth folder is documented.
- UNC or mapped-drive permissions are tested.
- Deletion behaviour is understood by the folder owner.
- The backup root and retention period are suitable.
- A preview has been reviewed before the first full run.
Local-to-network sync questions
Does LibSync run automatically in the background?
No. Current syncs are started manually. Profiles save recurring source, target, backup and policy settings.
Does it support UNC paths?
Yes. Local folders, mapped network drives and UNC paths can be used when the Windows account has the required permissions.
Is this a two-way sync?
No. The normal flow is one source to one or more targets. A target-only orphan can explicitly be copied back, but there is no automatic two-way conflict resolution.
Related guides
Continue with the next practical question in this workflow.