About a year ago, I switched from Tutanota and Tresorit to Proton, mainly because of the extra features it offered—like aliases, more storage, and so on. Around eight months ago, I moved to Linux, and that’s when I realized I’d made a big mistake. How can a company with such a large Linux user base not have a proper desktop app? I just can’t wrap my head around it.

After months of relying on the browser—manually downloading files and reuploading them—I’ve had enough. My subscription ends in about seven months, and after that, I’m done. It’s obvious the Linux community is big enough to justify proper support, but instead, Proton keeps rolling out features that should really be lower on the priority list.

I'm looking for a new service to subscribe to. Proton looks neat, but the total absence of Linux support is simply pathetic. That combined with the fact that the rclone folk *wanted to help* and were simply blocked by the lack of collaboration *from Proton* suggests that the problem may not really be lack of manpower (as they like to claim) but negligence and potentially even ignorance from the managers involved.

Just remember: Linux folk are usually not toddlers, we usually don't expect handholding like your average Windows or Mac user. Give us a CLI, open the API for rclone developers or talk to them to work together. You are making this way more complicated than it should.

Yes we needs <3

I'm migrating from Windows to Linux, never to return.
I'm a paying user of Proton Drive.
By October 2025, either Proton will have a Linux client for Drive, or I will no longer be a paying subscriber to Proton Drive.
It is just that simple.

"Linux Client" is definitely the top requests for your users as the next thing to get started ... so please listen to your users!

---
Current standing in Votes for "ideas" in the Proton Drive category

1. "Proton Docs / collaboration suite" - 8,479 votes
This is is already started and more or less completed for the text document editing.

2. Linux Client - 3,658 votes
This has, by far, most votes of not started ideas in the Proton Drive category but feels like it's ignored by the Proton development team???
Why is that???

3. Proton Photos - 1,790 votes
This is already started and Proton Photos is already in production (even though it could be more feature rich).

4. Photo Albums, tagging, location search - 1,225 votes
Not marked as started but feels like it's interlinked with Proton Photos

As an almost linux-exclusive user, a linux client is something I really need. 3K+ votes make me wonder how important the linux community as a privacy focused users is. Got me thinking about finding an alternative to Proton Drive and cancel my subscription.

I am waiting this feature very much.

I wish I could trade my Google drive for Proton drive. But as an avid Linux user I have to rely on rclone for synchronization. And that (otherwise excellent) program does not offer sufficient stability for daily use. Not least because the developers apparently receive little to no support from the Proton team. I understand that there is a long wish list among users and I also understand that choices have to be made when you do not have enough hands for all the work. But this is a critical part for using proton drive. As far as I'm concerned, it should be at the top of your priority list by now.

Please put this feature on the priority list in the roadmap, it is the last hurdle for me to linux migration

Please give the development of this feature priority. As I'm moving away from American technology, access to Proton Drive on Linux is becoming increasingly important for me.

... and guys commenting and voting here:

Don't forget to support the idea of a Native Linux Proton Drive client here as well:

https://protonmail.uservoice.com/forums/932839-proton-drive/suggestions/45271456-linux-client

That thread has been going on since June 2022 and have a lot more votes already!

We are on a family subscription where 3 out of 4 members are on Linux ... I had to make a bulky solution to make it work for us:

All Linux hosts we use constantly keeps parts of their filesystems in sync with a Linux server using Unison. That Linux server hosts a virtual Windows 10 instance that the server
syncs those files to via an NTFS filesystem (having the btrfs side preferred to keep symlinks and file permissions in sync between the Linux hosts). The Windows VM runs ProtonDrive to keep it sync with the cloud.

This forces me to use double file space on the Linux server to host the same files that are also available on the Linux clients (some clients sync all the 3 TBs) and in Proton Drive.

That's the extent I went to get it working instead of simply having all Linux hosts sync directly with a Native Proton Drive client ... if only it where available.

I don't mind a headless (command-line only) client and with restrictions on symlinks and file permissions not being properly synced ... all that is fine and what I'm used to syncing to Google Drive with inSync.

If you lack Linux competence to implement a native client, please collaborate with inSync and help them integrate Proton Drive into their product. They know the Linux side of things well enough to provide a decent client.

This is critical to any proton drive user.
I cannot understand how nothing has been released when it has been asked for for so long... Especially considering how the proton team is actively blocking 3rd party softwares like RClone... (sources: https://github.com/rclone/rclone/issues/7864)

To me, it's the single biggest trouble with using the otherwise amazing cloud suite from Proton.

This is critical to any proton drive user.
I cannot understand how nothing has been released when it has been asked for for so long... Especially considering how the proton team is actively blocking 3rd party softwares like RClone... (sources: https://github.com/rclone/rclone/issues/7864)

To me, it's the single biggest trouble with using the otherwise amazing cloud suite from Proton.

We are on a family subscription where 3 out of 4 members are on Linux ... I had to make a bulky solution to make it work for us:

All Linux hosts we use constantly keeps parts of their filesystems in sync with a Linux server using Unison. That Linux server hosts a virtual Windows 10 instance that the server
syncs those files to via an NTFS filesystem (having the btrfs side preferred to keep symlinks and file permissions in sync between the Linux hosts). The Windows VM runs ProtonDrive to keep it sync with the cloud.

This forces me to use double file space on the Linux server to host the same files that are also available on the Linux clients (some clients sync all the 3 TBs) and in Proton Drive.

That's the extent I went to get it working instead of simply having all Linux hosts sync directly with a Native Proton Drive client ... if only it where available.

I don't mind a headless (command-line only) client and with restrictions on symlinks and file permissions not being properly synced ... all that is fine and what I'm used to syncing to Google Drive with inSync.

If you lack Linux competence to implement a native client, please collaborate with inSync and help them integrate Proton Drive into their product. They know the Linux side of things well enough to provide a decent client.

... and guys commenting and voting here:

Don't forget to support the idea of a Native Linux Proton Drive client here as well:

https://protonmail.uservoice.com/forums/932839-proton-drive/suggestions/45271456-linux-client

That thread has been going on since June 2022 and have a lot more votes already!

3642 votes, 4 years old and still no Linux support, what a shame

The only reason I haven't bought the premium subscription is the lack of a Linux Client. Just using Mail for now... Meanwhile Filen is getting my money for cloud storage.

We are on a family subscription where 3 out of 4 members are on Linux ... I had to make a bulky solution to make it work for us:

All Linux hosts we use constantly keeps parts of their filesystems in sync with a Linux server using Unison. That Linux server hosts a virtual Windows 10 instance that the server
syncs those files to via an NTFS filesystem (having the btrfs side preferred to keep symlinks and file permissions in sync between the Linux hosts). The Windows VM runs ProtonDrive to keep it sync with the cloud.

This forces me to use double file space on the Linux server to host the same files that are also available on the Linux clients (some clients sync all the 3 TBs) and in Proton Drive.

That's the extent I went to get it working instead of simply having all Linux hosts sync directly with a Native Proton Drive client ... if only it where available.

I don't mind a headless (command-line only) client and with restrictions on symlinks and file permissions not being properly synced ... all that is fine and what I'm used to syncing to Google Drive with inSync.

If you lack Linux competence to implement a native client, please collaborate with inSync and help them integrate Proton Drive into their product. They know the Linux side of things well enough to provide a decent client.

Regarding a Proton Drive Linux client: I'm beginning to wonder about the company's motivations given the number of votes and comments. I pay good money for my Unlimited subscription. I don't HAVE to keep subscribing.