FolderSync Fits Power Users Needing FTP And Tasker
FolderSync review digs into two-way sync conflict winners and deleted files, Android 11+ scoped storage SD/USB OTG quirks, and NAS SMB3 small-file performance.
App summary
- App
- FolderSync
- Developer
- Tacit Dynamics
- License
- Proprietary
- Version
- unknown (version number changes frequently; the current build is listed on the Google Play page)
- Size
- unknown (install size varies by version and device architecture; shown on Google Play)
- Price
- Free ad-supported version plus a paid 'FolderSync Pro' version sold as a one-time purchase (no subscription model). Exact price varies by country and currency, so check the Google Play listing for the local price.
FolderSync is one of the older names in Android file synchronization, and it has kept its shape: a Tacit Dynamics app, Android-only, that copies folders between your phone’s storage and somewhere else. That “somewhere else” is the interesting part. Most sync apps pick a lane — Google Drive, or Dropbox, or a peer-to-peer mesh — and stay there. FolderSync connects to Dropbox, Google Drive, OneDrive, Box, Amazon S3 and SugarSync, and it also speaks plain FTP, SFTP, SMB/CIFS and WebDAV. If your storage lives on a NAS in a closet or a VPS you rent by the month, FolderSync will talk to it.
It ships in two editions on Google Play: a free, ad-supported build and a paid FolderSync Pro unlock sold as a one-time purchase. No subscription. The app is proprietary and closed source, which matters for anyone who cares about auditing credential handling, and the configuration surface is dense enough to scare off someone who just wants their camera roll in the cloud.
That density is the point, though. FolderSync is a sync engine with a scheduling system, file filters, root support and a Tasker/Locale plugin, not a set-and-forget backup service. The rest of this review treats it that way: what it does well, where the sharp edges are, and what you should verify on your own hardware before you point it at a folder you would be sad to lose.
FolderSync Two-Way Sync: Which File Wins and What Happens to Deleted Files
FolderSync offers three basic directions of travel. Local-to-remote pushes changes from the phone outward. Remote-to-local pulls them in. Two-way sync lets changes flow both ways, so an edit on the phone lands on the server and an edit on the server lands on the phone. Layered on top of that is a “sync only changed files” behavior, which is about efficiency — it skips files that have not moved — and not about conflict resolution. Most of the time those two ideas get conflated, and that is where people get hurt. If you want the same file-sync job without relying on a remote server, Syncthing shows how peer-to-peer syncing works between Android devices and what battery tradeoffs to expect. For readers who want a hosted cloud target that FolderSync can connect to, Dropbox explains how its Android offline files differ from desktop-style sync and where scoped storage limits appear. If your sync destination is a self-hosted Nextcloud or WebDAV server, OnlyOffice Documents walks through connecting Android to those services and what editing fidelity to expect.
In the ordinary case there is no conflict at all. A file changed on one side and not the other, so the changed copy propagates. That is normal change propagation, and it is what happens in the overwhelming majority of sync runs. A true conflict is narrower: the same file changed on both sides between two runs, so the app has to pick. FolderSync’s help pages at foldersync.com are the authoritative place to check the current rule set, because the behavior depends on which options you have enabled and the app has been revised many times over the years. Before you trust it with anything important, build a disposable test folder, put a file with different content on each side, run the sync, and read the detailed log to see what survived. Ten minutes of that tells you more than any general description.
Deletions are the part that catches people. Two-way sync treats a deletion as a change like any other. Delete a file on the phone and the next run may well delete it on the server too — that is correct synchronization and catastrophic backup behavior at the same time. If what you actually want is a backup, configure a one-way remote-to-local pull, or keep versioned snapshots on the remote side so a propagated deletion costs you a restore rather than a file.
The diagnostic tools help but do not settle the question. Detailed sync logs show what was transferred, skipped or overwritten, and file filters let you narrow a sync pair to a specific pattern so a misbehaving job cannot reach the rest of the share. Neither of those features proves conflict-free behavior. They tell you what happened after the fact. Add Tasker triggers or instant-sync on top of a fixed schedule and you also need to think about how often runs can overlap, because two syncs racing each other is a genuinely bad way to discover your conflict rules.
FolderSync on Android 11+: SD Card and USB OTG Sync Under Scoped Storage
Syncing the SD card to a remote server is one of FolderSync’s core jobs, and the app requests broad storage access to do it, with optional root available for folders that ordinary apps cannot reach. Android 11 changed the ground under that arrangement. Scoped storage means an app no longer gets free rein over the filesystem, and removable volumes — SD cards and USB OTG drives — are the sharpest edge of the change. What worked on Android 9 does not automatically work on Android 13.
The practical test is short. Mount the card or the OTG drive, create a test folder on it, and run a one-way push of a small directory to your remote target. Then run a pull back down to the same volume. You are checking two things: that FolderSync can write to the location, not just read from it, and that files land where you expect rather than in a redirected app-specific directory. If writes fail, the usual remedies are granting access through the system folder picker, choosing a folder the app is permitted to write to, or running root on a rooted device. Root only helps on rooted hardware, and it widens what the app can reach, so treat it as a deliberate trade rather than a default.
Keep the distinction between user-accessible folders and everything else firmly in mind. A folder you created on the SD card, or DCIM, or Documents, is fair game. App data under /data/data and system directories under /system are not, unless you have root — and even then, syncing them is a different project with different risks. FolderSync is not an app-data backup tool, and no amount of configuration turns it into one.
Version drift makes this harder to pin down than it should be. The app is Android-only, and the minimum supported Android version differs between releases, so the system requirements on the Google Play listing and the notes at foldersync.com are the numbers that count for the build you are about to install. If your workflow depends on OTG specifically, confirm it on your own device before you build anything around it.
FolderSync to a NAS over SMB: SMB3, Permissions, and Thousands of Small Files
SMB/CIFS sits alongside FTP, SFTP and WebDAV as a first-class protocol in FolderSync, which makes NAS sync a core use case rather than an edge case. If you run a Synology, QNAP, TrueNAS box or a Windows share, the app can mount the target as a remote account and treat it like any other sync destination. That is a big part of why people pick FolderSync over a Drive-only tool.
Protocol negotiation is the first thing to verify. Modern NAS firmware disables SMB1 by default, and you want SMB2 or SMB3 on both ends. Check what your server actually offers, then confirm the connection works with the share you intend to use rather than a generic test share. DFS namespaces are a separate wrinkle: a domain-based path does not always behave like a plain UNC path to a mobile client, so test with the exact path you plan to use in production. Permissions are the other half. The account FolderSync authenticates with needs write access to the target directory, and NAS ACLs sometimes grant listing without granting create or rename. Test a create, a rename and a delete, not just a read.
Performance with thousands of small files is where expectations need calibrating. Per-file overhead dominates these workloads, so a folder of twenty thousand 40 KB photos behaves nothing like a single 5 GB video, even at identical total size. Treat throughput as something you benchmark on your own hardware: time a first full sync, then time an incremental run after touching a handful of files. Wi-Fi quality, SMB signing, the NAS’s disk subsystem and the phone’s storage speed all move the number, and none of them are under the app’s control.
Camera-folder-to-NAS is the canonical example, and it is a good one — point a sync pair at DCIM, target the share, and your photos leave the phone without a cloud account in the middle. Filters and schedules decide how pleasant that is. An include filter for JPEGs and an exclude for RAW keeps the job small; a fixed overnight window keeps it off your battery during the day. Instant sync on change is event-triggered, not continuous real-time mirroring, and it still lives inside Android’s background execution limits. If a sync must happen at a specific moment, a scheduled window plus a manual widget is more predictable than hoping the trigger fires.
FolderSync Is Not Cloud-to-Cloud: Why Drive-to-Dropbox Sync Needs Local Staging
Every sync pair in FolderSync has a local side and a remote side. The remote side can be Google Drive, Dropbox, OneDrive, Box, Amazon S3, SugarSync, or an FTP, SFTP, SMB or WebDAV server. The local side is the phone’s internal storage or its SD card. There is no provider-to-provider pipe anywhere in that model, and the long list of supported clouds does not add one.
So a Drive-to-Dropbox job means staging. You create one pair that pulls the Drive folder down to a local directory, and a second pair that pushes that directory up to Dropbox. The data travels to the phone and back out again, which requires free device storage roughly equal to the size of the data set plus some headroom, and it consumes bandwidth in both directions. On Wi-Fi with a charger attached that is fine. On a metered connection with a large photo library it is not.
You can make the sequence tidier with the Tasker/Locale plugin — trigger the pull, then the push — but the topology does not change. The files still land on the phone in between. Anyone who needs a server-side transfer, where the bytes never touch the handset, needs a different tool entirely, and no amount of Pro-version configuration gets FolderSync there.
This is the single most common misconception about the app, and it is worth being blunt about it. The one-time Pro purchase buys you a broad protocol list and a capable automation layer, not a cloud integration platform. If your mental model is “Zapier for storage providers,” FolderSync is the wrong shape.
Pricing & Plans
FolderSync comes in two editions. The free version costs nothing and is ad-supported, with a feature set that is deliberately narrower than the paid build. FolderSync Pro is a one-time purchase — no subscription, no recurring charge — and in the US Play Store it has historically sat in the single-digit-dollar range, roughly $3 to $4, with the exact figure set per country and currency. Check the Google Play listing for your local price before you assume anything.
The free edition is genuinely useful as an evaluation tool. You can add an account, point a sync pair at your FTP server or your NAS, and find out whether the protocol negotiation and permissions work before spending anything. What you get in return for the ads is a reduced feature set, and the specific split between free and Pro is listed on the store page rather than fixed in stone across releases.
The one-time model is the app’s quiet selling point. Sync tools that charge monthly are asking you to rent access to your own files, and over three or four years that adds up to far more than a few dollars. The trade-off is that a one-time purchase does not fund a permanent engineering team, so version cadence is what it is and you should not expect the release rhythm of a venture-backed service.
Who Should Use FolderSync
- Homelab and NAS owners who want their phone’s camera folder landing on an SMB share or an SFTP server without routing everything through a consumer cloud.
- FTP and SFTP holdouts — people with a web host, a seedbox or a VPS who already have storage and just need a client that speaks the protocol properly.
- Tasker users who want syncs triggered by context: arriving on home Wi-Fi, plugging in a charger, or finishing another task. The Locale plugin and intent hooks are the reason to pick this app over simpler alternatives.
- Multi-provider households with a Drive account for work, a Dropbox account for a shared project and an S3 bucket for archives, all configured in one account manager with separate sync pairs.
- People who prefer paying once over another monthly line item, and who are willing to spend an evening on configuration to get it right.
Who Should Skip FolderSync
- Anyone who wants real-time continuous mirroring. Scheduled and event-triggered syncs are not a live filesystem mirror, and Android’s background limits make true continuous sync impractical for any app.
- People who want a complete phone backup including app data. FolderSync syncs selected folders. App data and system directories are out of reach without root, and even with root this is not a backup product.
- Users expecting direct cloud-to-cloud transfers. Drive to Dropbox means local staging, free space and double the bandwidth.
- A simple set-and-forget photo uploader. If all you need is camera roll to Google Photos, the built-in tool does it with less friction and no configuration.
- iOS or desktop users. There is no official client for either, so cross-platform sync depends entirely on the remote server or cloud service doing its own job.
Comparison with Alternatives
| Feature | FolderSync | Syncthing | Autosync for Google Drive | Resilio Sync |
|---|---|---|---|---|
| Protocols | FTP, SFTP, SMB/CIFS, WebDAV plus consumer clouds | Peer-to-peer only | Google Drive only | Peer-to-peer only |
| Cloud accounts | Dropbox, Drive, OneDrive, Box, S3, SugarSync | None required | Google Drive | None required |
| Open source | No (proprietary) | Yes | No | No |
| Tasker / Locale plugin | Yes | Limited | Basic scheduling | Limited |
| Root support | Yes, optional | No | No | No |
| Price model | Free ad-supported; one-time Pro | Free | Free tier; one-time Pro | Free tier; one-time Pro |
Syncthing is the privacy answer. It is open source, serverless and peer-to-peer, so no cloud account sits in the middle and the code can be audited. What it does not give you is protocol breadth — if your destination is an FTP server or an SMB share, Syncthing is not the tool. Autosync for Google Drive and Dropsync, both from MetaCtrl, are the opposite trade: a cleaner interface and a narrower scope, excellent if you live entirely inside one provider and never need WebDAV. Resilio Sync sits between them, proprietary but mature, with selective sync and no central server.
The honest framing is that FolderSync wins on reach and automation, and loses on simplicity and auditability. If you need one app that talks to your NAS, your web host and three cloud accounts, nothing else in this table does that. If you need device-to-device sync with a code review behind it, Syncthing is the better answer and it costs nothing.
Verdict
FolderSync is a power-user sync engine, and it rewards being treated as one. The protocol coverage is genuinely unusual for Android — SMB, SFTP, WebDAV, FTP and the major consumer clouds in a single account manager, with per-folder sync pairs, filters, schedules and a Tasker plugin. The one-time Pro purchase is a fair deal for that breadth, and the free ad-supported build lets you verify your server works before you pay.
The cost is setup work and verification. Two-way sync is not conflict-free by default, and deletions propagate. Scoped storage on Android 11 and later makes SD card and OTG writes something you test rather than assume. SMB performance with large numbers of small files depends on your NAS, your network and your filters, and the only meaningful benchmark is the one you run yourself. Cloud-to-cloud transfers require local staging and free space. None of these are reasons to avoid the app; they are reasons to spend an hour with a disposable test folder before you point it at your photo library.
Use FolderSync if you have a NAS, a VPS, an FTP host or several cloud accounts and you want one Android app that automates syncs across all of them. Use it if you already run Tasker and want sync to react to context. Skip it if you want a backup tool, a real-time mirror, a cloud-to-cloud bridge, or a photo uploader you never have to think about. The app is honest about what it is — a sync engine with a lot of knobs — and it works best for people who are willing to turn them.
Pros
- Unusually broad protocol and provider coverage for an Android sync app — one tool covers FTP/SFTP, SMB, WebDAV and major consumer clouds
- Fine-grained automation: schedules, instant-sync on change, filters and Tasker integration suit power users
- One-time purchase model for the Pro version rather than a recurring subscription
Cons
- Closed-source proprietary app, so the sync logic and credential handling cannot be independently audited
- The free version is ad-supported, and the feature set is intentionally more limited than Pro
- Interface and configuration options are dense, which can be intimidating for users who just want a simple photo backup
- Android-only — there is no official desktop or iOS client, so cross-platform sync depends on the remote server/cloud service
The link goes straight to Tacit Dynamics. We do not host app files.
Frequently asked questions
Is FolderSync free?
The recorded pricing model is Free ad-supported version plus a paid 'FolderSync Pro' version sold as a one-time purchase (no subscription model). Exact price varies by country and currency, so check the Google Play listing for the local price..
What license does it use?
It is listed under Proprietary.
Where can I download the official version?
The official link points to https://play.google.com/store/apps/details?id=dk.tacit.android.foldersync.lite.