Ask HN: Alternatives to Google Photos?
With Google ending its free photo storage policy in a few days[0], I'm considering switching to another service. I've poked around a few recommendation sites[1], but am curious to know if anyone has suggestions for new and/or under-the-radar services they would recommend?
[0] https://blog.google/products/photos/storage-changes/
[1] https://www.techradar.com/how-to/best-google-photos-alternat...
316 comments
[ 3.1 ms ] story [ 176 ms ] threadI think the Synology NAS do the same.
https://www.theregister.com/2021/04/22/qnap_nas_ransomware_q...
There's also an active forum for both support and to discuss what and how new features are built out.
https://photostructure.com/
Disclaimer: I'm the (only) author.
It's also why I implemented bitrot detection and metadata inference. A beta tester just called the date parsing heuristics "freaking awesome and so close to black magic…" :)
https://forum.photostructure.com/t/combining-images/524/7
(And if you prefer the command line, know you can do tons of things via the CLI: https://photostructure.com/server/tools/ )
I tried a few things with ImageMagick, but ran into problems. I'll have to try your app!
https://photostructure.com/getting-started/automatic-library...
- [1] <https://www.youtube.com/results?search_query=%22photostructu...>
I know you previously responded that people should upvote that feature, but the inability to distinguish video from photo just seems like a must have fix over other potentially over engineered stuff that others are asking for.
Yes: out of an abundance of caution, the unique (by SHA) variations of each asset are copied into your library. There are heuristics that pick which is the "best," and although those heuristics seem to be robust for most beta users, I didn't want to be the source of want data loss.
> datestamp info in the filename?
The metadata in the file is trusted more than any date extracted either from the filename or the directory hierarchy. Details are here: https://photostructure.com/faq/captured-at/
If you use the info tool, it'll tell you how it's extracting the date from any given file: https://photostructure.com/server/tools/#file-information
> slow to sync
PhotoStructure scales imports to accommodate current hardware, in Ann effort to keep the system responsive. Parallelism is limited by available RAM and CPU count. If you think it was being too conservative, please send me a screen shot of your about page (it includes both system metrics and what is thinking for scheduling limits), and if you want, debug logs, and we can look into what's going on. https://photostructure.com/faq/error-reports/#how-to-manuall...
> no map view
This is a popular feature request that I'm looking forward to building: https://forum.photostructure.com/t/support-reverse-geocoding...
https://photostructure.com/server/photostructure-for-servers...
[0] https://github.com/LibrePhotos/librephotos
(Or, for optimal performance, the hybrid solution: put the library in a sparsebundle disk image, put that on the NAS, and then mount the disk image over SMB. This is what Time Machine does under the covers, because it vastly improves the overhead of filesystem operations over directly manipulating the files in SMB.)
(It's also frustrating that the VoiceOver image recognition is far superior to Photos', but is inaccessible to the Photos app.)
If the reason is because they want a free tier forever, that impacts the recommendation. If the reason is because they think google could shut you out, that may need a completely different recommendation.
So while at it move away from one more Google service.
Also haven't they said on both the big changes anything in the past will be held as legacy under free and future uploads will go to storage? I think you have to accept business needs to adapt models sometimes and Google Photos is more this than bait and switch.
Fair call on the lockout. This is a real issue for Google.
I run one on my wife's account with a cron job to grab new photos daily.
Yes, you pay real money for the stupid cloud model, but — I can add gradient and circular filters, correct for the lens distortion with profiles for most major cameras and lenses (including your iPhone), get one-click perspective correction so a building facade is square against the image plane ... and it's all lossless editing.
You want a map of your photos over time? Of course we have the map. You want facial recognition but locally hosted so it's not creepy? Got ya covered.
There's a cloud-oriented Lightroom these days. I don't use it and don't look forward to when they stop supporting Classic so I'll have to ... switch away yes that's definitely what I'll do 100%
But the problem is Adobe Lightroom CC has effectively zero penetration with professional photographers. If I had to summarize the pro market opinion of CC, it would be contempt. Here's an example: This article (https://petapixel.com/2020/01/02///why-im-sticking-with-ligh...), about choosing Classic over CC, has about 100 comments, the maximum allowed, most panning CC. Of those 100, it's easy to find the single positive comment about CC: it's at the bottom, with the most downvotes.
The problem is the whole basis of CC (cloud storage) is antithetical to how professional photographers work (thousands of large photos per shoot). Adobe can't grow CC into eventually supporting this market because it can't support offline storage, because the whole reason CC exists is to have a product that's cloud only...
So I think Adobe will effectively be supporting Classic forever. Here's an example: Adobe has committed to native support for Classic on Apple Silicon (https://helpx.adobe.com/lightroom-classic/kb/macos-big-sur-c...).
Pros who need Photoshop will still need Adobe. There is nothing remotely close to replacing Photoshop. And AFAIK, every Lightroom competitor ships with an “open this file in Photoshop” button.
Apple did this with Final Cut. After years of being proud that Real Hollywood Films were edited with Final Cut, they gave up Hollywood and pivoted the product firmly toward prosumers. It has not hurt Apple at all, and probably saved them some money and heartache along the way.
This is theoretically possible, but I'd bet against it because of the brand halo effect of having Lightroom Classic be the main tool of professional photographers is too valuable. The second Adobe discontinues Lightroom Classic, the professional market will move to Capture One. That's a dangerous position for Adobe to be in. I wouldn't put it past Adobe to still make this mistake (e.g., see Figma), but I think if they did, it would be a mistake so large that it would shape the future of Adobe as a company. I.e., Adobe will be weaker forever if they do this.
> Apple did this with Final Cut. After years of being proud that Real Hollywood Films were edited with Final Cut, they gave up Hollywood and pivoted the product firmly toward prosumers. It has not hurt Apple at all, and probably saved them some money and heartache along the way.
I do not think Apple is happy about the way Final Cut Pro X turned out. The feedback to Final Cut Pro X was so bad that Steve Jobs personally called Randy Ubillos about it (source https://www.youtube.com/watch?v=bfII0EcbCsg). That's the only time I've ever heard of Steve Jobs getting involved with one of Apple's pro apps.
Consider this: Look at the Mac Pro and in particular, the Pro Display XDR. Which industry were those products made to placate? Do you think Apple is happy that video studios that once would have been running their software on those machines are now running Avid/Premiere? Plus look at the corresponding roll out of Logic Pro X two years later, which was far less of re-imagining than Final Cut Pro X was. I think Apple has learned their lesson. "Success hides problems", from 2010-2020 made some colossally terrible decisions, that we only talk about less because the iPhone has compensated for so much, Final Cut Pro X is one of them.
[0] https://www.synology.com
Also, the OP doesn't need to get rid of Google Photos. They can keep Google Photos as a off-site back-up.
I third this recommendation.
I use the pointy clicky AWS Glacier backups app in case everything goes sideways.
It has the flavor of Google Photos, but it's definitely a step down in UX. One of the features I really love about Google Photos is the ability to jump quickly through time. Like if I'm looking for a photo I took around June 2018, I can get to it in <5 seconds.
I didn't realize what a magical feature it is until I tried looking for it with alternatives and found that they all have a lot of scrolling, pausing to load new photos, more scrolling.
But I'm impressed with what Photoprism has achieved as a small, donation-funded OSS project, so I'm hoping to see them grow.
[0] https://photoprism.app
Not only that, you can search for a photo of a light bulb you know you took, but don't know when, but simply typing "light bulb".
If I had such a need and privacy was not an issue I would use Dropbox (I already use Dropbox a lot, easy to share, excellent download speeds, and I don't have a huge photo library).
No matter what you do, stay away from iCloud. By God, they have made it so bad that it feels like a criminal offence.
I tell you what I was trying to do just now. Literally minutes ago.
I have photos in "Library" (i.e. the first screen that loads) and I didn't want that. I wanted them in different albums and just stay there. So I added them to different albums. There's no way to "move". They will still show there.
Now you can hide them from "Library" and they will vanish from the Library. Awesome, right? Nope! They vanished from those other albums you had added them into as well. Now those photos are in a special library called "Hidden". Yes, all those photos!
Okay fine. Now you want them back in those albums. So you go to Hidden and select some photos to be added into an album. Everything happens fine it just that the photos still don't show anywhere but only in Hidden. So I guess you will have to first unhide those photos and get them all in Library and then add them all to albums.
And all I wanted was to keep the photos that processed (i.e. moved to diff albums) and the ones not processed separately.
Now I don't even want to start on how my friends exclaim "What kind of service is this? Which company? God such a pathetic download speed!". Those friends are from all over the globe.
I ended up building my own, which has the advantages it's designed specifically for my needs (but which obviously means it's less likely to be useful for other people with different requirements or workflows).
My two main criteria were: supporting galleries of non-square images (very few solutions support this, they just crop to squares which makes things much easier for layout, but I don't like), and having portable catalogs with the metadata (mine are basically YAML defined metadata per photo, like geo location hierarchies (Europe / France / Paris), tags, categories, such that I am not locked to a DB, and can move the catalogs (and images) around on arbitrary drives / volumes, and can transfer them.
The large downside (although I'm willing to put up with it), is having to fairly manually curate each photo item, but a lot of "tourist photo" style stuff is quite similar for me, so I can share multiple metadata for multiple photos, so it's not too bad.
We have shipped open-source[2] web and mobile apps that have preserved 180,000+ files. Apart from cross-device sync, you can share your albums end-to-end encrypted, and filter photos by location and time.
We recently had a "successful" launch on r/degoogle[3]. We wanted to Show HN after incorporating the feedback we received from there, but since OP asked, I thought I’ll drop a comment here.
If you’ve any questions, please ask.
[1]: https://ente.io
[2]: https://github.com/ente-io
[3]: https://www.reddit.com/r/degoogle/comments/njatok/we_built_a...
Wish you all the best!
As for personnel costs, a few more hundred paying users and we'll be set. Feedback from existing users have been positive, and we should be able to reach that point by end of the year.
It helps that we're living in one of the cheaper parts of the globe, and are not motivated by money. We're building this because an easy to use, privacy friendly alternative needs to exist.
Ummm, could you elaborate on this? It sounds great but it's at the same time so foreign to me...
"not motivated by money" sounds very much like "we'll be shutting down in 2 years"
Our pricing plans are designed such that you cover your own storage + bandwidth costs, and then some more. We don’t have a "forever-free" plan, and don’t intend to have one.
And the compute requirements for a product like this are low (since most of the computation happens on the client).
So currently what we need money for is employees (engineers) and not infrastructure.
Tagging faces and objects is on our roadmap, we will ship it.
[1]: https://web.ente.io
Also the phrase "ente has an open architecture and source code that has been peer reviewed" that can be found on their website follows a dark pattern: hey, look we are open but not really.
Also, self-hosted consumer products are hard to sustain profitably. Avenues for monetization are low.
Given that our long term target audience is people like my parents, we did not see enough value in investing in a self-hosted variant, and wanted to reduce the number of distractions.
This is not to say that we are against the idea of a self-hosted variant, just that it is not a priority for us right now.
We had started off as a self-hosted project, but ran into difficulties monetizing that model. We wanted to pay our rents, and continue working on this, and an E2EE SaaS was a way forward.
We are not averse to supporting a self-hosted version in the future. But that commitment requires engineering and support bandwidth, which we don’t have right now.
In my opinion open source software benefits greatly from first being closed sourced and commercially backed with an OSS release coming in the future after stability has been established.
What about latency concerns for people who are not based in EU? I saw on that website that the servers are hosted in EU, and say I need to use it in Asia will have service have usable latency?
If you find observable latency within the service, please write to vishnu[at]ente.io. I will see what we can do.
> We've already preserved 100,000+ files, and are quite reliable at this point.
"quite reliable" doesn't cut it for a paid service for me, even a new one.
My second issue, and I might be wrong about this, is that there's no way to share photos with someone who isn't a (paying) ente user.
As an engineer, I shy away from using superlatives. But sorry, I now understand that this could have been phrased better. Thank you for pointing it out.
> no way to share photos
Correction, the receiver can be on the free plan.
But I think you need user logged in because of encryption.
We could generate public URLs that contain the decryption key of the album within the URL fragment. But as an encrypted storage provider, we would like to ship this only after we're reasonably confident that there are checks in place to prevent abuse.
For example: albums.ente.io/{albumID}/!#{decryptionKey}
Now on the receivers side, the client can use this `decryptionKey` to decrypt and render the photos.
It's fine in a spoken context as tone can add sufficient extra meaning. If you can guarantee the listener is expecting an informal register then it probably also comes across as a superlative. "I met him and he's quite unpleasant" would usually imply he was a total c*nt.
Personally, I'd never trust the only copy of something important to a service provider--especially one that isn't a "big name." (Though even in the case of big names there can be issues with account access, etc.)
ADDED: Curious why people find this a controversial statement. I understand if you have AWS set up with various redundancies but even a service like Backblaze I consider a belt and suspenders-type backup. This is in no way a commentary on the OP but simply an acknowledgement that stuff happens.
Our current setup includes primary backups to BackBlaze[1], and eventually consistent replications to Scaleway's cold storage[2].
We would like to offer an extra replica as an addon in the future.
[1]: https://www.backblaze.com
[2]: https://www.scaleway.com/en/c14-cold-storage
I know a lot of people these days are fine with their stuff mostly just being stored in "the cloud" someplace. But for things like photos, I really want a couple copies under my control to the degree possible.
Do you have an public API? I'd love to have a tiny sync client to fetch photos and store them on my laptop.
If your current use case is only to sync your uploaded files to a local folder, we have an Electron app that does just that: https://github.com/ente-io/bhari-frame/releases/tag/v1.0.3
An electron app seems like a huge overkill for something so simple (have you considered just a simple cli instead?).
The Electron app is indeed an over kill (hence the repo-name "bhari", meaning overweight). But it made it easy for us to reuse stable code that performed authentication, decryption, data-sync, etc. Also, we did not want to commit to the overhead of maintaining another stack (say a CLI or a native app) at a point where the value it would provide to a customer was unclear.
Feedback: You can improve your website looks.
Goodluck
Regarding the website, I would be grateful if you could point out the worst part(s). I would love to improve.
If it’s degooglers then perhaps convincing us it has everything Google Photos had is job number 1. If it’s missing feature X then you’ve got a reason to say no, if it’s at parity then it comes down to whether we trust YOU and is the deal good enough.
You’ve already convinced us you’re not Google so there is some things implied but you need to lean into it. Privacy, not having you information used for ad targeting, never sharing our photos or information derived with third parties - those are all thing to highlight (be the anti-Google).
I think you need some other killer feature or appeal that makes you different than iCloud here since Apple are already the anti-Google. I think you can also get 2TB of iCloud Photo storage for $10 a month so you gotta hit that if you want to charge $15 for 500GB.
Is that the total number of files on your platform? Not to be rude, but is this supposed to be impressive or reassuring? My photo collection is approaching half that number, and I'm just one person, so now I'm feeling completely underwhelmed by the claim.
But you're right, the number is minuscule compared to where we are hoping to be. We're just getting started and I'm hopeful that we will 10x this number in the next few months.
https://nextcloud.com/
I've been using for a couple months and been extremely happy with it.
I'm using DO's Spaces (S3) as file storage. I also suspect very strongly that it is the main source of the slowness of the nextcloud (but it is super cheap!).
The main pain in the ass is having to update every year or so. It usually works flawlessly, until it doesn't and I have to run a few manual commands. Other than that, it just works. 100% recommend it.
Mine is a personal instance, being used by 5 people (family). I've had the nextcloud and its postgres database running in a 5$ instance for years, no problem (I did add a bit of swap for the DB).
I should warn users that such instance may struggle to run even bare minimum nextcloud.
2-4GB is preferred.
On the other hand, mine is running at 400MB right now.
I guess it also depends on the frequency and how it is used. We mostly use the apps on the phone and file app integrations (Ubuntu lets you access the files from the Files app).
It is true that it is somewhat slow when loading the website.
Chris MacAskill founded it with his son. Pretty solid company, seems like.
https://mixergy.com/interviews/smugmug-chris-macaskill-inter...
I have a DIY NAS, based on a Raspberry Pi and an external hard disk enclosure, running in my kitchen. The disks are encrypted with LUKS. A combination of Syncthing and a cron job ensure that photos from my phone are constantly synced to the NAS without any input from me, and old photos are removed from my phone. A nice bonus is that if someone were to search my phone, they would not find many photos on it. I also never run out of space for photos/videos on my phone.
To view photos I use Shotwell. It does a decent if not perfect job of tagging, basic editing etc.
For encrypted, deduplicated offsite backups I use rsync.net and Borg, again together with a cron job.
All this crap is configured with Ansible in an effort to make it a little less fragile and more reproducible. It has been running without maintenance for a year or so but if you take this path, expect to spend many, many hours tearing your hair out over SAMBA Unix permissions and all sorts of other delights...
https://photoprism.app/
[1] https://help.nextcloud.com/t/search-images-for-content-of-im...
[2] https://apps.nextcloud.com/apps/ocr
I personally use iCloud, and back everything to a Synology.
As always, we don’t sell your information to anyone, and we don’t use information in apps where you primarily store personal content—such as Gmail, Drive, Calendar and Photos—for advertising purposes, period.
https://blog.google/technology/safety-security/keeping-priva...
As always with privacy policies, the information is in what is NOT said.
1. They don't sell to anyone. But what giving away for free?
2. They don't use personal content for advertising purposes. But what about other purposes than advertising? For example applying face or location recognition in photos to establish a profile that is used in a fraud detection service in Google Pay?
2 seems more plausible.
However they probably do sell information/meta data they themselves have mined from my data, which they probably claim is harmless and de-personalized.
They got something in return - as they do with all their partners - but this is not generally considered a sale, and often not even a trade.
The distinction is that 3rd parties only have access to Google UIs or APIs based around ad targeting selectors. There is no API for 3rd parties to just download raw user data from Google.
This is in contrast to Facebook, which used to allow “apps” on their platform to suck down raw user profile data in large quantities.
It seems very likely that Google is using their user data for non-ad purposes, for example using Google Photos data to train ML image recognition engines, or using Gmail data to train conversational AI systems.
The main failure mode I'm concerned about is if Google decides I'm no longer worthy of an account. In that case I'll still have my pics and I'll put in the effort to set up some other service.
With an iPhone it doesn't seem that there is a way to sync with a folder anymore.
My cameras are all Androids, so I use FolderSync to put things in the cloud. It being Android there's still a filesystem that it can scan. I use an app on my QNAP to bring them back home.
Some of the tools recommended are:
https://syncthing.net/
https://www.resilio.com/
https://www.photosync-app.com/home.html
[0] : https://github.com/icloud-photos-downloader/icloud_photos_do...