proton photos

If rclone already moves your other clouds around, adding Proton Drive looks like the obvious next step. It is a real rclone backend, open source, and for scheduled jobs and mounts it does a genuinely good job. The catch only shows up when the job involves photos or videos.

You use rclone to backup a camera roll, then open Proton expecting the Photos tab to be full. The files are there, just not where or what you expected: a folder in My Files full of generic file icons, and nothing in the Photos timeline.

People describe it plainly:

Uploading images via rclone results in generic file icons instead of visual thumbnails inside the Proton Drive interface.

That line comes from a thread where a NAS owner set up rclone with Proton Drive and asked why nothing looked like a photo^[1]. It is not a Proton bug. It is what happens when a general file mover uploads into a service whose photo features depend on extra data the mover never sends.

Bot blober and rclone use Proton's own encryption, so privacy is identical either way. The difference is what survives the upload: thumbnails, capture dates, and which surface the media ends up on. For a photo library, those decide whether the result is usable.

Proton Drive is end to end encrypted, so Proton's servers never see the inside of your files. They cannot generate a preview from the original, because nothing is decrypted until it reaches your device.

That means the uploader has to make the thumbnails. Proton's own apps decode each image or video on your device, build the small preview images, encrypt them, and store them beside the original^[2]. Those extra blocks are what the interface renders as a tile or a preview.

rclone's Proton backend only speaks the file side of the API. It uploads the original and stops there, with no thumbnail blocks and no preview. On the rclone issue tracker this shows up as a known missing feature: the client would have to generate the preview and upload it for the file to display one^[3]. Proton then has nothing to render but a generic icon.

There is also no fix later. Proton Drive has no option to set or replace a thumbnail on a file that is already uploaded, and its servers cannot generate one after the fact. To get a preview you have to upload the file again with a client that sends thumbnails. So the tool you choose on day one decides what your library looks like from then on.

Blober uploads the same thumbnail data Proton's own clients do. Before an upload it decodes the media, produces Proton's standard preview sizes, and sends them alongside the original. Images and videos both show real previews in My Files, and photos get a proper tile in the Photos timeline. Audio gets the same care, and here Blober goes further than rclone could: a music file's embedded album art (the cover on an mp3 or m4a) is read straight off the file and uploaded as its thumbnail, so audio shows a real cover tile instead of a generic icon.

Proton Photos organizes the timeline by each photo's capture time. That value comes from the photo's EXIF data and is set when the file is uploaded. When it is missing, a photo has no real capture date, so it lands wherever upload time puts it.

The rclone backend documentation is direct about the underlying gap: the backend does not support updating modification times yet^[4]. rclone treats photos as files. Migrate a few years of pictures that way and you get a timeline that groups by upload date, not by when anything was taken.

Blober reads the EXIF capture time and hands it to Proton with the upload, and it carries over the file's own dates from the source. Photos group under the day they were actually taken.

Proton keeps two surfaces under one login: My Files, a folder tree, and Photos, a timeline with albums. Where a photo lands decides how you see it later.

rclone is a file backend, and it only ever sees the file side. Its remote maps to the My Files tree, and rclone forum threads describe trying to reach Proton's separate Photos area and failing, because that library sits outside the folder tree the backend exposes^[5]. Sync a camera roll this way and every picture lands in a folder, none of them appear in the Photos tab, and there is no album step to put them there.

Blober is built around the destination you choose. Pick the Photos surface and each upload becomes a timeline photo. Pick My Files and it is a regular file. Because Proton Photos is a flat timeline without folders, Blober automatically keeps the path rules you set sensible on either destination.

Most of the rclone column below comes from rclone's own Proton Drive documentation^[6].

	Blober	rclone (Proton Drive)
Interface	Desktop app	Terminal commands and config files
Proton login	Sign in inside the app	Username and password prompts plus 2FA or OTP, with an optional mailbox password for two-password accounts
Keys	Handled for you	Encryption keys must already exist from a normal browser login, and there is no official Proton API documentation to lean on when something breaks
Status	GA product	Community backend, still marked Beta and classed as Tier 4
Thumbnails	Generated for images, videos, and audio (album art)	Not generated
Capture time	Read from EXIF	Not set
Modification times	Preserved	Not supported by the backend
Photos surface	A real destination	Files and folders only
Fits best	Photo migrations, people who do not live in a terminal	Scripted sync, mounts, headless servers

That last row is the honest summary. rclone is the right tool when the job is moving files on a schedule or mounting Proton as a drive and you do not care about Proton's photo features. It is the wrong tool when the point of the move is getting a photo library to look right inside Proton.

If you are migrating a photo library, especially out of Google Photos, you want the uploader to behave like Proton's own client: generate previews, carry the capture dates, and put media where the Photos tab can show it. That is what Blober does.

If you are a terminal user syncing folders, running backups on a schedule, or mounting Proton on a server, rclone is a strong, established choice and you already know whether its tradeoffs matter to you.

For a photo library, that choice is the difference between files in a folder and a Photos tab that works the way Proton intends.

Why do my rclone-uploaded photos have no thumbnails in Proton Drive? Proton is end to end encrypted, so its servers cannot create previews; the uploading client has to. rclone's backend only moves files and sends no thumbnail data, so Proton shows a generic icon.

Can I add a thumbnail to a file I already uploaded with rclone? No. Proton Drive does not let you set or replace a thumbnail on an existing file, and its servers cannot generate one later. You would have to upload the file again with a client that produces thumbnails, which is what Blober does.

Does rclone upload into Proton Photos albums or the timeline? No. Its Proton backend works with files and folders in My Files only. Photos uploaded that way do not appear in the Photos timeline and are not added to albums.

Does Blober make thumbnails for audio files? Yes, and rclone cannot. Blober reads a music file's embedded album art (the cover on an mp3 or m4a) and uploads it as a Type1 thumbnail, so audio gets a real cover tile instead of a generic icon. rclone generates no thumbnails at all.

How stable is rclone's Proton Drive backend? It is a community backend. rclone ships it as Beta and Tier 4, Proton publishes no official API documentation, and rclone's own docs warn that Proton's protocol changes may leave some accounts incompatible.

For Proton Drive, is Blober better than rclone? For scripted file sync into folders, rclone is the established terminal option. For a photo library, where previews, capture dates, and the Photos timeline matter, Blober is the better fit because it uploads the thumbnail and metadata Proton needs. Both encrypt your data the same way.

• How to Move Google Photos to Proton Drive
• Proton Drive vs Proton Photos: What's the Difference?
• Proton Photos vs Google Photos
• Migrating To or From Proton Drive
• What Is Proton Drive? Features, Plans, and What It's Used For

You cannot move photos from My Files into Proton Photos. You are not missing an option or a setting: the two live in separate storage areas of your account - My Files holds folders, Proton Photos is a timeline (plus albums) - and Proton does not offer a way to move a photo from one to the other.

The only way a photo gets from My Files into the Photos timeline is to download it and upload it again into Photos. That is the community workaround: "You can upload them via the web version - not ideal but its a way of doing it"^[1].

This is not user error. The most upvoted answer to exactly this question on Proton's forum says it plainly: "No, you are not doing anything wrong, this is not possible at the moment"^[2]. The thread is full of the same frustration:

• "I uploaded all my images in my proton drive, but I want to have them at the photos section. I can't seem to move them. Am I doing something wrong?"^[3]
• "The photos section is pretty much reserved for photos backup from phones at the moment. If you manually import, they go to files instead."^[4]
• A Proton idea on UserVoice asking for "a way I could import photos from files uploaded to the photo section of drive from already existing directories within proton drive" has gathered dozens of votes^[5].

Proton's supported path for getting photos into Photos is the import flow: download your files locally, then upload them through the Photos tab (or the Windows app's Photos import). For a handful of files that is fine. For a real library it is a chore:

• One by one. The web UI has no "select all in this folder and send to Photos," so you are clicking through hundreds of files.
• No resume. A browser upload that fails halfway starts over, and nothing tracks which photos you already moved.
• Duplicates are silent. Proton Photos does not dedupe on upload - re-uploading a photo that is already in the timeline creates a second copy instead of replacing it.
• Cleanup is manual. After the upload you still have to delete the originals from My Files, file by file, or you end up with every photo in two places.

The same problem runs the other way: because Photos is built around phone backup, screenshots, PDFs, and documents you meant to keep as files can end up in the timeline, and there is no UI to send them back to a folder.

Blober connects to Proton Drive and treats both surfaces - My Files and the Photos timeline - as ordinary source and destination folders. It streams files from My Files to Photos.

To move your whole photo library from My Files to Proton Photos:

1. In Blober, add Proton Drive as the source and browse into My Files.

2. Add Proton Drive as the destination and choose the Photos surface.

3. Select all photos with one glob instead of clicking files. In Source Configuration, set the Include Pattern to:

   **/*.{jpg,jpeg,png,webp,heic,gif}

You can also use the built-in Raw Photos extension preset for CR2/NEF/ARW/DNG/RAW.

4. Run the workflow as a move. Blober copies each photo into Proton Photos and deletes the original from My Files in the same run.

The whole library lands in the Photos timeline in one run. Nothing is left behind in My Files, and there is no local download folder to clean up.

If files that are not photos ended up in your timeline - screenshots, documents, archives, or videos you would rather keep as ordinary files - Blober moves them back just as easily:

1. Set Proton Photos as the source and My Files (a folder) as the destination.

2. Use an Include Pattern that targets non-photo files, for example:

   **/*.{pdf,doc,docx,xls,xlsx,txt,zip}

   or exclude image extensions with an Exclude Pattern of **/*.{jpg,jpeg,png,webp,heic,gif}.

3. Run it as a move. The non-photos leave the timeline and land in a real folder tree where you can organize them.

Can I move photos from My Files to Proton Photos in the web app? No. Proton offers no move between the two surfaces. The community answer is "not possible at the moment," and the only manual path is download + re-upload through the Photos import flow.

Why doesn't Proton support this? My Files and the Photos timeline are separate storage areas, and Proton does not offer a move between them. The only way a photo crosses is to download it and upload it again, which is what Blober automates.

Does Blober move the photos for me? Yes. It downloads each photo and uploads it into Photos, because that is the only way a file crosses from My Files to Photos. What Blober automates is the selection, the transfer, the retry, and the cleanup, so you do not do it by hand in a browser.

Will moving my photos create duplicates in Photos? Proton Photos does not dedupe on upload. A Blober move deletes each original from My Files after it is copied, so a re-run of the same workflow finds nothing left to move and does not duplicate anything.

• Proton Drive vs Proton Photos: What's the Difference?
• How to Move Google Photos to Proton Drive
• Proton Photos vs Google Photos
• Select Files With Glob Include and Exclude Filters in Blober

Google Photos is convenient, but it has costs people increasingly want to avoid: 15 GB of free storage shared with Gmail and Drive, a default compression mode that downsizes originals, an inactivity policy that can delete your content, and a company that analyzes your photos and has folded Gemini AI into the product^[1]. The r/degoogle community is full of people asking for a way out, like the post "Alternatives to Google Photos?"^[2].

There are five realistic categories of alternatives, and the right one depends on how much you value privacy, whether you are willing to self-host, and whether you want a photo-specific app or just encrypted storage. The thread's consensus: for a managed privacy-first service, Ente Photos; for self-hosting, Immich; for a photo surface tied to a broader encrypted cloud, Proton Photos.

This round-up compares them all with current, sourced numbers, and links to the migration guides at the end.

Alternative	Type	Privacy model	Free tier	Price (paid)	Best for
Ente Photos	Managed, E2E encrypted	End-to-end encryption, open source, self-hostable	10 GB free forever	From $2.49/mo[3]	Privacy-first with a Google-Photos-like app
Proton Photos	Inside Proton Drive	End-to-end, zero-access, Swiss	5 GB free	From $4.99/mo (200 GB)[4]	Privacy plus a broader encrypted cloud
Immich	Self-hosted, open source	Your server, your keys	Free software; you pay for hardware	No subscription	Full control, face recognition, no monthly fee
iCloud Photos	Apple ecosystem	Encrypted in transit/at rest; Apple holds keys	5 GB shared iCloud	Paid iCloud tiers[5]	People already in the Apple ecosystem
Amazon Photos	Managed	Encrypted; Amazon holds keys	5 GB, or unlimited photos with Prime	Plans from $1.99/mo[6]	Prime members with big photo libraries
Flickr	Photography community	Photos are public/private by setting; no E2E	Free tier with upload limits	Pro subscription[7]	Photographers who want a community and portfolio
Backblaze B2 / S3	Object storage	Standard cloud encryption	None	About $6/TB/mo[8]	Cold archival, not daily photo browsing

Ente is the most common recommendation in the de-Googling community, and the top comment on that thread recommends it for anyone who does not want to self-host^[9]. It offers end-to-end encrypted backups, on-device face recognition, a zero-knowledge AI search, shared albums, memories, and a family plan, all open source with apps for Android, iOS, web, macOS, Linux, and Windows^[10]. The free tier is 10 GB forever, and paid plans start at a few dollars a month^[11].

Proton Photos is the photo surface of Proton Drive: the same end-to-end encryption, automatic mobile backup, albums, favorites, and filters, with a free 5 GB plan and paid Drive Plus tiers^[12]. It is the strongest choice if you also want an encrypted cloud for files, Docs, and Sheets, not just photos. It is younger than Google Photos: no face recognition and no AI search yet, which the community has loudly requested^[13]. See the full comparison in Proton Photos vs Google Photos.

If you do not want to rent storage from anyone, Immich is the leading open-source, self-hosted photo manager. It offers automatic mobile backup, facial recognition, shared albums, and search, running on your own server^[14]. The trade-off is exactly what self-hosting always costs: you provide the hardware, keep it updated, and own the failure domain. For a few gigabytes of phone photos it may be overkill; for a large family archive it gives you total control.

These replace Google Photos without really solving the privacy problem; they just move your photos into a different company's cloud:

• iCloud Photos: the natural choice inside the Apple ecosystem, with 5 GB of shared free iCloud storage and paid tiers^[15].
• Amazon Photos: "Prime members get unlimited full-resolution photo storage and 5 GB for video," with 5 GB for everyone else and paid storage from $1.99/mo^[16].
• OneDrive: Microsoft's storage, with photo backup built into the mobile app; storage is shared with the free OneDrive tier and Microsoft 365 plans^[17].

These are fine if your goal is simply to leave Google, but they do not change the underlying deal: your photos live with a company that holds the keys.

• Flickr: the photography community and portfolio option, with a free tier and a Pro subscription for unlimited uploads^[18]. Great for photographers who want visibility, not a private family archive.
• Backblaze B2 and S3-compatible storage: for the 3-2-1 backup mindset, object storage at around $6/TB/mo is the cheap way to keep an independent, cold copy of your library^[19]. It is storage, not a photo app: you pair it with a tool to browse or transfer. Blober supports B2 and the whole S3 family, so this is a natural pairing if you want a private archive you fully control. See How to Backup Google Photos Without Google Takeout for the workflow.

None of this matters until your library is out of Google Photos, and that is the step every alternative expects you to handle yourself:

• Google Takeout is the official export, but it is slow, splits into 2 GB zips, and flattens albums (Proton's own import guide even warns about scattered folders)^[20].
• Blober connects to Google Photos directly and transfers the library to any supported destination, including Proton Drive, pCloud, Backblaze B2, or a local drive, without Takeout. See How to Move Google Photos to Proton Drive and How to Backup Google Photos to pCloud.
• Whichever destination you pick, keep the originals until the transfer finishes and verify a sample before deleting anything from Google.

• Privacy + a managed app, no self-hosting: Ente Photos or Proton Photos.
• Total control, no subscription: self-host Immich (or a NAS).
• Already on Apple or Prime: iCloud Photos or Amazon Photos are the least-effort swaps.
• Photography portfolio: Flickr.
• Cheap independent archive: Backblaze B2 / S3 storage.
• Also want an encrypted file cloud, Docs, and Sheets: Proton Photos via Proton Drive.

What is the best private alternative to Google Photos? For a managed service, Ente Photos is the community favorite: end-to-end encrypted, open source, 10 GB free, with face recognition and shared albums^[21][22]. For a photo surface inside a broader encrypted cloud, Proton Photos.

Is there a free self-hosted Google Photos alternative? Yes. Immich is open source and free; you only pay for the hardware it runs on^[23]. It includes facial recognition and automatic mobile backup.

Does Amazon Photos give you unlimited storage? For Prime members, unlimited full-resolution photo storage plus 5 GB for video. Non-Prime customers get 5 GB total, with paid plans from $1.99/mo^[24].

How do I move my Google Photos library to another service? You can use Google Takeout (slow, zip-based) or a direct transfer tool. Blober connects to Google Photos and transfers to Proton Drive, pCloud, B2, or a local drive without Takeout. See How to Backup Google Photos Without Google Takeout and How to Move Google Photos to Proton Drive.

Will Google delete my photos if I stop using Google Photos? Google's policy states that if you are inactive in Google Photos for 2 years or more, your content may be deleted^[25]. This is one of the strongest reasons to hold an independent copy.

What about Proton Photos specifically? It is the photo surface inside Proton Drive: end-to-end encrypted, 5 GB free, paid tiers start with 200 GB on Drive Plus, with albums and automatic backup but no face recognition yet. See Proton Photos vs Google Photos.

• Proton Photos vs Google Photos
• How is Proton Drive different to Proton Photos?
• How to Move Google Photos to Proton Drive
• How to Backup Google Photos Without Google Takeout
• How to Backup Google Photos to pCloud
• Migrating To or From Proton Drive

Proton markets both "Proton Drive" and "Proton Photos," and the two names trip people up when they are deciding where their photos should go, or where their photos end up after a migration.

Proton Photos is not a separate product. It is the photo-and-album surface inside Proton Drive. Proton Drive is the general-purpose file storage product: folders, sync, sharing, Docs, Sheets. Proton Photos is the media surface built on top of it: timeline, albums, favorites, filters, EXIF-based organization, automatic mobile backup. Both share the same end-to-end encryption, the same storage quota, and one login.

If you upload a JPEG through the Photos tab, it appears in your photo timeline. If you drop the same file into a folder in My Files, it lives in the file tree. Knowing which surface holds your photos matters more than it sounds, because it decides how they are organized after a Google Photos migration.

Proton's web app has two main views:

	Proton Drive	Proton Photos
URL	drive.proton.me	drive.proton.me/u/0/photos
What it is	General file storage	Photo and video surface
Organized by	Folders, subfolders, file names	Timeline (date), albums, favorites, filters
Typical content	Documents, downloads, work files, archives	Camera roll, photos, videos, albums
Key features	Folder sync (Windows/macOS), sharing, Proton Docs and Sheets	Automatic mobile backup, albums, favorites, filters[1]
Sharing	Files and folders with password and expiry[2]	Albums shared by email invite, with view or contribute roles[3]
Encryption	End-to-end, zero-access	Same end-to-end encryption, including album names and photo locations[4]
Storage quota	Your Proton Drive quota	Same quota, shared with Proton Drive

The rule of thumb: Photos surface is for things you want in a timeline and albums; Drive surface is for everything else.

• Camera-roll backups from the iOS and Android apps land in Proton Photos, because automatic photo backup uploads to the Photos surface^[5].
• When you use the Windows app's "Photos import" feature, imported pictures are sorted into albums automatically^[6].
• Files you drag into My Files in the web app go to the Drive surface as ordinary files, even if they are images.

The practical difference is organization: Photos gives you a date timeline, albums, favorites, and filters. Drive gives you a folder tree. A photo sitting in a Drive folder is still encrypted and safe, but it will not show up in your Photos timeline unless it is in the Photos surface.

When you move a library out of Google Photos, the destination determines the result:

• Into Proton Photos: your photos are organized into a timeline and albums, which is the closest to how Google Photos worked. Proton's official Google Photos import does exactly this: it takes your Takeout folder and "automatically upload your photos and then sort them into albums"^[7]. Both Google Photos and Proton Photos don't have folders. If you want the timeline and albums, point it at Photos.
• Into Proton Drive folders: your photos are files in a folder tree. This is fine for archiving, but you lose the timeline and album view unless you then move them into Photos. If you want date-based folder organization, point the destination at a My Files folder.

There is a catch with the official Google Photos import that also matters here: it builds albums from folder structure, and Google Takeout can scatter photos from the same year across different parts, so Proton's own guide recommends manually reorganizing by year first^[8]. For a cleaner path, see How to Move Google Photos to Proton Drive, which compares the Takeout route with a direct transfer.

Choose Proton Drive if you want a general encrypted file store: documents, downloads, work files, synced folders, shared files with password protection, and Docs/Sheets.

Use Proton Photos for your personal media: automatic camera-roll backup, a date timeline, albums for trips and events, favorites, and filters.

In practice you get both with the same account. The question is only which surface your media ends up in, and that is decided by where you upload it. For anything photo-like, put it in Photos if you want the timeline and albums. For everything else, use Drive.

Is Proton Photos a separate subscription? No. Proton Photos is part of Proton Drive. It uses the same storage quota and the same plan, so 200 GB of Drive Plus covers both your files and your photos^[9].

Are my photos in Proton Photos encrypted? Yes. Everything in Proton Photos uses the same end-to-end encryption as Proton Drive, and Proton says album names and photo metadata like locations are encrypted too^[10].

If I upload photos to Proton Drive folders, will they appear in Proton Photos? Not automatically. Files in the Drive surface live in the folder tree; the Photos surface has its own timeline and albums. Import through the Photos flow (or the Windows app's Photos import) to get photos into the Photos surface.

Which surface should I use to migrate Google Photos? Proton Photos, if you want the timeline and albums to match how Google Photos worked. See Proton Photos vs Google Photos for the comparison and How to Move Google Photos to Proton Drive for the mechanics.

Can I move files between the Drive and Photos surfaces? Proton's import flow is the supported path for getting photos into the Photos surface. For moving the other direction, the general file-transfer story for Proton Drive is covered in Migrating To or From Proton Drive.

• How to Move Photos from My Files to Proton Photos
• Proton Photos vs Google Photos
• How to Move Google Photos to Proton Drive
• What Is Proton Drive? Features, Plans, and What It's Used For
• Alternatives to Google Photos

Google Photos is the default home for most people's photo library, and it has real costs: only 15 GB of free storage shared with Gmail and Drive, a compression option that downsizes originals, an inactivity policy that can delete your content, and a business model built on analyzing your photos. Proton positions its Photos feature as the private alternative, and the demand is real: a top r/ProtonDrive post titled "Make Proton Photos more like a real alternative to Google Photos" collects a long list of the gaps users hit^[1].

Proton Photos is the photo surface inside Proton Drive. It beats Google Photos on privacy: every photo is end-to-end encrypted before upload, nothing is compressed unless you choose it, and Proton says it does not scan your photos or train AI on them. Google Photos still wins on convenience: mature face recognition, AI-powered search, and a far larger feature set. If your priority is keeping photos private and unmodified, Proton wins. If you rely on Google's AI search and automatic face grouping day to day, you will feel the difference.

This article is the honest feature-by-feature comparison. For the actual move, see How to Move Google Photos to Proton Drive.

Proton Photos is not a separate app with its own login. It is the photo and album surface of Proton Drive, at drive.proton.me/u/0/photos. Your photo quota is your Proton Drive quota (5 GB free, 200 GB on Drive Plus), and the photos share the same end-to-end encryption as every other file in Proton Drive^[2]. Proton's own framing is direct: "Unlike Google Photos, Proton Drive empowers you to control your pictures, videos, and albums with uncompromising privacy and security"^[3].

Feature	Proton Photos	Google Photos
Free storage	5 GB (shared with Proton Drive)	15 GB (shared with Gmail and Drive)
End-to-end encryption	Yes, zero-access. Proton says "no one, not even Proton, can access your files"[4]	No. Google holds the keys and can read your photos
Compression	Originals stored as-is, no forced downscaling	"Storage saver" (previously "High quality") compresses photos[5]
Face recognition	Not available	Yes, mature, automatic
AI search	No (search by date, type, favorites, filters)	Yes, natural-language and object search, Gemini integration
Albums	Yes, shared albums with email invites, favorites[6]	Yes, shared albums
Auto mobile backup	Yes, iOS and Android[7]	Yes, iOS and Android
Metadata / EXIF	Preserved; album names and photo locations are encrypted[8]	Preserved, but readable by Google
Scanning / AI training	Proton states it does not scan photos or use them to train AI[9]	Google analyzes photos (faces, objects, locations) and has folded Gemini into Photos
Inactivity deletion	No such policy documented	Google may delete content after 2+ years of inactivity[10]
Jurisdiction	Switzerland, open source, audited	US-based, subject to US law
Price (paid)	Drive Plus: 200 GB, see pricing	Google One paid tiers (see plans)

End-to-end encryption. This is the entire point. Proton encrypts photos, album names, and metadata like locations on your device before upload, so even Proton cannot read them^[11]. Google Photos is not encrypted this way; Google can see your photos, and Proton's marketing presses the point that Google "scans and analyzes the faces" in them^[12].

No forced compression. Google's "Storage saver" mode downsizes originals to fit more in your quota, and it is the default that most people have been running for years. Proton stores originals as-is. If you care about keeping full-resolution files, that is a meaningful difference for a large library.

No AI-training or advertising pipeline. Proton's position is that your photos are "too personal to be scanned by surveillance systems or analyzed by algorithms"^[13]. Google, by contrast, has integrated Gemini into Google Photos and uses the data for its own models.

You are not renting against a deletion policy. Google's own support page states: "If you're inactive in Google Photos for 2 years or more, your content may be deleted"^[14]. Proton does not have an equivalent inactivity-deletion policy for stored photos.

Be honest about the gaps before switching, because they are real:

• Face recognition. Google automatically groups photos by person and lets you search by face. Proton Photos has no face recognition today.
• AI search. Google's natural-language search ("photos of my dog at the beach") is best-in-class. Proton searches by date, type, favorite, and filter, not by content.
• Mature editor and ecosystem. Google Photos has editing tools, shared libraries, partner sharing, and deep Android integration. Proton's Photos surface is younger.
• Bigger free tier. 15 GB vs 5 GB, both shared with the rest of the account.

The r/ProtonDrive thread that calls for Proton Photos to be "more like a real alternative" lists the specific gaps users hit^[15]:

1. Viewing on-device photos alongside cloud photos in one interface.
2. iCloud-style storage optimization (full original in the cloud, small preview on the device).
3. A dedicated duplicates view to find and remove duplicate files.
4. Editing tools (the post suggests Lumo image editing).
5. Editing the captured date of a photo to correct wrong timestamps.
6. A standalone Proton Photos app.

None of these are dealbreakers for a private archive, but they matter if you treat Proton Photos as a full Google Photos replacement for daily browsing.

	Proton	Google
Free	5 GB	15 GB
200 GB	Drive Plus (see pricing)	Google One paid tiers, see plans
500 GB	Proton Unlimited (VPN + Mail + Calendar + Pass)	Google One paid tiers

Proton's paid tier is a flat storage subscription. Google One bundles other Google benefits, but the storage is the part that matters for photos. Prices drift, so check the Proton Drive pricing page and Google One plans before deciding.

Choose Proton Photos if you want originals kept unmodified, end-to-end encrypted, in a zero-access service you are not renting against a deletion policy. Choose Google Photos if you rely on face recognition, AI search, and editing day to day and are comfortable with Google reading your library.

If you switch, the mechanics are covered in depth in How to Move Google Photos to Proton Drive, which compares Proton's official Takeout-based import with a direct transfer, and Migrating To or From Proton Drive covers the general Proton Drive migration story.

Is Proton Photos free? Yes. It is the photo surface of Proton Drive, and the free plan includes 5 GB of storage for photos and files. Proton says that is "enough space to store more than 1000 photos" at an average size of 4 MB^[16]. Paid plans start with 200 GB on Drive Plus^[17].

Does Proton Photos compress my photos? No. Originals are stored as-is. Google's "Storage saver" mode, by contrast, compresses photos to save space^[18].

Does Proton Photos have face recognition? Not yet. Google Photos has automatic face grouping; Proton Photos does not. It is one of the most-requested gaps in the community^[19].

Can Proton Photos replace Google Photos? For private, encrypted photo storage: yes. For a drop-in with Google's AI search, face recognition, and editing: not fully yet. This article walks through exactly what you gain and what you give up.

Is Proton Photos the same as Proton Drive? No. Proton Drive is the general file-storage product (folders, sync, sharing, Docs and Sheets). Proton Photos is the photo-and-album surface inside it, optimized for media. See How is Proton Drive different to Proton Photos? for the full explanation.

How do I get my existing photos out of Google Photos? Google has no bulk "download all" button, and Takeout is slow and Windows-only for Proton's import. See How to Move Google Photos to Proton Drive and How to Backup Google Photos Without Google Takeout for the options.

• How to Move Google Photos to Proton Drive
• How is Proton Drive different to Proton Photos?
• Alternatives to Google Photos
• Migrating To or From Proton Drive
• How to Backup Google Photos Without Google Takeout