Unofficial proton-drive-linux-fs mounts Proton Drive on Linux
proton-drive-linux-fs is a FUSE virtual filesystem that mounts a Proton Drive as a local folder on Linux, at a directory the user chooses. Files and folders are listed straight from Proton's metadata, but the contents of the files are not downloaded up front. Each file is fetched on demand when it is read. The project describes this as a "lazy" approach that saves bandwidth and disk space, in the manner of Google Drive, Dropbox and OneDrive.
Changes made elsewhere reach the mount through Proton's event feed, which invalidates the affected directory listings and cached file content. Writes go the other way more slowly: they are buffered to a local temp file and uploaded to Proton in full a set timeout after the file closes.
The author is blunt about maturity. The project is "early and unofficial" and is not affiliated with, endorsed by, or supported by Proton AG. The author tested the most common paths, meaning read, write, create, delete, rename and move operations, on one Proton Drive share, and says everyone has a different setup that cannot all be tested. The advice is to expect bugs and report them on the issue tracker.
The design keeps all contact with Proton in one place. Applications never talk to Proton directly. Reads and writes pass through the kernel's FUSE layer to the mount daemon, the proton-drive-fs daemon, which is the only component that speaks to Proton's API. According to the description, this confines communication to a single layer to avoid leaks of credentials or data. Inside the daemon the diagram shows three parts: fusefs, drive and auth.
A tray component, and any future developments (probably a GUI), talk to the same daemon over its local unix socket, falling back to a status file when the socket is not available. The author's stated hope is that the daemon will stay working no matter what happens.
Key facts
- proton-drive-linux-fs is a FUSE virtual filesystem that mounts Proton Drive as a local folder on Linux, at a directory the user picks.
- File contents are downloaded only when read; listings come from Proton's metadata, and remote changes arrive through Proton's event feed.
- Writes are buffered to a local temp file and uploaded in full a set timeout after the file closes.
- Only the mount daemon speaks to Proton's API; apps go through the kernel's FUSE layer, and a tray talks to the daemon over a unix socket.
- The author calls it early and unofficial, tested it on one Proton Drive share, and says Proton AG does not endorse or support it.
Why it matters
Proton Drive users on Linux get a way to see their drive as an ordinary folder, with files fetched only when opened rather than synced wholesale. The project positions this lazy approach next to the behaviour of Google Drive, Dropbox and OneDrive, and credits it with saving bandwidth and disk space. It is a small tool by an individual author, not a Proton product.
Who it affects
Linux users who keep files in Proton Drive and want them under a local mount point. Because applications only see a normal directory, anything that reads and writes files can work against it. The source text lists no supported distributions or install requirements, so it does not say which setups are expected to work.
How to use it
The package mounts Proton Drive at a directory you choose. The project's Quick start page carries a complete copy-paste flow for setting it up. Once mounted, read, write, create, delete, rename and move operations are the paths the author has tested. Bugs go to the issue tracker. No license is stated in the text.
How solid is it
The author's own label is "early and unofficial". Testing covered the most common operations on a single Proton Drive share, and the author says other setups cannot all be tested. No benchmarks or bandwidth and disk savings figures are given, and nothing is said about a security audit. The description of the daemon as the single point of contact with Proton is a design statement by the author, and the line that it should stay working no matter what is phrased as an ideal, not a guarantee.
Risks and caveats
The author's advice is to expect bugs. The project is not affiliated with, endorsed by, or supported by Proton AG, so there is no vendor behind it. Writes are held in a local temp file and uploaded in full only after the file closes and a set timeout passes; the length of that timeout is not given. The tool handles Proton credentials and data, which is the reason the author confines all API communication to the daemon, but that is a stated design goal rather than a verified property. No timeline is given for the GUI or other future developments.
“This is early and unofficial. Not affiliated with, endorsed by, or supported by Proton AG.”
— proton-drive-linux-fs project page