TeleDrive is a free, open source file management & sync project written in Kotlin and released under Apache-2.0. It has 511 GitHub stars, 65 forks and 18 open issues, and was last pushed 32 hours ago. On this registry it ranks #84 of 86 tracked projects in File Management & Sync, with 5 head-to-head comparisons available.

What is TeleDrive?

TeleDrive is an Apache-2.0 Kotlin application for individuals who want a personal cloud drive on Android, Windows, Linux x86_64 and macOS Apple Silicon, built by turning a private Telegram channel on their own account into storage, with no TeleDrive server or separate account to create.

What it is

TeleDrive is a file manager and backup client in the Telegram ecosystem, implemented in Kotlin with Compose Multiplatform and TDLib. One codebase ships the Android app and the Windows, Linux x86_64 and macOS desktop apps; they share the storage engine, encryption, transfers and the entire UI layer, and all of them browse the same drive. The app keeps a local index so browsing and search stay fast and work offline.

The concrete problem is storing and managing files without setting up a hosted cloud drive. TeleDrive stores files in a private Telegram channel on the user's own account, so there is no TeleDrive server and no account to create with the project. It replaces a conventional hosted cloud drive with the user's Telegram channel while adding a built-in file manager and player: folders, favorites, hidden and archived items, trash, bulk actions, inline previews and streaming. It also removes Telegram's message-size limits from the user's point of view: a 20 GB video is one file in the app, whatever Telegram caps a message at.

Key capabilities

  • Automatic backup on Android: photos and chosen folders upload on their own, with schedules, Wi-Fi and charging rules, and exclusion patterns.
  • Optional AES-256-GCM encryption covering file bodies, names, captions and the folder tree.
  • File management with folders, favorites, hidden and archived items, trash and bulk actions.
  • Streaming playback of video and audio straight from Telegram with seeking, encrypted files included, plus inline previews for images, PDFs, text and ZIP contents.
  • Multiple drives as separate channels for personal, work or photos on one account, and an Android share sheet intake that never uploads identical bytes twice.
  • A transfer queue with parallel transfers, pause and resume that survives reboots; recovery by reinstalling, signing in and entering the passphrase.
  • Device security through biometric app lock, screenshot blocking and an encrypted local cache.

Who uses it and how

  • Individuals replacing a hosted cloud drive with a private Telegram channel on their own account, with no server to deploy and no TeleDrive account to create.
  • Android users automating photo and folder backup with schedules, Wi-Fi and charging rules and exclusion patterns.
  • People who separate contexts with multiple drives—personal, work or photos—using separate Telegram channels on one account.
  • Cross-platform users who browse the same drive from Android, Windows, Linux x86_64 and macOS Apple Silicon, since the clients share the storage engine and UI.
  • Large-file and recovery workflows: a 20 GB video remains one file despite Telegram message caps, and a reinstall is recovered by signing in and entering the passphrase.

Getting started

Install from the GitHub releases page: Windows uses a per-user TeleDrive-*.msi that installs without an admin prompt, with separate Linux x86_64 and macOS Apple Silicon downloads and an Android app. There is no server to deploy; sign in to Telegram and use a private channel as the drive.

How it compares

The facts name no comparable file-management or sync tools, so TeleDrive stands alone in this registry. Its distinction is architectural: storage lives in a private Telegram channel on the user's own account, with no TeleDrive server or account to create, rather than in a separate hosted service.

When to use it — and when not

Use TeleDrive when a private Telegram channel is an acceptable storage backend and the priority is a cross-platform file manager, automatic Android backup and optional encryption without running a server. There is no database, object store or SMTP service to operate, but the user must maintain the Telegram account and channel and keep the passphrase for encrypted drives. It is a poor fit for anyone unwilling to depend on Telegram, and encryption is optional rather than on by default, so users who need it must enable it deliberately.

project readme (upstream, from github) — read inline

English · Español

TeleDrive

Back up and browse your files using a private Telegram channel as storage.

Android Windows Linux macOS Kotlin Compose Release Downloads License

Buy me a coffee


Contents


About

TeleDrive stores your files in a private Telegram channel on your own account. There is no TeleDrive server and no account to create with us. The app keeps a local index so browsing and search stay fast and work offline.

One Compose Multiplatform codebase ships the Android app and the Windows, Linux x86_64 and macOS desktop apps. They share the storage engine, encryption, transfers and the entire UI layer, and all of them browse the same drive.

Features

  • Automatic backup: photos and chosen folders upload on their own on Android, with schedules, Wi-Fi and charging rules, and exclusion patterns
  • No file size limit: a 20 GB video is one file in the app, whatever Telegram caps a message at
  • Encryption: optional AES-256-GCM for file bodies, names, captions and the folder tree
  • File management: folders, favorites, hidden and archived items, trash and bulk actions
  • Streaming: video and audio play straight from Telegram with seeking, encrypted files included
  • Previews: images, PDFs, text and ZIP contents open inline
  • Multiple drives: separate channels for personal, work or photos on one account
  • Sharing: files arrive from the Android share sheet, and identical bytes are never uploaded twice
  • Transfers: parallel queue with pause and resume that survives reboots
  • Recovery: reinstall, sign in, enter your passphrase, and the whole drive is back
  • Device security: biometric app lock, screenshot blocking and an encrypted local cache

Screenshots

Install

Windows

Download TeleDrive-.msi from the releases page and run it. It installs per user with no admin prompt, adds Start menu and desktop shortcuts, and uninstalls from Windows Settings. Your session and settings live in %APPDATA%\TeleDrive and survive reinstalls.

Linux (x86_64)

Download from the releases page. Everything is included, so there is nothing else to install.

AppImage (most distros from 2022 or later)

  1. Download TeleDrive--x86_64.AppImage.
  2. Make it executable: right-click → Properties → Allow executing file as program, or chmod +x TeleDrive--x86_64.AppImage.
  3. Double-click it.

.deb (Ubuntu 24.04, Debian 13 or newer)

sudo apt install ./teledrive_<version>_amd64.deb

Then open TeleDrive from the applications menu.

macOS (Apple Silicon)

Download TeleDrive-.dmg from the releases page, open it and drag TeleDrive to Applications. The build is Apple Silicon only, because the Telegram native library TeleDrive uses has no Intel Mac build.

The app is not signed with an Apple Developer ID, so Gatekeeper blocks it on first launch. Clear the quarantine flag once and it opens normally from then on:

xattr -dr com.apple.quarantine /Applications/TeleDrive.app

Your session and settings live in ~/Library/Application Support/TeleDrive.

Media preview works out of the box. Like the Windows build, the app ships its own copy of libVLC, so there is nothing else to install. If it ever fails to load, a VLC in /Applications is used instead, and failing that the app still opens, browses, uploads and downloads, with preview falling back to opening the file in your default application.

Android

Grab an APK from the releases page. Builds are split per CPU architecture, so pick the one that matches your device:

APK Use it when
TeleDrive--arm64-v8a-release.apk Almost every phone from the last several years
TeleDrive--armeabi-v7a-release.apk Older 32-bit devices
TeleDrive--x86_64-release.apk 64-bit emulators and x86 Chromebooks
TeleDrive--x86-release.apk 32-bit x86, rare outside older emulators
TeleDrive--universal-release.apk You are unsure, or sideloading somewhere unusual

The universal one carries every architecture at once, so prefer a specific build unless you need the fallback. Most of that size is TDLib, the official Telegram library the app is built on.

Requirements

  • Android 8.0 (API 26) or newer, 64-bit Windows 10+, Linux x86_64, or macOS on Apple Silicon
  • A Telegram account
  • Your own Telegram API credentials, free from my.telegram.org under API development tools

To get credentials: sign in at my.telegram.org, open API development tools, and fill in an app name and short name. Anything sensible works, and the platform and description do not matter. The page then shows an api_id and an api_hash, which is what TeleDrive asks for on first launch.

You enter the API ID and hash at runtime and they are stored encrypted on device. They are never bundled into the app, written to logs, or sent anywhere except Telegram. Because they are yours rather than shared, your usage is never pooled with anyone else's, and a rate limit on someone else cannot affect you.

Getting started

git clone https://github.com/Mahmud0808/TeleDrive.git
cd TeleDrive
./gradlew :android:installDebug  # Android
./gradlew :desktop:run           # Windows/Linux desktop

Then in the app:

  1. Enter your API ID and hash.
  2. Sign in, either by phone number and login code, or by choosing Sign in by QR code. If Telegram is installed on the same device, the QR step offers a Confirm in Telegram button instead, so nothing needs scanning.
  3. Choose the folders to back up.
  4. Optionally enable Encrypt uploads and set a recovery passphrase.

TDLib native libraries come prebuilt on every platform: the tdlibx/td AAR via JitPack on Android and tdlight on desktop (Windows, Linux and Apple Silicon macOS), so no native toolchain is needed. The build picks the native matching the host, so a package never carries an unused set.

Packaging the desktop app

jpackage does the packaging, and the Android Studio runtime does not ship it. Point the build at a full JDK with a desktopJavaHome property in your global ~/.gradle/gradle.properties, then:

./gradlew :desktop:packageMsi           # Windows installer
./gradlew :desktop:packageDebUser       # Linux .deb with system dependencies
./gradlew :desktop:packageAppImage      # Linux AppImage for any distro
./gradlew :desktop:packageDmg           # macOS disk image
./gradlew :desktop:createDistributable  # portable app folder

packageDebUser produces desktop/build/deb/teledrive__amd64.deb. It embeds a JVM runtime via jlink and declares its Debian dependencies, so end users only need sudo apt install ./teledrive__amd64.deb. libVLC is not bundled on Linux, it is pulled in as a package dependency instead.

packageAppImage produces desktop/build/appimage/TeleDrive--x86_64.AppImage from the same app folder and bundles the libVLC installed on the build machine along with the libraries its plugins need. It runs desktop/packaging/linux/build-appimage.sh, which needs patchelf, desktop-file-utils, the libvlc5, libvlccore9, vlc-plugin-base and vlc-plugin-video-output packages, linuxdeploy and appimagetool. Put the last two on the PATH, or pass -Plinuxdeploy=/path/to/linuxdeploy and -Pappimagetool=/path/to/appimagetool. Build on the oldest distro you want to support, since the bundled libraries set the minimum glibc; release builds use Ubuntu 22.04.

Bringing existing files in

Already have files sitting in a channel, a group, or Saved Messages? Forward them into the drive TeleDrive created and they appear in the app after the next sync. Forwarding happens on Telegram's servers, so nothing is downloaded or uploaded again, and files of any size come across in seconds.

Select the messages in the Telegram app, forward them to your TeleDrive channel, then pull to refresh in TeleDrive.

What to expect for forwarded files:

  • Only messages sent as documents are picked up. A photo or video sent the normal way was compressed by Telegram into a media message, and those are skipped. Forward the original file version instead.
  • Captions are replaced. TeleDrive stores each file's name, folder and flags in the caption, so the first rename, move or trash overwrites whatever text the message carried.
  • No checksum is recorded, since the file is never read locally. Duplicate detection cannot match forwarded files, so uploading the same file later creates a second copy.
  • Files land at the drive root and stay unencrypted, because they were already stored that way. Move them into folders in the app afterwards.

Architecture

Kotlin Multiplatform with Clean Architecture and MVVM. The dependency rule is `presentation -> domain TeleDrive is an independent project, not affiliated with or endorsed by Telegram.

Frequently asked questions

Is TeleDrive free to use?

TeleDrive is open source under the Apache-2.0 licence. There is no licence fee and no seat count — you can self-host it or, where the project offers one, pay a vendor for a managed version instead.

What does TeleDrive do?

Turn a private Telegram channel into your personal cloud drive. Android, Windows, Linux and macOS, auto backup, optional E2E encryption, built-in file manager a

What is TeleDrive written in?

TeleDrive is primarily written in Kotlin. Its source is publicly available at https://github.com/Mahmud0808/TeleDrive, and it has 511 GitHub stars.