# Avoid creating local "conflicted copy" files, always take server version/overwrite local?

**URL:** <https://help.nextcloud.com/t/avoid-creating-local-conflicted-copy-files-always-take-server-version-overwrite-local/175699>\
**Category:** 💻 Desktop\
**Created:** [December 3, 2023, 6:35pm UTC](https://help.nextcloud.com/t/avoid-creating-local-conflicted-copy-files-always-take-server-version-overwrite-local/175699 "2023-12-03T18:35:15Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![nofish](https://help.nextcloud.com/letter_avatar/nofish/32/6_22734026db12803ebb3e059622ac3534.png) [@nofish](https://help.nextcloud.com/u/nofish)\
**Post date:** [December 3, 2023, 6:35pm UTC](https://help.nextcloud.com/t/avoid-creating-local-conflicted-copy-files-always-take-server-version-overwrite-local/175699/1 "2023-12-03T18:35:15Z")

</div>

Hi,

I have a folder synced across devices where it’s ‘normal’ (expected) to get sync conflicts.  
Though the issue is when syncing it creates more and more ‘conflicted copy’ files (renaming the original local ones).  
I don’t need this functionality in this case, can I make it so that in case of a sync conflict the local files automatically get deleted/overwritten with the server versions (rather than renamed)?

For illustration, I’d like to avoid this (and having to delete the ‘conflicted copy’ files manualy).

Thanks.

 ![conflicted copy](https://help.nextcloud.com/uploads/default/original/3X/3/6/369df7c63240a529573c7de5ab98fc4a50115382.png)

---

<div class="post-metadata">

**Author:** ![tflidd](https://help.nextcloud.com/letter_avatar/tflidd/32/6_22734026db12803ebb3e059622ac3534.png) [@tflidd](https://help.nextcloud.com/u/tflidd)\
**Post date:** [December 4, 2023, 12:26pm UTC](https://help.nextcloud.com/t/avoid-creating-local-conflicted-copy-files-always-take-server-version-overwrite-local/175699/2 "2023-12-04T12:26:01Z")

</div>

I don’t see such an option in the documentation:  
[https://docs.nextcloud.com/desktop/3.10/conflicts.html](https://docs.nextcloud.com/desktop/3.10/conflicts.html)

On a short term, you could just have a script that deletes such files searching for the specific pattern. Beyond that, it depends if this might be interesting for others as well… (you can check the bug tracker if there is a feature request: [Issues · nextcloud/desktop · GitHub](https://github.com/nextcloud/desktop/issues)).

---

<div class="post-metadata">

**Author:** ![wwe](https://help.nextcloud.com/user_avatar/help.nextcloud.com/wwe/32/72963_2.png) [@wwe](https://help.nextcloud.com/u/wwe)\
**Post date:** [December 14, 2024, 8:47pm UTC](https://help.nextcloud.com/t/avoid-creating-local-conflicted-copy-files-always-take-server-version-overwrite-local/175699/3 "2024-12-14T20:47:35Z")

</div>