You open OneDrive and find two copies of the same document. One has your computer name appended to the filename. You are not sure which one is newer, which one has your latest changes, or what happened to create the situation in the first place.
This is a sync conflict, and it happens to most people who use cloud storage across multiple devices. Understanding why it happens makes it far less mysterious, and knowing how each service handles conflicts tells you exactly what to do when you encounter one.
What a Sync Conflict Actually Is
Cloud storage services keep your files identical across every device you use. When you edit a document on your laptop, the service uploads the new version and pushes it to your phone, your desktop, and anyone else you have shared it with.
This works seamlessly when changes happen on one device at a time. The problem starts when two versions of the same file are modified before either one has had a chance to sync.
Imagine you edit a report on your laptop at home, then close the lid and head to the office. Before your laptop's changes have finished uploading, you open the same file on your work computer and make different edits there. Now two different versions of the same file exist simultaneously. When the sync service eventually sees both, it faces a problem it cannot resolve on its own. It does not know which version you actually want. Both were edited legitimately. Neither one is wrong.
This is a sync conflict. What happens next depends entirely on which cloud service you are using.
How Each Service Handles Conflicts
Every major cloud service takes a different approach, and knowing which one you use determines what you will see when a conflict occurs.
OneDrive
OneDrive creates a duplicate file rather than overwriting either version. The conflicting copy gets the device name appended to its filename. You might see Report.docx sitting alongside Report-LaptopName.docx in the same folder.
Both files are preserved. Nothing is lost. But you now have two copies to compare, merge, and clean up manually. OneDrive does not merge the changes automatically and does not highlight what is different between the two versions.
For Office documents like Word, Excel, and PowerPoint, OneDrive has an additional layer of protection. When you have two people or two devices editing the same file at the same time through Office apps, OneDrive uses real-time co-authoring to merge changes automatically. This works well in practice and largely prevents conflicts for Office files. The duplicates you tend to see are the result of offline edits that bypassed the real-time system.
Google Drive
Google Drive handles conflicts differently depending on the file type. For Google Docs, Sheets, and Slides, conflicts rarely occur because every edit is saved in real time to the cloud version. There is no local copy to fall out of sync. Multiple people can edit simultaneously and Google handles the merge automatically. Version history records every change, so nothing is permanently overwritten.
For non-Google files uploaded to Drive, such as Word documents, PDFs, and images, the behaviour changes. Google Drive for desktop can create a duplicate copy when a conflict is detected, similar to OneDrive's approach. The conflicting file appears with a modified filename in the same folder. Version history is still available through the web interface, so you can recover any earlier version regardless of what happened to the synced copy.
Dropbox
Dropbox creates what it calls a conflicted copy, naming the duplicate file with the date and the account that created it. You might see Budget.xlsx alongside Budget (John's conflicted copy 2026-04-15).xlsx. Like OneDrive, both versions are preserved and you need to manually compare and decide which to keep.
Dropbox's version history is one of the most accessible of any cloud service. Right-clicking a file and viewing its version history shows every saved state going back 180 days on paid plans, and 30 days on the free plan. This makes recovering from accidental overwrites straightforward even when the conflict resolution creates confusion.
The Three Most Common Causes
Editing Offline Then Reconnecting
This is the most frequent cause of conflicts. You work on a file while offline, a flight, a poor signal area, or simply with Wi-Fi disabled. When you reconnect, the sync service discovers that the file was also changed from another device or by another person while you were disconnected. Two different versions exist and neither one has synced yet.
The offline editing scenario is particularly common with laptops that sleep rather than shut down properly. A file edited before sleep on one machine and edited again on another machine before the first machine wakes and syncs is a reliable recipe for a conflict.
Two Devices Editing Simultaneously
Using the same account on two computers, both with sync clients running, creates the conditions for conflicts whenever you work on overlapping files without waiting for one device to fully sync before editing on the other. Many people do not realise how common this is, particularly if they leave a file open on a home computer while also opening it on a work computer remotely.
Antivirus and Application Locks
Some antivirus software and applications lock files while scanning or processing them, which prevents the sync client from uploading changes immediately. If another version of the file was updated in the cloud while the local copy was locked, the sync client sees a discrepancy when the lock is released and creates a conflict to preserve both versions.
This is less common but can create persistent, seemingly unexplained conflicts on files that nobody is editing from multiple devices. If you see repeated conflicts on specific file types, check whether your antivirus or any related application is interacting with those files.
How to Resolve a Conflict
The process is similar across all three services.
Start by identifying the two versions. Look at the filenames. The conflicted copy is usually named with your device name, the date, or the account that created it. Open both files side by side and identify what is different between them. In most cases, one version has the changes you actually want and the other is outdated or has only minor differences.
If both versions have changes you want to keep, manually copy the relevant content from one into the other. This takes a few minutes but preserves everything. Once you have a single merged file, delete the conflicted copy and let the sync service push the resolved version to all devices.
For Office documents in OneDrive and Word, the built-in compare and merge tools simplify this significantly. Open the most recent version in Word, go to the Review tab, and use Compare to load the conflicted copy. Word highlights every difference between the two versions in a tracked changes view, letting you accept or reject each change individually rather than manually hunting for differences.
How to Prevent Conflicts
The most effective prevention is simple and requires no special tools.
Let sync complete before switching devices. Before closing your laptop or switching to another computer, check that the sync client shows all files as uploaded. OneDrive shows a green tick on synced files. Google Drive shows a checkmark. Dropbox shows a green tick on the system tray icon. Switching before sync completes is the most direct cause of conflicts.
Avoid editing the same file on two devices simultaneously. If you genuinely need to work on a file from two locations, use the web version of the service rather than a locally synced copy. Google Docs, Office Online, and Dropbox Paper all edit in the browser with real-time cloud saving, bypassing the local sync process entirely.
Close files before switching devices. An open file on one machine is more likely to create a conflict when opened on another. Saving and closing before moving to a different device is a simple habit that eliminates a significant proportion of conflicts.
Use co-authoring features for shared files. If multiple people regularly edit the same documents, shared editing through OneDrive or Google Drive in a browser session is safer than multiple people maintaining locally synced copies. Co-authoring in real time avoids the conflict problem by design.
Frequently Asked Questions
Can I lose data during a sync conflict?
In most cases, no. OneDrive, Google Drive, and Dropbox all preserve both versions when a conflict is detected rather than silently overwriting one with the other. The duplicate file is the service's way of protecting your data while leaving the decision about which version to keep to you. The risk of data loss comes from resolving conflicts carelessly, specifically deleting the wrong version, rather than from the conflict itself.
Why does OneDrive keep creating duplicates with my computer name?
This is OneDrive's standard conflict resolution behaviour. When it detects that a file was modified in two places before syncing, it renames one copy with your device name to distinguish it. The most common cause is editing a file offline and then reconnecting while a different version exists in the cloud. Ensuring the sync client shows all files as uploaded before switching devices or going offline prevents this.
Does version history help with sync conflicts?
Yes, significantly. All three major services maintain version history that lets you recover any earlier state of a file regardless of what happened during a conflict. OneDrive keeps version history for 30 days on personal plans and longer on Microsoft 365 plans. Google Drive keeps it for 30 days for non-Google files and indefinitely for Google Docs edits. Dropbox keeps 30 days on the free plan and 180 days on paid plans. If a conflict results in the wrong version being kept, version history is your recovery path.
Discussion (0)
Be the first to comment.