SparkleShare

Last reviewed Sep 13, 2026 · 801 words

Every save in a SparkleShare folder is a Git commit pushed to a server you own, which means every version of every file exists forever and you can pull up the text of a document as it was at 14:32 last Tuesday. That is the reason to run it. The same fact is the reason most people should not: Git stores whole files, so a 200 MB video edited 10 times occupies 2 GB on the server and every client that has ever synced it. SparkleShare is a superb tool for a writer, a small design team working in SVG and text, or a research group sharing LaTeX and CSV, and a poor Dropbox replacement for a household of photos and MKVs. Syncthing is the general-purpose answer; SparkleShare is the specialist.

There is no server to install, and that is the good news

SparkleShare is a desktop client (Windows, macOS, Linux; 128 MB of RAM is generous). The "server" is any machine that runs sshd and has Git installed: a Raspberry Pi, a VPS, a NAS with SSH enabled, or an existing forge such as Forgejo. Add a project in the client by pasting an SSH address and a repository path; it clones, watches the folder, and commits and pushes on change. The project ships a shell script called Dazzle that creates a locked-down storage user and bare repositories on a fresh Linux host in about 2 minutes, but a plain git init --bare in a directory the SSH user can reach works identically.

Because transport is Git over SSH, there is no daemon to keep patched, no web UI to expose, and your existing SSH key hygiene is the whole security model. Firewall port 22 to your VPN and the attack surface is zero.

Conflicts resolve themselves, which is rarer than it sounds

Two people edit the same file offline; on reconnect Git sees a merge conflict. SparkleShare does not ask you to resolve it. It keeps both, renaming one copy to mark it as the conflicting version, and carries on syncing. For text this is the correct behaviour and beats Syncthing's .sync-conflict files only in that the history view lets you diff and restore either side with one click. You never lose work, and you never get stuck with a folder that refuses to sync.

The history panel is the feature people who stay with SparkleShare talk about most: a per-file list of every change with author and time, and a restore button. For a manuscript or a set of config files it is version control without anyone learning git rebase.

Encryption is a per-folder switch and it is client-side

Tick "encrypted" when adding a project and SparkleShare encrypts file contents before they are committed, using a password that never leaves the clients. The host sees filenames and sizes but not content, which makes an untrusted VPS or a friend's server a usable backend. The cost is that the server-side history is opaque; you can still restore old versions, but only from a client that knows the password, and you cannot browse the repository in a forge's web UI. For a folder of legal documents or tax records on rented hardware this is the right trade; for a shared team folder it just adds a password to lose.

The binary problem and the project's pace

Two honest limits. First, Git's whole-file storage means large binaries grow the repository without bound, and every new client clones the full history, so a fresh laptop may download 20 GB to see 500 MB of current files. Keep SparkleShare folders for text-like content and put media in Syncthing or Nextcloud. Second, the project has been around since 2010 and is maintained by a very small group; releases are infrequent and the clients lag the newest OS releases by a while. It works, and it has worked for a long time, but do not expect new features. The Nextcloud vs Syncthing comparison is the read if you want the two bigger projects laid side by side.

What I'd do

If you write (prose, code, papers, config) and want every draft kept with zero effort, put SparkleShare on your machines, point it at a bare repository on a Forgejo instance or a git-shell user on a VPS over Tailscale, and turn on encryption for anything financial. Keep those folders under a few GB of text. For everything else, including the family photo pile and any folder a non-technical relative shares, run Syncthing and never look back. Used inside its lane, SparkleShare is one of the few sync tools I would trust with 15 years of a book.