Try or ByeTry or Bye

KeePassXC Sync Conflict and Conflicted Copy

Share
Workaround available Windows, macOS, Linux Updated November 14, 2026Based on 4 user reportsHow we research

Quick answer

A conflicted copy appears when two devices edit the database offline. Open the main file and use Database > Merge From Database with the conflicted copy, then delete the copy.

Most likely fix: Merge from the conflicted copy

How to fix it

Try these in order — the most common fix is first.

  1. 1. Merge from the conflicted copy

    1. Close other devices that have the file open
    2. Open the main database in KeePassXC
    3. Go to Database > Merge From Database and select the conflicted copy
    4. Save and delete the conflicted file
    Did this fix it?

  2. 2. Avoid conflicts

    1. Let KeePassXC reload the database when it changes on disk
    2. Save and close the database before switching devices
    3. Keep a dated backup of the database
    Did this fix it?

  3. 3. Merge several conflicts

    1. Merge one conflict file at a time; batch merge is a requested feature (GitHub issue 5024)
    Did this fix it?

Symptoms

Extra files named 'conflicted copy' (Dropbox) or 'sync-conflict' (Syncthing) next to your .kdbx, or entries missing after sync.

Why it happens

  • Two devices edited while disconnected
  • Sync service kept both versions
  • A mobile app saved over an outside change (reported by some users, disputed by others)

This guide also covers

  • keepassxc conflicted copy
  • keepassxc merge database
  • keepassxc syncthing sync-conflict

Still not working?

If KeePassXC keeps failing, you're not alone. See every KeePassXC problem users report or the alternatives people switch to.

Have an app idea? Our small team builds any software: web and mobile apps, games, desktop, AI tools. Price agreed together.

Talk to us
Fixed it? Share this guide

The same problem in other apps

All sync failures guides →

Other KeePassXC errors