File conflicts occur when changes to the same file are made independently on two separate devices or by two different users before synchronization. "Replace" uses the file from the source location to overwrite the destination file. "Skip" ignores the incoming file change, keeping the existing version at the destination untouched. "Keep both" preserves both modified versions, typically saving the conflicting file with a new name or in a designated folder to prevent data loss.

For example, if you edit a document on your laptop and your colleague edits the same file offline on their desktop, cloud services like Google Drive or OneDrive may detect this conflict upon syncing. Choosing "Replace" would prioritize one person's changes, "Skip" would leave the cloud version as-is, and "Keep both" would save both edited versions. Developers often use "Keep both" (sometimes called 'merge conflict') in systems like Git, creating separate file branches to manually review and integrate changes later.

The best choice depends on context: Replace risks losing desired changes if chosen incorrectly; Skip avoids data loss but prevents updates; Keep Both ensures all work is saved but creates duplicates requiring manual reconciliation. "Keep both" is safest to avoid unintentional overwrites but requires management. Modern sync tools increasingly offer better automated merge capabilities for specific file types. Choose wisely based on which data is most current or critical.