You definitely can if you put Immich behind a reverse proxy like Caddy and open it up to the rest of the world. I also protect my instance against bots with Crowdsec. That's how share albums with family and friends.
Selfhosted
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil.
-
No spam.
-
Posts are to be related to self-hosting.
-
Don't duplicate the full text of your blog or readme if you're providing a link.
-
Submission headline should match the article title.
-
No trolling.
-
Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
There is also this: https://github.com/alangrainger/immich-public-proxy
I think your immich gallery can even be private ( though the public proxy would need to be able access it ).
I have no experience with it though.
Why would you think you can't share albums? You definitely can.
only if immich is publicly accessible (reverse proxy to domain, etc.). If it's on a closed network like tailscale, albums aren't accessible from outside the network afaik
You can share Immich albums.
If you plan to make a diy solution, you might've seen one or two CLIs for uploading to Google Photos. Just FYI, you can also leverage rclone to create Google Photos albums and uploads photos/videos there.

Isn't this 'sharing an album'?
It is but it requires public internet access to the Immich instance, or everyone involved being on our VPN. Reusing someone else's publicly facing service to share photos from a private Immich instance is a clever workaround.
Using a reverse proxy / ingress, you can configure only share links to be publicly available, while keeping the rest of immich exclusive to your private-network. Optionally combine with something like Cloudflare Tunnel if you're worried about leaking your server's IP.
Afaik immich is generally safe to publicly expose. Otherwise, I'd just use http basic auth. Supported by every server and client, should be secure enough to hold off attacks in case immich's login/auth mechanisms fail, and I don't see a usecase where this wouldn't work.
If you don't have a public IP or need IPv4, get a 4€/Month VPS (cheaper than even a Pi's energy usage I suppose) and put headscale on it.
Coud probably be done. Find publicly shared Immich albums -> sync to Google Photos -> share publicly -> write the public Google Photos URL to the metadata of the Immich album.
Another could be an insulated public facing Immich instance that gets publicly shared albums pushed to it, the same way as with the other scheme. No reverse access to the private Immich instance. Then if that gets hacked, only those photos leak, attacker can't get their hands on other server data. Assuming it's really well isolated. A public VPS would probably be best for this.
IMHO you should look/ask for such a feature in a google group because big g may have a business case for such a feature: it would pull back in those users who try to escape.
and that should not be an immich feature but a google one.
as a self-hoster I prefer to have control on my data; a solution to feed my data to google through a third party (that may do whatever it wants while performing the transfer) is the exact opposite of what i'm trying to achieve and would have little to no value for me.