Move your data to Ente (end-to-end encrypted)
Once you have your data out of the big services and cleaned up, it needs to live somewhere you control. This guide covers moving your archive to Ente (end-to-end encrypted).
Step by step
-
Decide if the trade suits you
Ente is a hosted service you pay for, like iCloud or Google Photos, with the difference that it cannot read what you store. You get the phone app, sharing and search; you give up the ability to recover anything if you lose your recovery key, because nobody at Ente can reset it for you. It is also open source and can be self-hosted if you would rather run it yourself.
-
Install the desktop app
Get the desktop app rather than using the browser. It is the supported route for importing from a local disk, it handles large sets, and it is what does the encryption. The CLI is worth knowing about but is built for exporting your library back out, not for bulk import.
-
Write down the recovery key
Do this before uploading anything. End-to-end encryption means the key is the only way in - lose it and the photographs are unrecoverable by anyone, including Ente. Store it somewhere that survives the loss of your computer: a password manager, or paper somewhere safe.
-
Import the folder Muletto wrote
In the desktop app choose to add files from a folder and point it at your organised library. Ente reads the date and location out of each file, so the timeline lands correctly - which is exactly what repairing metadata first is for. The folder structure can become albums, so the year and month folders keep meaning something.
-
Let it finish, and watch the storage
Encrypting and uploading a large library is slower than a plain copy, because your machine is doing cryptography on every file. Leave it running on power. Keep an eye on your plan's storage as it goes, since a full repaired library is usually about the size of the archive you downloaded.
-
Keep a copy that does not depend on them
Encrypted and hosted is still hosted. Ente makes leaving easy - the CLI exists specifically so you can take continuous exports with no dependency on them - so set that up, or keep the folder Muletto wrote on a drive of your own.