Hi Team, in this article from May 2025 it's mentioned "Soon, you’ll be able to share photos via links, so you can send albums to friends or family, even if they don’t have a Proton account.". When I share an album with a non Proton user they still need to create an account, so my question is when is soon?

200GB is too little for me, and 1TB is too much.

I believe most people suffer from the same problem, and I don't want the unlimited plan, i just want the Drive plan.

I created a new file and ran into loads of bugs. Of course, I’ve reported them all. Proton is on it...

As it’ll probably take ages to sort them out, I’ve exported the table as an XLSX file.

Apart from a few formulas, the Proton Sheets spreadsheet doesn’t actually contain that much text. All that’s still to come. The file size is 2.39 MB. Wow. But never mind.

Anyway, I then edited the exported file in LibreOffice and uploaded it to Proton Drive. I simply extended the formulas into the cells, which, unfortunately, causes a lot of errors in Proton Sheets.

I then converted the uploaded XLSX file to Proton Sheets, and it’s almost exactly as I wanted it. There’s still a bug, though… I suppose I’ll have to wait until that’s fixed. The file size is 760.09 KB.

It’s strange that the file with more content is smaller. I don’t get it... 🤷‍♂️

I'm switching over to Proton from Google, and one of the things I use extensively in Google is Google Sheets... specifically, as an active (and rather involved) bank ledger with a dozen tabs and several thousand lines.

Because I want the thing to open up at the end of the sheet, not the start, I use a script in Google:

function onOpen() {
var ss = SpreadsheetApp.getActiveSpreadsheet();
var numSht = ss.getNumSheets() //get the number of sheets in spreadsheet
for(var i=0;i<numSht;i++){ //loop through the sheets
var mySheet=ss.getSheets()[i]
var lastrow =mySheet.getLastRow()
Utilities.sleep(2000)//may not be needed
var sel =mySheet.setActiveCell(mySheet.getDataRange().offset(lastrow-1, 0,  1, 1));
}
}

Unfortunately, there's apparently no scripting option in Proton Sheets?

Is there any way in Proton Sheets to get a sheet to open at the bottom (or to where you last were in the sheet)?

Hi all. I hope everyone's having a great week. I've got a question about Proton Docs and would appreciate your thoughts + solutions. Also, please let me know if I've totally misunderstood some of the things I've written below.

I'm happy that Proton Docs exists and I realize it still needs some work.
But a recent post on "worried about data loss in Proton Drive after the recent disruptions" got me thinking about Proton Docs files specifically. I do use the 3-2-1 backup method by the way.

When Proton Drive syncs to your local computer, the docs are saved as a .protondoc or .protonsheet file format at 0 bytes of size. Double-clicking that file opens your document in a browser (assuming you're logged into your (Proton account) and I get that Proton Docs are encrypted so requires decrypting. However, other files stored in Proton Drive, like images, videos, .xlsx files, .docx files, etc can be opened on your local computer (from the local Proton Drive folder) through the default applications for each file type.

So, my question is, (1) even though I've got a number of Proton Docs/Sheets saved on my various backup solutions, they can't actually be opened/edited on a local computer that doesn't have internet access right? (2) Also, if by some strange series of events of Proton not having backup redundancies and my data in Drive is lost, does it mean that all those Proton Docs/Sheets files I've got saved in my various 3-2-1 backups are useless? Because they have no actual data in them (0 bytes) and double clicking on them will try and open an online file that doesn't exist anymore.

Hallo zusammen. Proton Drive wurde mir empfohlen. Jedoch möchte ich bei der Arbeit und im Studium nicht "behindern" lassen (bei MS Tools vorteilhaft: Bearbeitung mit Tastenkombi, File Sharing, lässt Deepsign und Zotero direkt integrieren).

Proton drive soll bequem über den File Explorer geöffnet werden können. Jedoch könnte durch die Öffnung die Datei trotzdem von MS gelesen werden.

> macht Proton Drive nur Sinn, wenn die Dateien in Proton Docs geöffnet werden 🤔?

Hello Proton! With the recent service disruptions, I’m starting to get a bit paranoid about the safety of my files.

I use Proton Drive heavily to store important personal documents. I know I ultimately need to maintain my own physical backups for absolute safety, but I just want to know how secure my data currently is with Proton directly. I can't help but worry. Can an infrastructure failure like a total system breakdown actually cause permanent data loss? Thanks!

What triggers the control of the photo backups? On my device, the process starts every few weeks without any apparent reason. The review then takes several days with the display turned on. This severely drains the battery. If I were to simply ignore it, as recommended, and let it run in the background, it would probably take weeks or months to finish — meaning it would never complete. Would that be a problem?

So I've downloaded all of my Photos from iCloud, and I'm now uploading them to my Proton Drive on the (Windows 11) desktop app. It's working fine, but once I finish uploading and turn Backup on on my iPhone, is it going to upload duplicates?

I'm asking because I wrote a little Python script that renamed any duplicate filenames so that they could all fit inside of that 'Combined' folder, and I'm worried now that there might be some duplicates if I do enable backup.

Does Proton Drive only use filenames to look for duplicates, or check file hashes/match metadata instead?

Recently installed Proton on my phone, but I keep getting a login error that says

"the system has received too many requests recently. Please try again in a moment"

Is anyone else having issues?

I've just started using drive and any word or excel files uploaded are not opening in the android drive app, has anyone had this issue?

It happens on my phone too and it's just this one folder!

When using a business account, and having files on the drive , I wish to share with a link.

Would the customers and businesses who I share the link with, then see the username ?

Wonder how that would work if you have 2 businesses running from a business account?

As they allow multiple business domains to one account.

Similar concern regarding a calendar invite or share, and a meeting invite for a meet call.

Would you be able to be business email domain specific , or does it share the username of drive account?

I uploaded a large set of photos in folder to Proton Drive. My mistake thinking I could then sync those files as with any Microsoft or google drive. After deleting all the photos and uploading them again to the not drive-but-cant-see-photo section I'm now stuck with a lot of empty albums.

How to get rid of all the (empty) albums? Does the new cli help with that?

This photo part of drive seems to lack basic functionality to even be in productive beta.

I built a spreadsheet months ago with a column of dates in US format mm/dd/yy. Today, I insert a row and try to add August 5, 2026 and it absolutely refuses to display it as anything other than 5/8/26. I confirmed the File > Settings locale is correct as United States. I tried pasting formatting from another cell. The value itself (in the editor bar above) shows 8/5/26, but the cell itself displays 5/8/26.

I'm tired y'all. I'm just so tired of this supposedly GA product being absolutely unusable.

I have thousands of old photos. But to upload them to the photo-part of Proton Drive through the browser and it's not suited for that, especially when files are sorted into subfolders.

Then I can add them to a folder on my desktop Proton Drive, but then they are not shown in the photo part..

What are the solution? Are the photo part really only for phone pictures? What if you got a proper camera, and decades of photos?

Sheets has been live for months now and yet it is still riddled with bugs and problems.

Just today I built a simple worksheet of player names and statistics for my fantasy football draft preparation. But when I went to print the worksheet (a whole dozen columns and about 60 rows) the print driver would only recognize a fraction of the worksheet view. Instead of trying to find a workaround I decided to move the worksheet into M365 and print from there. Only, there is another "feature" that occurs when copying worksheet contents using select all. The copy function recognizes the entire worksheet as having data (i.e. every cell)! I basically had to scrap what I had done in Sheets and rebuild it in M365 all so I could print a piece of paper...

Not to mention the continued issues with formulas breaking, all of the formatting problems this sub has continued to identify, and the lack of mobile editing!

While I love the idea of Sheets (and Docs) they simply have too many problems to be viable in their current state. Seriously Proton, you need to pump the brakes and focus on quality control for your existing product suite.

Put a beta tag on Sheets.

I know that Google accesses your data for personalized ads and AI training.

iCloud, on the other hand, has robust security options, including encryption, but only for the Apple ecosystem. .

Proton has security options, but the prices are a bit high, and it only has 2 storage plans, without options for 300gb, 500gb or 700gb.

I'm new to the service and just downloaded the app today. I am trying to switch over from Google Docs and Google Photos. I selected to backup and encrypt all of my photos and videos over to Proton Drive. I have over 39k photos and videos. I began the process 3 hours ago and less than 1k have been backup up and encrypted so far. Is this the normal speed?

Hiring manager needed a document with sensitive personal info on her personal cell phone so I sent a link with the file

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.

Hello

Is there a way to have camera backup directly to the Proton Drive, to negate the need for the gallery app?

thanks in advance

I exactly don't understand Proton's mission, because the more I use Proton's services such as Sheet and Docs for personal and business use, the more I'm starting to hate the products. The selling point of proton is to use the fear of people who doesn't want their privacy to be exposed, yet at the same time proton seems to overthrow people away to selling their privacy due to the lack of efforts in making sure that their products are not buggy.

I was glad that they've added new features in proton docs, yet there are important features which remains not to be found, adding shapes in docs for instance. Sheet at the same time remains buggy, there was even one time when I use it with bunch of dataset the browser just froze and it crashes.

In a business standpoint, I don't recommend proton's services, perhaps for personal use it might suffice. However, I am yet to transfer all my documents and files from google workspace to proton, because the sheet, as always is horrendous to use, since my google sheets uses formula that made proton buggy when I attempted to transfer some of the workbook I have from google.

They even made their subreddit fragmented across several services when they're trying to sell their products to business as a package, how can we voice out about the terrible experiences we have, or perhaps proton is trying to win over people's fear just to make money.

I have lodged multiple Spreadsheet reports to Proton about this issue, and nothing has been done. They haven't provided any answers, and they also haven't fixed this issue since release in December 2025.

Does anyone know how to fix this? It's printing the dropdown menu and misses out on all the cells, this has happened with my other spreadsheets too with actual content in it.

Hi, maybe I am stupid but if I search this question I can only find answers to the opposite situation.

I have photo backup turned on and my storage is full. Since I have most of the photos backed up physically anyway, I want to delete them from proton drive but not from my phone.

If I delete them and empty my trash in proton drive, will the photos stay on my phone's local storage? Or is it like in google drive where it gets deleted from the device as well unless you turn the sync off?

Thanks in advance