Connect a dedicated Telegram account
Sign in directly to Telegram inside Ambry using Telegram’s official TDLib client. A separate, dedicated Telegram account is recommended so your photo archive stays isolated from personal chats.
Back up your photos and videos with Ambry. A private photo library powered by Telegram storage, processed and managed right from your Android phone — with no Ambry storage server in between.
3 years ago
On this day
▶ 0:30
Why It Matters
It holds the evening your family stayed late around the table, the morning light from a trip you will never repeat, the ordinary Tuesday you didn’t realize would become a favorite memory five years later.
Phones get dropped, replaced, or run out of space. Yet backing up a decade of life usually leaves you with an uncomfortable choice: hand your library to a hosted photo company forever, or run and maintain a home server yourself.
Ambry — an old word for a recessed cabinet built into a wall to keep precious things — offers a quieter middle path.
Meet Ambry
Built by adapting Immich’s Flutter mobile app and pairing it with Telegram’s official TDLib client library, Ambry moves photo-library processing onto your Android phone and stores your backed-up media inside private channels in your own Telegram account.
2 years ago
Autumn trip

▶ 1:12



Summer Coast
148 items
Family 2026
234 items
Table & Friends
64 items
Mountain Weekends
91 items
Representative preview of Ambry v1.0.0 for Android (Sunlit Alcove interface).
How It Works
Ambry does not operate its own storage backend. Your phone handles the library work locally, while Telegram provides the underlying storage infrastructure.
Sign in directly to Telegram inside Ambry using Telegram’s official TDLib client. A separate, dedicated Telegram account is recommended so your photo archive stays isolated from personal chats.
Create your vault passphrase, record your 24-word recovery kit, and pick which Android albums to back up. Client-side encryption is on by default, and you can change it for new uploads anytime.
Your Android phone computes SHA-1 deduplication hashes, reads EXIF and GPS metadata, generates encrypted local thumbnails and previews, and updates your local SQLite library index.
Ambry uploads each file to a private Library channel owned by your account and periodically saves encrypted index snapshots to a private System channel for recovery.
Important distinction: Ambry operates no servers of its own, so the developer never receives or stores your media. Telegram still provides the underlying cloud infrastructure that hosts your private channels.
Privacy & Encryption
Telegram private channels use client-server encryption, not end-to-end encryption. That is why Ambry encrypts your files on your Android phone before upload by default — while still letting you choose plain uploads if you prefer to open new items directly inside Telegram.
Each photo or video gets its own unique AES-256-GCM key and is encrypted in 1 MiB segments before upload. Telegram stores opaque binary documents, so neither Telegram nor anyone opening your channel can view the images without your vault passphrase or 24-word recovery kit.
If you switch off “Encrypt before upload” on the Backup screen, new uploads are stored as regular files inside your private channel. You can open them in Telegram directly — which also means anyone with access to your Telegram account, and Telegram itself, can view those unencrypted files.
The Gallery Experience
Ambry feels like a calm, dedicated photo gallery first — not a file manager or a messaging app. Everything shown below is built and verified in Ambry’s Android app today.
01 · Viewing & Streaming
Because Ambry encrypts files in 1 MiB segments and serves them through an
on-device loopback media server (127.0.0.1), you can open full-size
photos, stream and seek videos directly from Telegram, or download byte-identical
originals back to DCIM/Ambry/ — even after using
Free up space to remove older local copies from your phone.
Representative photo viewer & details sheet in Ambry.
02 · Organization & Private Search
Organize your archive into albums, star favorites, archive clutter, and explore GPS-tagged photos on a map powered by OpenFreeMap. Search runs locally against your on-device index by filename, description, camera make and model, date range, and media type — plus locally computed “On this day” memories.
Browse local folders & pick backup sources
Computed locally from dates & photo GPS
Note: Face grouping (People), reverse-geocoded city names, and AI/CLIP search are not part of v1.
Recovery & Continuity
Ambry backs up an encrypted snapshot of your library index to your private System channel daily (and on demand) so a new Android phone can reconstruct your timeline and albums from Telegram alone.
Encrypted SQLite snapshots (newest 3 kept) and a pinned vault record live in your private System channel alongside media captions in your Library channel.
Sign in to the same dedicated Telegram account on your new phone. Ambry locates the pinned System record automatically.
Enter your vault passphrase or 24-word recovery kit. Ambry decrypts the newest index snapshot and reconciles any newer messages from channel history.
Your timeline, albums, favorites, and metadata return. Thumbnails and originals are fetched from Telegram on demand as you browse.
Honest Comparison
Every backup model involves real trade-offs between convenience, control, cost, and durability. Choose the model that matches your risk tolerance.
| Dimension | Ambry (Android) | Hosted Cloud Photo Backup | Self-Hosted Photo Backup |
|---|---|---|---|
| Infrastructure model | No Ambry-operated storage server; Android app talks directly to Telegram via TDLib. | Provider-managed cloud servers, web apps, and multi-device sync infrastructure. | You run a server (NAS, mini-PC, or VPS) with storage drives, backups, and networking. |
| Storage backend | Private channels in your own dedicated Telegram account (subject to Telegram’s ToS & limits). | Commercial cloud object storage with paid tiers and formal service availability commitments. | Your own local hard drives, RAID/ZFS pools, or cloud storage buckets you pay for. |
| Local processing | Hashing, EXIF/GPS parsing, thumbnails, albums, memories, and metadata search run on Android. | Often processed in the cloud (or on-device in privacy-focused services like Ente). | Processed by your home server (enables heavy ML like face clusters and CLIP search). |
| Encryption options | Optional client-side AES-256-GCM encryption, enabled by default; toggleable for new uploads. | Varies: standard server-managed encryption on mainstream services, or client-side E2EE on privacy providers. | Full disk encryption on your hardware; HTTPS in transit; depends on your server setup. |
| Server administration | None — install the Android app and sign in to your dedicated Telegram account. | None — managed entirely by the provider. | Ongoing OS updates, Docker/app upgrades, TLS certificates, drive health, and offsite backups. |
| Recovery & durability | You hold the Telegram account + passphrase / 24-word recovery kit. No storage SLA from Telegram. | Account recovery flows and professionally replicated storage backed by the provider. | Your responsibility to maintain hardware redundancy and off-site copies (e.g., 3-2-1 backup). |
Telegram is a messaging platform, not a professional archival storage provider with a durability SLA. For irreplaceable family photos, consider keeping an additional offline or secondary backup copy alongside Ambry.
Technical Transparency
Explore the verified implementation details directly from Ambry’s architecture and engineering logs.
Telegram’s cloud Bot API caps downloads at 20 MB, cannot create channels, cannot list channel history for recovery, and prohibits using bots for external cloud storage sites.
Ambry embeds Telegram’s official TDLib 1.8.65 client
library via a native Kotlin/JNI bridge, authenticating with your dedicated
Telegram account. This supports single files up to 1.95 GiB, ranged
downloads for video streaming, channel creation, message deletion, and
history scanning for vault recovery.
Ambry reuses Immich’s Flutter UI and Rust native_core
image codecs alongside a local SQLite index (keepsake-index.db)
projected into Drift tables.
Your phone runs native SHA-1 hashing for deduplication, MediaStore & EXIF
reading, thumbnail (320 px) and preview (1440 px) generation, local
metadata search, and a loopback-only HTTP media server
(127.0.0.1 guarded by a random per-install path token) to
decrypt thumbnails, originals, and HTTP Range video streams on the fly.
Library channel: one document message per backed-up photo or
video (sent with disable_content_type_detection when encrypted),
accompanied by an encrypted IMTG2 recovery caption containing
the wrapped per-file key and essential metadata so the library can be rebuilt
even if snapshots are missing.
System channel: a pinned KSVAULT1 vault
discovery record (containing only passphrase- and recovery-wrapped vault key
blobs), encrypted KSIDX1 SQLite index snapshots (newest 3 kept),
and a sealed active-device record enforcing one writer phone per vault.
At setup, Ambry generates a random 256-bit vault key wrapped twice: once with
Argon2id (64 MiB, t=3, p=2) from your passphrase, and once
with HKDF-SHA256 from your 24-word recovery kit (192 bits).
Either secret unlocks the same vault key.
When encryption is enabled (default), each asset receives a fresh random
key and is encrypted in 1 MiB AES-256-GCM segments
(IMTG v1 format with header + segment index authenticated via
AAD), allowing random-access video seeking without downloading the whole
file.
File size limit: Single files larger than 1.95 GiB are currently refused (multi-part splitting is not implemented in v1).
Background battery policies: Phones running aggressive background killers (such as Realme/Oppo ColorOS, Xiaomi, or Vivo) may pause closed-app background backups until you allow background activity / “Unrestricted” battery for Ambry. The Backup screen alerts you when this setting is off.
Account or channel loss: If your Telegram account is banned, deleted, or inaccessible, or if you manually delete messages/channels inside Telegram, Ambry cannot retrieve those files from Telegram. Deleting an item permanently inside Ambry’s Trash also deletes the corresponding Telegram message.
Questions & Answers
Everything you should know before trusting Ambry with your Android photo library.
Ambry is an open-source Android photo and video backup app (GNU AGPL v3) adapted from Immich’s mobile application. It lets you browse, organize, and back up your library directly into private channels owned by your own Telegram account, without running a separate storage server.
Ambry embeds Telegram’s official TDLib client library so your phone connects directly to Telegram. After sign-in, Ambry creates two private channels owned by your account: a Library channel for your photos and videos, and a System channel for encrypted index backups. Ambry is an independent project and is not affiliated with Telegram.
We strongly recommend using a dedicated Telegram account rather than your personal messaging account. High-volume media backups can occasionally trigger Telegram rate limits or automated account checks, and a dedicated account keeps your daily chats completely separate.
Yes — client-side encryption is enabled by default. Before a photo or video leaves your phone, Ambry encrypts it using AES-256-GCM with a unique per-file key wrapped by your vault key.
Yes. You can turn off Encrypt before upload on the Backup screen (after a confirmation prompt). New uploads are then stored as ordinary files that you can open directly inside Telegram. Anyone with access to that Telegram account — and Telegram itself — can view unencrypted files. Previously encrypted items and your library index remain encrypted.
Ambry does not operate its own storage backend or developer servers. Your backed-up photos, videos, and index snapshots are stored on Telegram’s infrastructure inside private channels owned by your Telegram account.
Yes. Install Ambry on your new Android phone, sign in to the same Telegram account, and unlock your vault with your passphrase or 24-word recovery kit. Ambry downloads the latest encrypted index snapshot from your System channel, reconciles any newer items from your Library channel, and restores your timeline and albums. Recovery requires both your Telegram account and your encryption key.
If you permanently lose access to your Telegram account or the account is suspended or deleted, you will lose access to the media stored in its channels. Copies still stored locally on your phone are unaffected, so avoid relying on any single storage platform as your only copy of irreplaceable files.
You can still unlock your vault using your 24-word recovery kit generated during setup. If you lose both your passphrase and your 24 recovery words, encrypted backups cannot be decrypted — there is no Ambry server or password-reset mechanism.
No. Ambry is currently an Android-only application (Android 8.0 / API 26 and newer). There is no iOS app, desktop app, or web viewer.
Ambry v1.0.0 is currently preparing for Google Play closed testing and is not yet publicly listed on the Play Store. You can inspect the complete AGPL v3 source code, architecture documentation, and release progress on GitHub.
Keep your Android photo library organized and backed up in your own private Telegram channels — built in the open under GNU AGPL v3.