Proton Drive app for Windows

This is a fork of ProtonDriveApps/windows-drive. It adds user defined ignore rules to the sync engine, plus the tooling needed to build the published sources. Proton's original README starts at License below.

What this fork adds

Ignore rules

Files and folders inside a sync root can be kept out of synchronization, the same way .gitignore keeps files out of a Git repository.

• .protonignore on the root of a sync folder applies to that whole sync root.
• .gitignore in any directory applies to that directory and everything below it, exactly where Git would apply it. On by default, can be turned off.
• Full gitignore pattern syntax: anchors, directory only patterns, negation, *, ?, ** and character classes.

Rules only take effect for items that are not yet indexed. Adding a rule never removes something that is already in sync, it only stops new items from being picked up. See PROTONIGNORE.md for the syntax, the precedence order and what happens when rules change.

Proposed upstream in PR #2.

A source drop that builds

The published sources do not restore as they stand. Proton.Cryptography and Proton.Drive.Sdk are referenced but exist on no public feed, so restore fails with NU1101. Both assemblies ship inside the official client, which is a .NET single file bundle: tools/bundlex reads that bundle format and tools/localfeed/build-localfeed.ps1 repackages the missing assemblies into a local NuGet feed. With that in place the whole solution compiles.

See BUILDING.md for the exact steps and the versions involved.

Building it yourself

.\build.ps1

That is the whole procedure. The script finds the .NET 10 SDK, including a user scoped one under %USERPROFILE%\.dotnet, builds the local NuGet feed if it is missing, and publishes a self contained artifacts\ProtonDrive.exe. Prerequisites are the .NET 10 SDK and an installed official client of the same version, the script says so if either is missing.

There is no download here, and there will not be one. Two of the assemblies the application needs are Proton's, they are published neither as source nor under a licence that would let anyone else pass them on, and they end up inside every build. On top of that a binary like this carries Proton's name and asks for Proton credentials while being signed by nobody. Building it yourself from sources you can read is the honest version of that, and it is one command.

Contributions to this fork

The "Contributions are not accepted at the moment" note further down is Proton's and refers to their repository. For this fork, issues and pull requests are welcome. The ignore rules are proposed upstream in PR #2, so anything that improves them may end up there.

---

Copyright (c) 2026 Proton AG

License

The code and data files in this repository are licensed under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version. See LICENSE or https://www.gnu.org/licenses/ for a copy of the license.

However, some portion of code is licensed under the MIT License. See LICENSE-MIT for a copy of the license.

Distribution

You can download the latest stable release from the Proton Drive official website.

Contributions

Contributions are not accepted at the moment.