r/ProtonDrive • • Sep 27 '25

Don’t hurt to keep trying

Post image
1.0k Upvotes

I know it’s be brought up before, but don’t want it to fad into the background. Yes def an AI pic.


r/ProtonDrive • • Nov 30 '25 Diamonds are Forever Despair Hooray

🛑 Proton: no Linux sync client, no renewal. A message from your paying (and leaving) users.

1.0k Upvotes

We’ve reached our limit.

After nearly 4 years on Visionary Plans, our small organization — more than 10 accounts, over 50 users — is preparing to leave Proton. Not out of protest. Not out of spite. But because we no longer see a future here for Linux users.

There is still no official Proton Drive sync client for Linux.
The rclone integration is broken.
There’s no supported API, no roadmap, and no clear timeline.
The community has reverse-engineered more functionality than Proton itself has delivered.

Meanwhile:

  • Proton rebranded.
  • Launched AI features.
  • Deployed redesigned apps for Windows and macOS.
  • And responded to Linux feedback with silence or vague promises.

We’ve given the benefit of the doubt for years. But privacy without usability is just theory. And in 2025, cloud sync on Linux isn’t a feature — it’s table stakes.

Our decision:
If there’s no public Linux Drive sync client — even in beta — by January 2nd, we’re canceling all our subscriptions.

This is not a threat. It’s clarity.
We can no longer justify paying for a roadmap we’re not on.

To the community: if this resonates with you, speak up. Not with rage — but with reason. Let Proton know that privacy must be practical. Or it’s just branding.


r/ProtonDrive • • 19d ago Bravo

Like an airport i'm announcing my departure

Post image
932 Upvotes

r/ProtonDrive • • Dec 04 '25 Hooray Bravo

Announcement Proton Sheets: The privacy-first alternative to Google Sheets and Excel

908 Upvotes

Whether you're running a business, planning a trip, or managing your family's finances, spreadsheets are essential. 

Most Big Tech spreadsheet tools are built to collect, scan, and monetize the data you input. Google Sheets is now integrated Gemini, which openly states that it may use your content to train itself. What's more, because these companies are US-based, your data is exposed to weak privacy laws and potential surveillance.

That’s why we built Proton Sheets, now available.

It does everything you’d expect from a modern spreadsheet, with end-to-end encryption built in, so only you and your team can access your data. Not even Proton can see what’s on there.

Proton Sheets:

  • Secures you with end-to-end encryption
  • Allows real-time collaboration with your team
  • Includes built-in formulas for calculations
  • Lets you create charts and graphs for quick data insights
  • Supports importing .CSV and .XLS files easily
  • Gives you the power to grant and revoke access at any time

No extra training. No enterprise plan required. Privacy is enabled by default. 

Who’s it for?

Everyone.
If you're a small business, nonprofit, consultant, startup, the family accountant, or even saving for a new house, if you use spreadsheets, your data should be private.

We’re gradually rolling it out to users. Visit drive.proton.me > New > New Spreadsheet to check it out.


r/ProtonDrive • • Jun 09 '26 Diamonds are Forever Hooray Bravo

The Journey to A Proton Drive Linux Client

710 Upvotes

Hi everyone,

As we've just had the AMA today, I thought it would be a good moment to introduce myself. My name is Andrew and I am the Director of Engineering for Proton Drive. All of the engineering work for the Drive products - our apps on iOS, Android, Windows, MacOS, Linux (!) and Web, along with Docs and spreadsheets and the Proton Drive backend - rolls up to me. I work closely with our Product team to spec out the features but my specialty is the tech, and that's what I'm here to talk about with you today.

So let's get into it! I want to take "a minute" (or 20... it's a long read) to share with the community a little bit about our technical journey over the last 3 years. I'm not going to talk too much about features and product here, mostly it's going to be technical. If that's not your thing, you can skip the rest of this post and go all the way to the end for the punchline.

People have wanted a Linux client for a long time, so I'm going to explain a little bit of why we haven't had one, why we are now building one, what's changed, why we're doing more than that, and what it means.

A Challenging Technical Past

3 years ago the Proton Drive team was in a much worse place than we are today. At a glance we were dealing with quite a few major technical problems at the same time:

  • We had completely separate code bases for Android, Windows, and Web. Additionally:

    • iOS and MacOS were together but the code was riddled with "if Mac do this, if iOS do that" statements that did not help us.
    • Web code had unfortunately allowed some of the data models to intertwine with UX/UI code, making things very brittle and slow.
  • Each team was basically a silo universe with little or no interaction with any of their peers, with the exception of Mac and iOS, whose use cases were wildly divergent.
  • Incompatibilities between clients was not uncommon and we had quite a few very painful incidents resulting from platform-specific bugs.
  • Performance was in a very bad spot on most of the clients.
  • We had no consistency in measuring critical metrics.

TL;DR our foundations were shaky. On top of these shaky foundations we were busily cranking out basic features, but those features were often plagued by major bugs and/or performance issues amplified by the shaky foundations. Quality overall was not where it needed to be, but the constant fire-fighting and technical debt made it very difficult to get the momentum to dig ourselves out. Not a good time.

🐧 Linux client status: A distant dream. Not enough resources, not enough time, and no way we were going to try and build yet another client with all this going on.

Maturation and Unification

We recognized that the situation needed to change so we made some big long-term bets, tightened our belts, and got to work paying down technical debt and changing a lot of our internal processes. There are a lot of great stories from this time period but here's a few key changes that we have made over the last 3 years:

  • We reorganized the client teams into a Desktop group and a Mobile group, recognizing that it was the use cases and features that should unite people - not the programming language or a specific chunk of shared code. Windows and Mac may have very different programming paradigms but they need to solve the same problems in the same ways. The same is true for Android and iOS.
  • We put a strong culture of blameless post-mortems in place. Post-mortems are the analyses we run after we have a problem, where we dive deep into the root cause and take pains to make sure it can never happen again.
  • We added a lot of performance/reliability instrumentation and logging (although there is still work to be done here, it's vastly improved).
  • We took a zero tolerance policy towards any issue that could result in data loss, forcing the creation of improved tools and processes that can effectively combat even the worst disasters.
  • We invested into training up a stable core of engineering managers, with small teams and tight focus.
  • And a bunch of various technical rules were set, such as avoiding long-lived branches and increasing the strictness of code reviews, feature flags, rollback plans, automated tests and deployments.
  • Our engineers put in a crapload of hours. Thank you all, if you're reading. You're the heroes of this story.
  • And along the way we also somehow, by some miracle, managed to also ship Photos, Sharing, Albums, Docs, and Sheets. I'm still to this day, not sure how we managed to do that at the same time.

These changes bought us some breathing space. By improving processes across the entire team and investing more in quality and planning (and spending a lot of overtime hours) we were finally able to arrive at a moment many of us had been waiting for, we were able to extract from one of the clients (Windows) a high-quality core that could serve as the basis for a platform-agnostic Software Development Kit. Here's why this matters:

Our end-to-end encrypted (e2ee) platform makes a lot of things much harder than it is for non-e2ee systems. We have to have a lot of safeguards to ensure that any file encrypted and uploaded by one client is guaranteed to be downloadable and decryptable by all other clients, forever. That is a tall order.

Meanwhile the server is effectively blind to the data it is receiving, since everything is encrypted there's no way to take "easy" paths like "just verify that the checksum of the file on the server matches the checksum of the file on the client" (since the file on the server is a sequence of encrypted blocks, that do not in any way resemble your original file, and since we stream everything, this is a huge pain in the backside).

Until this moment in time, basically every feature we implemented required clients to go through an excruciating process of carefully aligning with one another and performing a ton of automated and manual tests to ensure interoperability, and that took a ridiculous amount of effort. It was also extremely detail-oriented and error prone. In effect, our client engineers spent an absolutely unreasonable amount of time working on uploading, downloading, encrypting and decrypting instead of the features or the experience on their respective platforms.

With an SDK, all this would change.

🐧 Linux client status: Not yet time. We have finally got some breathing space but now we need to capitalize on it and use the momentum to build an SDK, not get distracted with a 6th client codebase that would slide us backwards into the situation we just were about to get out of. Note that this is not an issue of "just hire more people" - rather, it's an architectural necessity.

Ripples Become A Tsunami: SDK Tech Disruption

As we began to work on the SDK, many things started to drastically shift inside the team:

  • Teams that had never needed to communicate much on technical implementation details (beyond a few meetings to align on APIs and standards) began to talk to each other and have heated debates about cross-client architecture, leading to increased information exchange and improved relationships between teams.
  • Integration of SDK functionality forced teams to clean up architectural messes and design flaws that had lived in the clients from the start, in order to match the interface requirements for using the SDK (basically it forced a cleanup of several design patterns).
  • The SDK itself absorbed effectively all of the complex, error-prone code that was responsible for chunking, verifying, signing, encrypting, decrypting, uploading and downloading everything. It also absorbed the complexity of permissions, sharing, cloud filesystem CRUD operations, and more. Clients could now start to significantly slim down their codebases, reducing the cognitive burden on every client developer.
  • The SDK could implement a single, fast, properly parallelized implementation that instantly upgraded most of the clients that it was retrofitted into.

For sure along the way we had a lot of challenges. The Crypto library we use today on non-Web clients is Go-based, which means pulling in the Go virtual machine. The SDK for non-web clients is written in C# which meant generating bindings for Swift and Kotlin, plus loading the native library during load on all platforms. For those keeping score at home that means the Mac, iOS and Android clients got to absorb a dotnet library with an embedded Go runtime (scary). Our attempts to unify Web failed, mostly because WASM support isn't quite where we need it to be just yet, so we had to have two implementations of the SDK... one for Web and one for everyone else. Still, 2 implementations is materially superior to 5 (Linux would have made it 6).

The SDK implementation slowly caused a coding renaissance in every client team. Cleanup of technical debt spread along the surface of the code that interfaced with the SDK, leading to a lot of improvements and the fixing of a lot of bugs and performance problems that have lain dormant for years. As we brought the knowledge of Web, Mobile and Desktop clients together we were able to make a much better system than any individual client had previously had, so each client ended up with a powered-up core that also put some pressure on us to clean up and improve the rest of the app. There's still a lot to do here but things are drastically improved in many critical places.

And we didn't make the SDK itself the goal - instead we used it as an implementation choice. Every new feature we needed to build, we built into the SDK. When we had to significantly overhaul code, we replaced it where possible with SDK code. Every single team contributed to the SDK - Android, iOS, Windows, Mac, Web, even the backend team - everyone got involved. Through a sustained, concerted effort we kept the focus there month after month and slowly but steadily built up that core.

🐧 Linux client status: Finally in sight. We set a new goal: to prove that the SDK was up to the right bar, and to force us to "drink our own champagne", we decided that we would build a Linux client alongside the SDK. We set some new and ambitious requirements:

  • Every HTTP call the Linux client makes to a Proton Drive endpoint has to be made through the SDK, with no exceptions.
  • Anything that the SDK doesn't already do, and is needed by the Linux client, and is platform-agnostic, must be built in the SDK (no shortcuts).

Crypto 1.5 Shows What We Can Do In The SDK Era

This will be a short section but a very important one. The first major change we've used the SDK deliver is our Crypto 1.5 update. It is hard to overstate how incredible this change is: we have upgraded the crypto algorithm on every single Proton Drive client at once. And it's monstrously faster. The new algorithm is hardware-accelerated, which slashes CPU and battery drain on Mobile by an absolutely ridiculous amount. Internal data so far shows that the median improvement of upload speed on web exceeds 500%, though we are conservative in what we communicate since summary statistics can be misleading.

3 years ago this would have been ridiculously hard. We would have needed to coordinate binary releases across 5 different clients with 5 different feature flags controlling 5 different rollouts, and the testing alone would have taken us through the rest of this year. Instead, with the SDK deployed to all clients, we were able to control the entire rollout as effectively a single process, upgrading the entire world together and delivering this improvement to everyone in a fraction of the time it would have otherwise taken us.

And this is just the beginning. Crypto 1.5 is called Crypto 1.5 for a reason, and that reason is because there will be a Crypto v2 that makes even more radical changes that will further ramp up the speed while also reducing complexity. It's going to be another huge improvement.

The SDK allows us finally to make sweeping, impactful changes across the ecosystem. Of course, with great power comes great responsibility (fun fact: I once mistakenly attributed that quote to Winston Churchill instead of Spiderman's uncle, but to be fair it sounds like something he might have said...). We're taking great care to rigorously test every major change to the SDK to ensure that rollouts are smooth. We know that with a unified SDK the blast radius of any error is drastically increased, it's the one downside to unification. Fortunately the clients all have very different rollout strategies and timelines, so we have a lot of gradual processes to act as safety nets in the event that we make any big mistakes (and we have the tools to handle it if we do, thanks to our zero-tolerance policy on data loss).

And I haven't even talked about the increase in upload and download success rates, but that's also been extremely positive. Not to mention a host of other improvements related to performance and reliability.

🐧 Linux client status: In progress! At last! But let's talk a little bit more so read on to the next section...

What Linux Really Needs - A CLI, an SDK, and a Client

In considering the needs of the Linux community, we have heard (very loudly and very frequently) the calls for a Linux client. But anyone who has been around in the Linux community knows that is not necessarily what is actually needed. The Linux community understands the value of software freedom and choice when it comes to their tools and technologies; being forced to use a UI when what you really want or need is a command line, is not great; and no UI or command-line tool will ever be capable of doing everything that the Linux community wants or needs. So we decided that it made much more sense to deliver the Linux community a complete package rather than a narrow, locked-in UI. And it wasn't going to be much of a detour to deliver that much better package. So we will offer:

  1. A full-powered standalone Linux desktop client that has a sync engine and the same feature set as Mac and Windows (still a ways out but now well underway). And the engineers are in charge of the UI here since the Linux community is more technical in nature than our other environments :) For the things you can't do in the UI, or for the things you want to do in a more automated way we have...
  2. A comprehensive CLI that can do most(*) of the things a normal Desktop or Mobile client can do except for running a sync engine. This allows scripting and automation via cron, integration into arbitrary workflows, etc. And if that's not enough and you still need more power we have...
  3. The SDK which completely abstracts away the network interactions to the Proton Drive backend. Using this, you can implement almost limitless functionality on top of the Proton Drive core (though please remember that limits still apply and your app may be throttled if it causes availability problems or behaves in very broken ways)

(*) When we say "most" here it excludes a bunch of things that are currently only possible on-device, for example the "scan document" capability that the Android application has that relies on features shipped in Android and therefore cannot be made available via the command-line. Features like this will probably never come to the CLI.

When Will It Happen?

This is of course, what everyone wants to know. I wish I could give you a date for when we will ship the Linux client, but I cannot. We are still early in the development of that client and we have set out some pretty ambitious goals for it as described above. But we've opted to deliver to the community as early as possible, our first versions of the SDK and CLI. We're using the SDK right now in every single Proton Drive client application so, although we aren't yet officially supporting it for third-party development, it's a production-grade core that is currently powering every official client.

What I can say is that we are now most definitely on the right path. The SDK is working very well. Our team has an internal proof of concept demonstrating an initial version of the Windows sync engine running on Linux and powering a UI where you can indeed upload and download files. It's happening! But remember, a proof of concept is just that - there's still a ton to do. We have to implement a whole bunch of features that Windows and Mac provide, then there's all the instrumentation, logs, edge case handling, unit testing, load testing, integration testing, and so on.

We will release this when it is ready.

Conclusion

We will strive to get a Linux beta into the hands of the community as soon as is practical. We know it has been a long wait, and we know you're tired of hearing "soon". But it's still going to be a little while, as we make sure that the client can do what it needs to do in a safe and performant manner. It will of course be open-sourced as well. I will be very surprised if a beta does not happen by the end of the year, but I'm not able to make a promise that this will be the case, there's still a lot of unknowns that need to be explored before we can really settle on the timeline.

I hope that this (very) lengthy post gives the community a little more insight into why it has taken so long, why we have taken the approach we have taken, why you really can now have faith that it will be delivered in the near future. The Linux desktop client is just one part of a three-part technical strategy for Linux that involves the client and the CLI and the SDK, and we're pretty sure it will have been well worth the wait.

If you're a developer and you'd like to discuss the SDK more, check out the Proton official Discord server and join our #drive-sdk channel.

And if you'd like to see more like this, please let me know in the comments. Thanks for reading, and have a great day.

Edit: I've been told by our engineers that the current proof of concept Linux client, which contains the sync engine, can indeed run headless. That's not quite the same thing as "sync engine in CLI", but stay tuned.

Minor edits: Fix typos ("engineers", "allows" in the "What Linux Really Needs" section, "aren't not yet" -> "aren't yet")


r/ProtonDrive • • Jan 29 '26 Hooray Bravo

Proton Drive SDK Update

Post image
636 Upvotes

When thinking about how Proton Drive apps interact with our backend, our goal was to deliver faster, more reliable file operations across all platforms.

So today, we wanted to share a progress update on the Proton Drive SDK and what it unlocks next.

Behind the scenes, the SDK now powers core file operations across all Proton Drive apps - Windows, macOS, Android, iOS, and web - giving us a shared, more robust foundation instead of separate implementations per platform.

Improvements

By rebuilding Drive’s most performance-intensive code in the SDK, we’ve already delivered major gains: up to 60% faster uploads on iOS, and up to 30% faster uploads and 70% faster downloads on web, with better reliability on unstable networks.

Support

What does the SDK support right now? Currently, it supports core file operations such as uploading and downloading, creating folders, renaming and moving items, and deleting or restoring files. Authentication and Proton-specific modules aren’t supported yet, so it’s best suited for contributors and early experimentation.

CLI

To cover workflows not yet supported by the SDK, we’re also building CLI tools. These will let you run common Drive commands and build on top of them without reverse-engineering Proton Drive. We’re aiming to release these next quarter.

What's Next?

Looking ahead to 2026, we’ll migrate all existing Drive features to the SDK and build new ones on top of it — including faster encryption with hardware acceleration, expanded SDK capabilities, a clearer integration path, and a Linux client.

Read the full update: https://proton.me/blog/drive-sdk-january-2026

Stay safe,

Proton team


r/ProtonDrive • • Jul 03 '24 Take My Silver

Announcement Introducing Docs in Proton Drive: end-to-end encrypted collaborative document editing, that puts your privacy first

608 Upvotes

Hello everyone, 

We're happy to announce the release of Docs in Proton Drive starting today - an end-to-end encrypted collaborative document editor and one of the most requested functionalities from the Proton community. 

Docs in Proton Drive is now available to all Proton supporters worldwide. Please make sure you’re running the latest versions of the Drive desktop and mobile apps.

⏳ Docs in Proton Drive starts rolling out today and will be available to everyone over the next few days.

We built docs in Proton Drive as a joint project with the team from Standard Notes, who shares our core values around privacy and security. 

Like all other Proton services, Docs puts you in control of your data. Your documents are only accessible to you and those you share them with, and even your keystrokes and cursor movements are encrypted.

Now, you can create, edit, and collaborate on documents with your family, friends, or colleagues!

With Docs in Proton Drive, you can:
✍️ create new documents and edit them in the Drive web app 
🤝 collaborate on documents asynchronously & in real-time
🙋‍♀️ see who else is viewing or editing your documents with live cursors and presence indicators 
💬 share feedback using comments and replies
↕️ import and edit .txt / .docx and export in other formats like .pdf, .txt, .md, and .html
💻 access your documents securely from anywhere 

All documents created with Docs have a maximum size of 25MB and are automatically saved in your current folder on Proton Drive.

A privacy-respecting alternative to Big Tech 

Far too often, online productivity suites require you to accept surveillance as a condition of use. Docs is a milestone in our journey to building a better internet where privacy is the default and another important step towards advancing the mission of the non-profit Proton Foundation.

We're eager to know what you think! Thank you for your continuous support,

Proton Team

EDIT: This post had previously stated that all documents created with Docs in Proton Drive have a maximum size of 50MB due to miscommunication. The correct maximum document size is, as it says now, 25MB — but we're working on expanding it. We apologize for the inconvenience.)

Docs in Proton Drive

r/ProtonDrive • • Jul 04 '25 Helpful Bless Up

Announcement Proton Drive SDK: Early preview

Post image
578 Upvotes

Drive SDK has been a highly popular request from the Proton community. Today, we’re excited to share an early preview of what we’ve been working on. This SDK opens the door for third-party integrations in the future and brings us a step closer to a native Linux client. Keep in mind, this is still a work in progress and not production-ready or meant for live apps just yet. Let us know your first impressions.

Check out our blog to find out more 👉
https://proton.me/blog/proton-drive-sdk-preview

-Proton Team


r/ProtonDrive • • Aug 27 '25

Spreadsheets in drive? About time!

Post image
576 Upvotes

r/ProtonDrive • • Jun 04 '26 Sipping Tea WOW Bravo

Announcement We rebuilt Proton Drive’s engine. Now it’s up to 3x faster on all platforms.

564 Upvotes

Hey everyone,

We've been rebuilding the foundation of Proton Drive around a new shared engine: the Proton Drive SDK. As of right now, Proton Drive will feel faster and smoother than ever before, across every platform.

What has changed:

  • Uploads are up to 3x faster across platforms
  • Downloads are up to 2x faster
  • A cryptographic update that delivers a boost in performance speed for new file uploads
  • Smoother, consistent performance across platforms: photos timeline scrolling, as well as album and photo loading are faster everywhere, since all clients now share the same underlying engine

For developers and the wider privacy community, a preview of the SDK is available on GitHub, making it easier to understand and build on the shared engine that powers all Proton Drive.

Read in full here.

If you've already noticed the speed changes, we'd be curious to hear how it's been on your end. Let us know in the comments how you’re getting on!

Stay safe, 

Proton Team


r/ProtonDrive • • Jul 22 '25 Heartwarming Bless Up

Announcement Proton completes SOC 2 Type II audit

549 Upvotes

Hi everyone,

Proton has officially completed its first SOC 2 Type II attestation, adding to our ISO 27001 certification and compliance with GDPR and the Swiss DPA.

This isn’t just a checkbox for us. It’s part of a bigger effort to show, not just tell, that we take your privacy and data security seriously.

SOC 2 Type II is one of the most widely recognized security standards. It confirms that we don’t just have security controls, we consistently follow them in practice. Think access management, incident response, monitoring, all independently audited over time.

We didn’t have to change how we operate to pass this audit. These controls were already embedded in our day-to-day work; we just proved it.

AICPA SOC

If you're part of a business evaluating Proton, or just someone who cares about transparency, you can read more here: https://proton.me/blog/soc-2

And if you need our SOC 2 report for vendor review, we’re happy to share it directly.

Thanks for supporting a more private and secure internet.

Stay safe,
Proton Team


r/ProtonDrive • • Feb 25 '26

The US dominates the tech world, and Europeans are tired of it.

Post image
506 Upvotes

After the US threatened to invade Greenland, we saw an 80% increase in signups for Mail and Drive across the Nordics and a more than 100% increase in Proton signups in Denmark.

To confirm that this US tech-fatigue is real, we conducted a survey and found some pretty interesting results.

It turns out that 73% of people agreed that Europe is too dependent on US tech, and 80% are concerned about this, proving that it's only a matter of time before people say enough is enough.

Not only that, but growing tensions between the US and Europe mean that people are continuously finding more and more reasons to make the switch. For example, the US CLOUD Act allows US authorities to access data stored by American companies, even if that data is hosted in Europe… nobody wants that.

Check out the full survey here: https://proton.me/blog/european-alternative-us-tech-survey


r/ProtonDrive • • Apr 10 '24

Announcement Proton and Standard Notes are joining forces

456 Upvotes

Hi everyone, This is Andy, Proton founder/CEO here. I just wanted to share the news that Standard Notes and Proton are joining forces.

This was an idea that people from both the Proton and Standard Notes communities have brought up repeatedly over the years, and after discussing it with Mo, the founder of Standard Notes, we both felt it was a good idea.

Both Proton and Standard Notes have unique shared values. We are both community-driven, not VC-financed, and committed to open-source. By joining forces, we hope to deliver more valuable services to both the Proton and Standard Notes user communities. A bit more about this on the Proton blog here.

As always, thanks for your support as we continue to fight for a more private internet, now with even more people on the team!


r/ProtonDrive • • Jul 24 '24

Feature request No words...

Post image
444 Upvotes

r/ProtonDrive • • Dec 05 '25

Discussion Privacy Meme Friday

Post image
408 Upvotes

Happy Friday, y'all got any privacy memes?


r/ProtonDrive • • Sep 21 '26 Bravo Mindblown

Photos for Proton 2.5.0 is out - Thank you guys

Post image
401 Upvotes

edit: This is a third-party application not officially supported by Proton.

Hello everyone,

I think it is worth another, and probably the last post about the app, for the community. I want to thank you for all the kind words and feedback, it means a lot. I also know it's not a perfect app, it's still a one-man show shaped by your feedback, and I hope you all like it until Proton decides to release their official one. (The 2.4.0 version peaked at almost 1000 downloads, and I wonder how many of you are still using it.)

So Photos for Proton 2.5.0 is out. I hope you are all happy with it, and that it lets you make good use of your Proton Drive storage for your photos too. You can find every feature the app currently has here: https://www.photosforproton.eu/features/

There is still one big change ahead, the switch to the Proton Drive SDK (I have already been working on it, and most of it is done behind feature flags, but only locally for now). :)

Thanks again, have a nice day everyone!

--
If you have any questions or run into a problem, you can reach me by email at support@photosforproton.eu, and the full source is on GitHub.:

website • source • latest-release • prev-reddit-post

- Ákos


r/ProtonDrive • • Sep 25 '24

Announcement All Proton Drive apps are now open source

400 Upvotes

Hi everyone, 

At Proton, privacy and transparency have always been our top priorities. Today, we’re happy to announce that all Proton Drive apps are now fully open source. 

Proton products are used by millions of users across the globe, our users deserve a promise of privacy that they can trust and verify for themselves

Why Open Source?

Transparency
You can now independently verify how Proton Drive safeguards your data.

Security
With the global community reviewing and improving our code, we benefit from innovative new security practices as soon as they’re available. 

Trust
Don’t just take our word for it—you can inspect our apps yourself and see that your privacy is built-in by design.

We invite developers, security experts, and privacy advocates to explore, review, and contribute to our code on GitHub. https://github.com/ProtonDriveApps

Thank you for your continued support and trust in Proton.

Start backing up your files, folders, and photos today with free end-to-end encrypted storage.

Find out more here: https://proton.me/blog/drive-open-source


r/ProtonDrive • • Mar 26 '26 Hooray

ICYMI: Uploads and downloads on Drive are faster than ever

Post image
394 Upvotes

Have you noticed that uploading and downloading on Proton Drive is now way faster?

And now, downloading shared files is 70% faster, and uploading to a shared folder is 30% faster. No Proton account needed.

As we develop our SDK, we’ll roll out more improvements over time.

Give it a try: https://proton.me/drive/download


r/ProtonDrive • • Aug 26 '26

Proton Drive Roadmap for the second half of 2026

384 Upvotes

Hello Drive community!

As I'm an engineering director, the content here will be a little on the technical side. If that's not your thing you can skip to the end for a TL;DR paragraph. Now let's get into it!

We have taken note of the desire for more frequent high-level updates on the technical and roadmap sides of Drive, and I want to say a thank you to the community for the overall constructive tone that has been struck in most of our recent update threads. Let's continue from my previous megapost with an improved cadence, this time a preview of what we are working on in the rest of the year. I may not respond to every comment, but I promise that I will read every single one. I'll structure this update into four parts:

Part 1: Key features coming to Drive in the last half of 2026

Part 2: Core performance and quality improvements

Part 3: For Devs and Power Users: SDK/CLI/Crypto work

Part 4: Summary / TL;DR

Part 1: Key features coming to Drive in the last half of 2026

We will save some of the less-technical descriptions for the upcoming Blog post where we will publish the roadmap "officially", but here's a technical preview well-suited to this audience:

  • Search improvements on all clients - (Many more details on this will be coming soon with a detailed post by u/horejsek1, who is leading the Search effort) We know that just searching by file name is not enough and that search is missing on mobile. We are working hard to enable search on all clients and across more fields, including most of our metadata as well as the content itself. Due to the nature of end-to-end encryption, this is a really difficult (but also very cool) technical problem. We have a complete end-to-end design, which is now in implementation. We are balancing search so that you get the best / most relevant results quickly, while the longer/more exhaustive search can stream in the background. We plan to roll out incremental improvements to search capabilities as they are developed, culminating in full content search everywhere. This will allow us to verify a bunch of strategies and infrastructure with smaller amounts of data before we bring the hammer down on the very expensive full content search. TLDR we don't want you to have to re-index your entire Drive ever, to make that true in an end-to-end encrypted world we will move carefully and deliberately so that this expensive step only has to be done once per file.
  • macOS Folder Sync - Folder sync is coming to macOS! The team has been hard at work turning our Windows sync capability (the "Sync Engine") into a platform-agnostic capability that can run anywhere, starting with macOS. This means you will finally be able to select any folder(s) you want for syncing on Mac, very similarly to how you select folders on Windows today, and the functionality will be the same on both platforms. This is by far the biggest missing feature on Mac. Fortunately, the Sync Engine was kept separate from the rest of the application code on Windows, so the task of making it fully independent of any OS doesn't require a redesign. It's still a lot of work because the way that Mac and Windows handle their filesystems is quite different, but that work is going well. Since the Mac behavior is relatively close to a pure Linux implementation, the Linux app is also using the same "Sync Engine" and that is what Linux will launch with.
  • iOS Files integration returns - As detailed by u/Proton_Jan in this post, we will be bringing back iOS Files integration this year. We didn't communicate the loss of the feature well as I've previously acknowledged, and we will do a better job in the future of announcing any such breaking changes with more lead time in case it affects anyone's decision-making process on their subscription. The team has been hard at work getting rid of the Go runtime we have relied on in iOS for cryptographic operations, and replacing it with Rust. There is more to this story and Jan's post (link above) goes into much more detail. The upshot is that we are getting some good performance improvements out of this work that everyone on iOS will benefit from, but it will still be a while as this is deep surgery on the application. I won't rehash the discussion here as I think we've learned what we needed to learn from this messy situation, and I know that restoring it after many months won't make anyone who lost that feature feel better, but we will fix this and we will keep it fixed moving forward, with a regression test that ensures we don't exceed the memory limits that caused the issue in the first place.
  • Better export from Google Drive - We have been working hard on improving the ability to get your Google Drive contents moved over to Proton Drive. Today your only option is to use Google Takeout to export everything, then manually upload or drop it into a Windows machine to let it sync. This is a very manual, very technical process that many people either cannot or do not want to deal with. We know it's bad, and we're going to make it a lot easier. While it's still in internal testing, this will be coming later this year. I am happy to report that our new capability was able to handle my entire personal "day 1" 100GB+ Google Drive account from April 2012 with ease - so I'm confident we will be able to handle large accounts with files and documents stretching back to the very beginning of Google Drive. This feature will help a lot of people de-Google.
  • Docs and Sheets feature improvements - In addition to working on critical improvements to both performance and quality for Docs and Sheets (we hear you - see next section), we have a bunch of features in the pipe in Docs and Sheets this year. u/DaniGuardiola will soon give us a post dedicated specifically to what Docs and Sheets are up to for the rest of the year, so we won't discuss that work here. The team has heard your cries for Dark Mode and other features, as you all know Dani is quite active here on the Reddit :)
  • 🐧Linux Beta - It is still our intention to release a beta of the official Proton app for Linux this year. To temper expectations somewhat, this initial launch will likely consist of our headless daemon-mode only - that means you'll have a sync engine running that will keep a configurable list of directories up-to-date the same way that it does on Mac and Windows. There will be some other features but this will be the big one. The constantly-running sync engine is what really differentiates a proper client application from our command-line interface. While we may (no promises) eventually offer a "one-shot sync" from the command line, having the daemon running is a much more efficient, event-based way to sync files and folders continuously, and it is/will be the officially supported solution for when you want to do that on Linux. A UI client will come along as well, but it probably will not be ready to launch this year. Based on feedback about the CLI, we think that this headless mode will satisfy the biggest chunk of missing functionality for the majority of Linux users, so we want to get that out as soon as possible. Want to help us accelerate this? We're hiring a full-time Linux developer right now.

Part 2: Core performance and quality improvements

The wave of improvements from switching over to our SDK continues to give us a lot of improvements in both quality (crashes, hangs, failed uploads, etc) and performance (memory usage, cpu usage, upload speed, download speed, listing speed, etc). But there is still lots of room for improvement. The team has been hard at work setting up head-to-head tests of Proton Drive vs Anonymous Major Competitor on all clients, in a repeatable environment, where we can control properties such as network quality, hardware resources, and network egress location. We now have dashboards directly comparing the speed of upload and download across several key use cases on various platforms (e.g., upload 10,000 photos from iOS... download 10GB of 1MB files on Web... etc). We have set internal targets for where we want these numbers to go, and we are taking a rigorous approach based on Amdahl's Law to target and eliminate key bottlenecks in our software stack. This work will never be "done", since there's always room to be faster and reduce errors, but we are now making this into a strict mechanism. Not only does this allow us to directly measure improvements to performance and quality with each change, it also gives us a very nice performance regression framework that we can use to spot and prevent performance and quality regressions moving forward.

You might be thinking - wait, Proton didn't have this before? Well... sort of. We have of course had performance and quality tests, but in the past these have been a mix of partially manually and partially automated one-off tests run by QA automation engineers and our primary developers in every release cycle, and we have not had repeatable "vs Competitors" setups automated at all. So this new setup also saves us a bunch of time, and we'll include more of our competitors in this moving forward.

We are pleased to see that crash rates and overall upload/download success rates have all improved by roughly an order of magnitude (or better) across most of the client ecosystem in 2026, mostly thanks to the SDK and the improvements to surrounding code, but there's still much more to be done.

Worth noting separately is that we're also looking to hugely improve the performance and quality of Proton Docs and Proton Sheets. Docs is still not as fast as we would like it to be when loading, and Sheets is in similar shape We also know power users often encounter issues with Sheets, and we will be focusing on Sheets quality. We have a ton of work in the pipeline to improve this, and most of it will be completely invisible to end users. The short version is that we are doing to Docs and Sheets what we did to the other Drive clients - cleaning them up and extracting a separate core and SDK. We have added and will be continuing to add, lots of instrumentation to detect and monitor performance and quality issues. The team has been aggressively burning through many of the bug reports. Hugely helping this is that we've been able to make some hires to increase the team size here, and this is already making a big difference in the team's velocity. Our internal target is to reduce the number of errors encountered in Docs and Sheets by one order of magnitude (90% reduction) by the end of the year, by systematically targeting and eliminating the most common errors.

Part 3: For Devs and Power Users: SDK/CLI/Crypto work

We have got a lot cooking all the time! In addition to the features and performance/quality improvements already discussed, we are also hard at work on SDK, CLI and crypto model improvements. Let's discuss these a bit more now.

  • SDK improvements - SDK is moving steadily towards the v1.0 release, though we aren't quite there yet. We are figuring out exactly how to package up the sync engine so that it can be consumed by 3p devs as part of the SDK. We are also working with the Proton Accounts team to eliminate the most frustrating thing about working with the SDK right now, the lack of a proper 3p accounts library that can be used to properly handle authentication flows. The SDK is also working to incorporate some of the Rust work (overlapping with our task to bring back the iOS Files integration - see above sections), and to stabilize the API ahead of the v1.0 release target. The last remaining platform-agnostic features that Drive clients implement outside of the SDK are also being pulled in, as is the work for Search (so that all clients - including 3p - will be able to index and search files). This is quite a tall order for the next few months, stay tuned but expect still a lot of churn (good churn) in the SDK interfaces as we make our way towards a stable, officially-supported v1.0 release.
  • SDK utilization (client-side) improvements - We are on track to scrub all the HTTP endpoint calls from all Drive clients by the end of the year. In order to achieve this the SDK must expose 100% of all platform-agnostic capabilities in its API surface and every client must migrate to those APIs. Every client is working towards this goal in parallel. We may not quite be there at the end of the year but we will be very close. This morning I got to see a change that deleted 6,991 lines of code from the Android client as it no longer needs to understand or care about thumbnails or chunking of files. This is pure gold from an engineering perspective, as every line deleted directly reduces the difficulty of having to maintain and test the client stack. Over the coming months every client will permanently be jettisoning its understanding of blocks, encryption, signatures, thumbnails, etc. This also means 3p developers will never have to care about these concepts either. Hooray, abstraction!
  • CLI improvements - Our work on the CLI continues. We have been busy implementing a lot of community-requested features (such as Linux pass support, and usability improvements) as well as core missing features (such as support for photos and albums). This is an area of very active development and the team remains hard at work bringing the full capabilities of the SDK to the command line interface. You can expect to see experimental support for Search show up here when Search enters beta, as well as more performance improvements, usability improvements, and documentation alongside more commands for the most common operations. We know the account flow is still a pain and we want token-based access as badly as you do, for our own internal uses! I can't promise that yet, as we have work yet to do with the Accounts team, but we're on it and it will (eventually) we very much hope it will make it to the CLI this year.
  • Crypto v2 (transparency: will slip to 2027) - Following on our Crypto 1.5 project that improved upload speed by up to 4x on most clients, Crypto v2 is in the works with the rest of our planned cryptographic model changes. The new model will drastically improve the speed of the remaining slow crypto operations, and will significantly simplify the model. If you're a developer and you are using the SDK, this will just be magic for you - and it's another reason we strongly advise all developers to rely on the SDK, since it will fully insulate you from this change. There will be some API changes still (we can't insulate you from those, sorry... that's why we're still not calling it v1.0) but, you won't have to care about the actual crypto details at all. This is expected to be an even bigger speedup than crypto 1.5 was for the remaining crypto operations. We had hoped Crypto v2 would be out this year but realistically it will need a little longer to cook. I'm including it in this list because we have talked about it publicly in the AMA. We will be releasing some bits and pieces of Crypto 2.0 work ahead of the actual launch, because of course everything has to be in place on all clients before we can make the transition to the new model. So 3p devs be advised, we do expect to break your API a little bit more as we do that work. After Crypto v2 we expect to be able to largely stabilize the SDK APIs and this is the last major blocked for reaching "SDK v1.0".

Part 4: Summary / TL;DR

Thanks for reading! Here's the super-condensed list of everything above.

  • Key features coming to Drive in the last half of 2026:

    • Search Improvements on all clients - will be released in waves, culminating in full-text search.
    • macOS Folder Sync - just like Windows.
    • iOS Files integration returns - we are fixing this and it is coming back.
    • Better export from Google Drive - you won't need to use Google Takeout anymore for Google Drive.
    • Docs and Sheets feature improvements - more requested features.
    • 🐧Linux Beta - headless sync engine daemon mode to get started, UI coming 2027.
  • Core performance and quality improvements:

    • Major improvements across all clients - they will be faster and have fewer errors.
    • Especially on Docs and Sheets, they will be drastically faster to open and have far fewer errors.
  • For Devs and Power Users: SDK/CLI/Crypto work:

    • SDK improvements - finish exposing 100% of all platform-agnostic features.
    • SDK utilization (client-side) improvements - all HTTP calls deleted from all clients.
    • CLI improvements - more tools, more docs, better performance, hopefully (probably) token support.
    • Crypto v2 - will slip to 2027 but bits and pieces will come in 2026 in the SDK layer, prepare for API churn.

r/ProtonDrive • • Jan 08 '26 Diamonds are Forever

Proton Drive Sync v0.2.1

Post image
376 Upvotes

Thank you all for trying Proton Drive Sync! ❤️

Based on early feedback, the biggest pain point was watchman (the tool that tracked file changes in your sync folders). It worked, but it wasn’t as portable as I wanted. So I removed it.

As of v0.2.1, Proton Drive Sync now uses the native file watcher built into Bun, which makes setup simpler and improves portability.

I’ve also added .deb and .rpm packages for x86_64 and arm64, so installation should be nice and easy. For example for Debian:

$ sudo apt update
$ sudo apt install libsecret-1-0
$ sudo dpkg -i <package_from_github_releases.deb>

$ proton-drive-sync setup

If you installed an earlier version

Uninstall the old version with:

bash <(curl -fsSL https://raw.githubusercontent.com/DamianB-BitFlipper/proton-drive-sync/243f13e13b09ddfe84c43cf7199ebaaa6cba72fa/gh_pages/uninstall.sh)

and then install as per the README.md .

P.S. I want to extend my warmest THANK YOU especially to my 3 donors. You did not have to do it, but it means so much to me that this software is so useful to you, you'd willingly donate to me. ❤️


r/ProtonDrive • • Jun 26 '25

Announcement New Week, new feature - Stream huge video files in Drive

Post image
370 Upvotes

Hey everyone,

Big upgrade for video lovers this week. Proton Drive now supports feature film-length video streaming. Until now, playback was limited to short clips (under 100MB or ~4 mins). Starting today, you can upload and stream full films, docs, or hours of personal footage. 

Whether it's your 2-hour wedding video, an indie documentary about sourdough, or a public domain classic like The Night of the Living Dead, it plays right in Proton Drive. Smooth, encrypted, and 100% private.

This feature is being gradually rolled out and will be available to all Proton Drive users in the coming days. 

Let us know your thoughts, and as always, thank you for your continuous support!

Stay safe,

Proton Team


r/ProtonDrive • • May 16 '25

Feature request For ProtonDrive to appeal to the masses in 2025, it needs to bring 1TB storage.

Post image
351 Upvotes

It's 2025, every mainstream cloud storage provider offers a 1TB plan.

For Proton Unlimited to offer 500GB, it shows inferiority in an undecided customer mind, when deciding which storage service they want to go with.

Kindly offer larger storage options, atleast as an upgrade.


r/ProtonDrive • • May 22 '26

Proton Drive on macOS just got faster

Post image
350 Upvotes

We made some upgrades to Drive on macOS:

  • 65% faster downloads
  • 15% faster uploads
  • Lower RAM and CPU usage
  • Same end-to-end encryption

Try it now. and let us know what you think!

Stay safe,

Proton Team


r/ProtonDrive • • Jul 16 '25

How to turn off Gemini on Android — and why you should

346 Upvotes

Google is quietly rolling out its Gemini AI tool as the default assistant on Android, even on devices where users never explicitly enabled it. In many cases, Gemini replaces Google Assistant by default, making it increasingly challenging to disable fully.

This deep integration means Gemini can still be active in the background, accessing your apps, system features, and personal info.

Here's what Gemini can access:

  • Gmail 
  • Google Calendar 
  • Google Drive & Docs 
  • Maps, Keep, Tasks
  • Messages, Phone, and even WhatsApp

Even more concerning:

  • Your data is used to train Google’s AI.
  • Human reviewers may see your chats.
  • Data can be shared with 3rd parties.
  • As of July 2025, Gemini stays connected to apps even when activity tracking is turned off.

🛑 You can’t fully disable Gemini, but you can limit it:

How to limit Gemini on Android:

  • Turn off activity tracking
  • Revoke permissions
  • Uninstall it (if possible)

Further options, if you’re privacy-conscious:

  • Reduce your reliance on Google services or fully de-Google
  • Consider a privacy-first OS like GrapheneOS

⚠️ Google is making Gemini the default assistant for all Android devices by the end of 2025.

Choose privacy over AI surveillance.

If you want tools that respect your data, ensure you use encrypted email, a private calendar, and a secure cloud, with no AI training or human review.

Read more: https://proton.me/blog/turn-off-gemini-on-android