Syncthing Android to PC: Setup, Conflicts and Recovery Checks

Sharing the wrong folder can spread unwanted edits or deletions to your other device. To set up Syncthing from Android to a PC, choose a currently maintained Android client, pair the two Device IDs, and verify an empty shared folder before adding important files. This guide uses project documentation checked October 15, 2026; we did not install the clients or test devices.

The original Android app is discontinued; Syncthing-Fork is a community continuation, and the PC still runs the Syncthing core. Start with one disposable folder in Send & Receive mode, accept the intended peer on each side, and open a sample file at both local paths. Then rehearse a conflict and a deletion with recovery before trusting the arrangement with real work. Recent project activity establishes maintenance activity, not a security audit or a guarantee that your phone will keep running it in the background.

• Pairing grants device trust; folder sharing chooses the files.
• The shared Folder ID must match; local folder paths can differ.
• Two-way sync carries deletions as well as additions.
• Versioning needs an explicit setting on each receiving device you want protected.

Check the Android client before installing

Use a dated project and release check to choose the Android wrapper. The upstream Android repository is archived and says its final release was planned with the December 2024 Syncthing version; this does not retire the cross-platform core.

The README also links F-Droid, but we could not verify its current listing during this check. We have not established channel equivalence, signing-key continuity or independent security assurance. If those are requirements for your files, resolve them before installing; recent releases alone cannot answer them.

On the PC, follow the core installation instructions for your operating system. Start Syncthing and open its local administration page, documented at http://localhost:8384/. Keep it local; this procedure does not require exposing an administration port to the internet. Leave valuable folders unshared while you set up the trial.

Pair the devices and map one empty folder

Configure each device with the other device’s actual Device ID, then share one folder with a matching Folder ID. The core tutorial documents Actions → Show ID and Add Remote Device in the Web GUI; these are not verified Android-native menu instructions. Use your installed client’s controls or its Web GUI to find the equivalent settings, and stop if you cannot identify the intended peer or folder.

1. Create an empty, user-accessible folder on each device. SyncTrial is an example name for this exercise, not an app default. Keep it separate from notes vaults, photos and existing archives.
2. Read each device’s own ID. On Android, add the PC’s ID; on the PC, add Android’s ID. Compare the full values with the actual devices before accepting a request.
3. Add the trial folder on one device and select only the intended other device for sharing. Accept that offered folder on the other device, selecting its empty local trial directory. Preserve the offered Folder ID rather than creating an unrelated share with a similar name.
4. Confirm Send & Receive on both trial folders. This is the standard two-way mode, including changes originating on either peer. Inspect permission or folder errors before creating a file.

Fill these values from your own clients. The configuration reference distinguishes ID, label and path; matching labels alone do not connect folders.

If you only need to open or copy a PC share on demand, use the Android SMB file-manager guide to assess that workflow instead of setting up ongoing synchronization.

Verify additions, edits and availability

Accept the setup only after files open with the expected content at both mapped paths. The GUI’s Up to Date status reports synchronization state; it does not prove you selected the right directory or checked the contents.

This is a proposed acceptance checklist for your own setup, not a record of completed tests. Use small plain-text files with distinct names and markers, and record the actual observation for each row.

There is no promised completion time. A paused folder cannot synchronize; an unavailable peer cannot exchange the queued files. Observe the actual Android client and phone’s background restrictions rather than assuming an always-running service. If the trial fails when the screen is off, keep the workload disposable until you understand that behavior.

Rehearse a conflict without losing either edit

Preserve both candidate files before deciding which content to keep. Syncthing’s conflict documentation describes a copy named with .sync-conflict- plus date, time and device information when simultaneous differing modifications collide. A conflict copy is an ordinary synchronized file, so removing it can itself spread a deletion.

For a controlled rehearsal:

1. Create conflict-trial.txt and confirm the same starting content on both devices.
2. Isolate the peers so neither can receive the other’s edit. Change the same file to different content on each device, save both, then reconnect.
3. Inspect the ordinary file and any conflict copy. If no conflict appears, record that outcome and investigate; do not mark this check as passed merely because both devices say Up to Date.
4. Stop editing and pause the trial folder on both devices. Copy the ordinary file and conflict candidate outside the synchronized directories before comparing them.
5. Read both preserved candidates and merge deliberately into a chosen result. Resume synchronization and open the result on each device. Remove obsolete trial copies only after confirming the preserved copies and intended content.

Do not choose the desired document by its timestamp alone. Syncthing’s conflict handling selects a file to rename; it cannot decide which of your ideas belongs in the finished document. Leave Override Changes and Revert Local Changes out of this beginner trial: those are consequential actions described in the folder-type reference.

Test deletions and receiving-side recovery

Expect deletions to propagate in the trial’s two-way mode, and enable versioning before the remote change you want to recover. Syncthing’s backup FAQ warns that synchronized modifications and deletions reach other devices. Send Only and Receive Only control direction; neither creates an independent, deletion-proof archive.

Versioning defaults to off and is configured per folder, per device. It archives earlier content when changes arrive from another device. Enabling it on the PC does not archive the PC’s own local edits. The default archive is .stversions; retention depends on the chosen strategy and settings, so do not assume every historical edit survives.

A version archive on the same PC is also vulnerable to that PC’s storage failure. Choose a separate recovery arrangement for important files; this small rehearsal is not a complete backup policy. For photos, messages and authentication data, continue with the Android backup checklist, which treats those as separate jobs.

Only after you understand all observations should you add a small real folder, with an independent recoverable backup already available. Any unclear deletion or restoration result is a reason to keep real files out of the trial.

Find the failure before changing more settings

Check the identity, sharing and local path first; then check whether the clients are able to run and communicate. A device connection and a correctly synchronized folder are separate conditions.

For the next step in building a complete notes-and-files routine, return to the Android productivity and essential apps guide.

Method and sources

This is a documentation-based setup procedure with suggested checks, written with AI assistance and editorial responsibility retained by TasteOfAndroid. Sources checked October 15, 2026 include the upstream discontinuation notice, the community project’s README and release metadata, stable-tag build declarations, and the Syncthing core documentation cited above. We did not test installation, current Android-native menus, permissions, background operation, conflicts or recovery on hardware. The desk scenes show devices, separate folders and storage; they are not app screenshots or evidence of completed tests.

Last updated October 15, 2026.