StoneSVN

STONESVN · PRACTICAL GUIDES

An open-source SVN client for Windows: install StoneSVN and the SVN CLI

By the StoneSVN project · Checked against StoneSVN v1.1.2 · Reviewed

StoneSVN is a free, MIT-licensed SVN desktop client for Windows, macOS and Linux. On Windows, it provides a workspace for reviewing diffs, choosing files and directories to commit, browsing history and saving unfinished text changes locally. It runs the installed SVN command-line client; the StoneSVN installer does not replace that requirement.

Which Windows installer should I download?

The official v1.1.2 release includes StoneSVN_1.1.2_x64-setup.exe and StoneSVN_1.1.2_x64_en-US.msi. These are x64 Windows packages. A native Windows ARM64 package is not part of that release. Use the EXE installer for the interactive setup flow, or the MSI package when that format fits your installation process. Follow your organization's software installation policy on managed devices.

Where do I get the separate SVN CLI?

Use a Subversion client package from a source you trust. Apache's Windows binary package list links to distributors. For example, SlikSVN provides a standalone Windows command-line client. If you use TortoiseSVN, include its optional command-line tools during installation. Installing a graphical SVN application by itself does not establish that svn.exe is available.

How do I check whether Windows can find svn.exe?

Open a new PowerShell or Command Prompt after installing the CLI:

svn --version --quiet
where.exe svn

The first command should print a Subversion version; the second locates executables on the current PATH. If the version command is not recognized, check the CLI installation. If you have multiple SVN installations, note which executable the terminal actually uses. You do not need to install a new SVN server to open an existing repository.

How do I start using StoneSVN?

  1. Install the compatible StoneSVN package and launch the application.
  2. Let it find SVN, or select the installed svn.exe in Settings. Select the Subversion client executable rather than another application's launcher.
  3. Add an existing local working-copy folder to the project sidebar. To create a working copy from a remote repository, use Checkout and enter your repository URL.
  4. Refresh status, open a changed file and inspect the diff.
  5. Select the intended files or directories, review the scope and message, then commit.

Existing SVN repositories do not need a StoneSVN-specific conversion. Repository permissions, credentials and network access still apply. Test a new client with a separate working copy before moving important unfinished work.

What if SVN works in my terminal but StoneSVN cannot find it?

Check the executable configured in Settings against the path reported by where.exe svn. A terminal opened before a PATH change can retain an older environment. Restart the affected application after updating the CLI installation. If SVN is found but a repository operation fails, read the specific error and check the same repository with that CLI; executable discovery, authentication and repository permissions are separate problems.

Can I save only part of an unfinished file?

Use local stashes of selected text hunks to set aside unfinished edits and review what remains. This is separate from a commit and does not share the stash with teammates. Global file filters can reduce local review clutter, but do not write shared SVN ignore properties.

Does StoneSVN cover every SVN workflow?

No. General Merge, Switch and line-by-line Blame interfaces are not currently available. Keep a client or CLI workflow for the operations you need. StoneSVN is developed from OrcaSVN, using Tauri 2, Rust and Vue 3. This guide explains the published package choices and setup flow; it does not claim manual installation testing on every Windows configuration.

Download official installers · Source at v1.1.2 · Report an issue