# Know which Syncthing changes create file versions

> Check where a change originated before expecting Syncthing to retain the file’s previous contents.

- Canonical URL: https://update.dsesecurity.com/updates/syncthing-local-versus-remote-file-versioning/
- Publisher: Detection Systems & Engineering (DSE Security)
- Author: DSE Security Editorial Team
- Published: 2026-10-15T00:43:37+00:00
- Modified: 2026-10-15T00:44:33+00:00
- Last reviewed by DSE: 2026-10-14
- Resource type: Guide
- DSE priority: Information
- Topics: Business Continuity, IT
- Reading time: 2 minutes

## What you need to know

Check where a change originated before expecting Syncthing to retain the file’s previous contents.

## Potentially affected

Use this guide when deciding whether a Syncthing deployment can recover a particular edit or deletion. Check each receiving device’s actual folder configuration.

## DSE recommendation

DSE recommends mapping the devices on which users edit files and the devices expected to retain prior versions.

## Article

Check where a change originated before expecting Syncthing to retain the file’s previous contents.

## Source facts

Syncthing documents file versioning as archiving an older file when a remote device’s change replaces or deletes it. It does not archive the previous contents when the file is changed locally on that same device. Versioning is configured per folder and per device, and the default retains no old versions. The available strategies have different retention behavior; a custom version-storage path should be on the same filesystem as the regular folder.

Source: [Syncthing — File Versioning](https://docs.syncthing.net/users/versioning.html).

## Applicability

Use this guide when deciding whether a Syncthing deployment can recover a particular edit or deletion. Check each receiving device’s actual folder configuration.

## DSE recommendation

DSE recommends mapping the devices on which users edit files and the devices expected to retain prior versions. Choose and document a versioning strategy on each intended receiving copy. Define capacity monitoring and an owner for restoration requests. Keep a separate backup plan for the recovery requirements that synchronization and local versioning do not meet. Explain the local-edit distinction to users so that a visible synchronized copy is not treated as proof of recoverable history.

## Verification

In a disposable test folder, change a file on one device and inspect versions on another, then repeat with a local change. Test deletion and restoration under the selected strategy. Record which device retained what and the actual retention settings before describing the recovery coverage.

## Official reference

[Syncthing — File Versioning](https://docs.syncthing.net/users/versioning.html). Reviewed October 14, 2026.

## Primary reference

- Name: Syncthing — File Versioning
- Authority: docs.syncthing.net
- URL: https://docs.syncthing.net/users/versioning.html
- Source publication date: Not stated by the source

## Citation and use

Preferred citation: “Know which Syncthing changes create file versions,” DSE Security, https://update.dsesecurity.com/updates/syncthing-local-versus-remote-file-versioning/
Publishing principles: https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/
Usage and citation policy: https://update.dsesecurity.com/usage/
Copyright © 2026 Detection Systems & Engineering. All rights reserved.