Telegram-powered personal cloud storage

Your files, encrypted before they ever leave your hands.

hamro turns Telegram into the storage layer for your personal cloud. Every file is sealed with AES-256-GCM in your browser — Telegram and our server only ever see ciphertext.

AES-256-GCM
E2E encrypted
Telegram-powered
Open source

Not “unlimited free storage.” Telegram-powered, with real limits — see our honesty page.

vacation-photo.jpg AES-256-GCM
🖼️
Plaintext
on your device
encrypt
8f3a…c19e
e02b…77af
d941…0bc3
Telegram
🔑 Key derived with PBKDF2 · AES-KW wrapped per-file · never transmitted
E2EAES-256PBKDF2
Live encryption
Everything you need

Built like a real cloud drive — secured like a vault.

Every core file-manager feature you expect, with encryption as the default — not an afterthought.

End-to-end encryption

AES-256-GCM per file, key wrapped with a password-derived key. Telegram never sees plaintext or unwrapped keys.

Explorer you already know

Windows-Explorer-style dashboard: Home, Photos, Videos, Audio, Documents, Shared, Favorites, Trash.

Chunked, resumable uploads

Large files are encrypted and split client-side, uploaded in chunks, and can resume after a dropped connection.

Time-boxed sharing

Share links expire in 1 hour, 1 day, or 7 days — with optional password, download counter, and one-click revoke.

Fast search & preview

Preview images, video, audio, PDFs, text, Markdown, code, and ZIP contents — all decrypted locally before rendering.

Installable PWA

Install hamro to your home screen, with an offline app shell and background sync workers for uploads.

Zero-knowledge architecture

How the encryption pipeline works

No plaintext file ever touches our server or Telegram's servers.

01

Log in with Telegram

Enter your phone number, confirm the OTP, and add an optional 2FA password — just like Telegram's own login.

02

Encrypt in your browser

Dropping a file generates a random per-file AES-256 key, wraps it with a key derived from your passphrase, and encrypts the bytes locally.

03

Ciphertext goes to Telegram

Encrypted chunks are relayed through our thin backend into your Telegram storage. Metadata (names, folders) lives in our DB — never file contents.

04

Decrypt only on your device

Downloads and previews are decrypted locally with Web Crypto. The server relays bytes; it can't read them.

Frequently asked questions

Honest answers about what hamro can and can't do.