Dropbox Keeps Creating “Selective Sync Conflict” Folders- Here’s Why
A frustration showing up across dozens of community threads, and what’s actually causing it.
A thread on the Dropbox Community forum describes a scene many Dropbox users will recognise immediately.
The user opened a recent project file in Ableton a music production app and it failed to load because Dropbox couldn’t access it. They tried the “Make available offline” command. That didn’t work either. Then they noticed the Dropbox app was stuck, frozen mid-sync on 44 files. And while it sat there spinning, it started creating something worse: multiple folders labelled “selective sync conflict,” multiplying in their file tree with no clear explanation.
This isn’t an isolated incident. Scroll through the Dropbox forums and you’ll find the same complaint filed under different triggers a new computer setup, an OS reinstall, an app update, a fresh install on an external drive. The names change. The mess of duplicate, conflict-labelled folders is always the same.
What “selective sync conflict” actually means
Dropbox’s Selective Sync feature lets you choose which folders sync to your local device. It’s useful when you have more files in the cloud than storage on your laptop you sync only what you need locally and keep the rest online-only.
The conflict happens when Dropbox’s memory of what you’ve desynced doesn’t match what actually exists on disk.
Specifically: if you previously desynced a folder told Dropbox not to store it locally and then a folder with the same name gets created in the same location, Dropbox doesn’t know what to do. It can’t overwrite the local folder, because that might destroy data. It can’t merge them, because it doesn’t know which version is authoritative. So it does the only thing it can: it creates a new folder with “selective sync conflict” appended to the name and leaves both sitting there for you to sort out.
The result is what one user described after a fresh OS install on a Mac: “a big mess of duplicate and triplicate folders, with the folder sizes being different across all of them.”
The triggers nobody warns you about
Several common actions reliably cause this, and none of them are flagged in Dropbox’s onboarding or update prompts:
Setting up a new computer. When you install Dropbox on a new machine and choose not to sync certain folders (to save local storage), those folders are marked as desynced in your preferences. If those same folder names already exist somewhere on your new machine even as empty shells from a previous backup conflict folders appear immediately.
Reinstalling the OS or moving the Dropbox folder. After a clean OS install, your Dropbox folder from an external drive reconnects to the app but the app’s selective sync settings don’t always carry over correctly. The mismatch between what the new install expects and what’s actually on disk triggers the conflict creation loop.
Updating the Dropbox app. Multiple forum threads from mid-2025 document users whose entire folder hierarchy was disrupted after a routine Dropbox update. One described the aftermath simply: “I was prompted to update Dropbox, so I did. Now I have selective sync conflicts everywhere and my folder hierarchy is basically gone.” An update shouldn’t be able to do that but it does.
Applications generating files automatically. If software running on multiple computers simultaneously writes to folders in your Dropbox (configuration files, autosaves, project caches), each machine can create a version of the same folder at the same moment. Conflict folders proliferate, one per machine per write event.
What you can and can’t do about it
The uncomfortable truth, stated plainly in Dropbox’s own community responses: there is no automated way to merge selective sync conflict folders. Only you know which version of the conflicting folder has the data you need.
If the conflict folders are empty which they often are you can delete them safely. Dropbox has confirmed this. Empty conflict folders don’t contain data; they’re just structural artefacts of the naming collision.
If the conflict folders contain files, you need to open both versions, compare them manually, and decide what to keep. There’s no merge button. No diff view. No tool inside Dropbox to help. The Dropbox Community’s own response to one user was stark: “This can only be checked manually by yourself since only you know which files need to be kept or discarded.”
For people with hundreds of conflict folders which is not unusual after a botched OS migration this can mean hours of manual triage.
The structural problem underneath
What makes this frustrating beyond the immediate inconvenience is that selective sync conflicts are entirely a Dropbox internal state problem. The user didn’t do anything wrong. They installed an update. They set up a new machine. They did what Dropbox asked them to do.
The conflict happens because Dropbox’s local app lost track of its own sync state and then recovered by creating duplicates rather than resolving the inconsistency cleanly. It’s defensive behaviour that protects against data loss which is good but it offloads all the cleanup work onto the user with no tooling to help which is not.
For teams managing Dropbox across multiple devices, the risk compounds. One person’s OS reinstall can trigger conflict folders that appear on every synced device in the shared folder. What started as a single-machine issue becomes a team-wide cleanup exercise.
Having visibility across all connected cloud accounts and folders in one place doesn’t prevent Dropbox from creating conflict folders nothing will, short of Dropbox fixing its own sync state management. But it does mean you can audit what’s where across multiple accounts without logging in and out of separate sessions, which at least makes the triage faster when the conflicts do appear.
The practical checklist
If you’re looking at a folder tree full of “selective sync conflict” labels right now:
Check whether the conflict folders are empty first if they are, delete them without hesitation. If they contain files, open both the original and the conflict version side by side and compare modification dates. Keep the newer version, move it to the correct location, and delete the conflict copy. After cleanup, go into Dropbox Preferences → Selective Sync and verify that your current settings match what you actually want synced. A mismatch here is usually the root of the next conflict cycle.
And if you’ve just set up a new machine: before installing Dropbox, check whether any folder names in your existing local structure match folders you previously desynced in Dropbox. That name collision is the most avoidable trigger and the one most people hit without realising it.
Had a selective sync conflict spiral get out of hand? Drop what caused it in the comments the pattern across different setups is genuinely useful for everyone else trying to diagnose theirs.