Telegram-Archive

Free

Telegram-Archive does not print a price. The repository is the product, and the license field on 18 Oct 2026 was GPL-3.0. The README says GPL-3.0-or-later. There is no hosted plan, no seat fee, and no checkout in the README. You pay for the machine you run it on, and you use your own Telegram account. Docker images named in the README for v9.3.3 are drumsergio/telegram-archive and drumsergio/telegram-archive-viewer. The pip package is telegram-archive. None of those lines is a bill. GPL terms apply if you redistribute the software. They do not transfer Telegram's own terms, and they do not include a support contract. If a third party sells hosting, that price is theirs. It was not on the repository page opened for this listing.

The README describes a backup of your own Telegram account, run in Docker or from pip. It saves messages, media, edits, and deletions on your disk. Photos, videos, voice notes, stickers, documents, and link previews are stored once even when several chats share them, and files over a size you set are skipped. The documentation site says files over 100 MB are skipped by default. The viewer is a local website. The README says it never talks to Telegram, and the Docker instructions open it at 127.0.0.1:8000 after you sign in with a viewer username and password. The first backup still needs the code Telegram sends you, and a two-step password if the account has one.

• v9.3.3 on 12 Oct 2026. That release is the latest the API returned on 18 Oct 2026. The repository was pushed on 15 Oct 2026.
• GPL field and README. The API license field was GPL-3.0. The README says GPL-3.0-or-later. Quote both.
• Your account, local viewer. Backup needs your api_id and api_hash. The viewer never talks to Telegram. Files over 100 MB are skipped by default.

1. 1

   Read the Docker or pip instructions in the project docs before you create an api_id.

2. 2

   Back up an account you control. The login step uses the code Telegram sends that account.

3. 3

   Open the viewer on the machine you host. The README uses 127.0.0.1:8000.

4. 4

   Treat a skipped large file as a size limit until you check the setting and the chat.

• A team wants a local copy of an account it already administers. Read the README before anyone creates an api_id. The project backs up that account to a machine you host, in Docker or from the pip package telegram-archive. Release v9.3.3 was published 12 Oct 2026. The viewer, which the README says never talks to Telegram, is opened on localhost after you enter the code Telegram sent the account. This is not a method for an account you cannot log in to.
• Legal asks which license to attach to a fork. On 18 Oct 2026 the GitHub API field was GPL-3.0, with 228 stars and 42 forks, and the README said GPL-3.0-or-later. Put both sentences in the note. The API field is the SPDX value. The README's or-later line is the project's additional statement. Neither sentence licenses the contents of a chat. Messages in the backup stay the account holder's copies.
• A reviewer cannot find an attachment. The docs say files over 100 MB are skipped by default, and the README says you can set that size. Check the setting and the backup log before you call the file deleted. Edits and deletions are only as complete as the runs that were scheduled. The local viewer will not refresh itself from Telegram. This listing did not sign in, so it has no chat to show.

Hard cases

The case where the first result is easy to over-read.

Questions

Titled sources. These public pages are what the quotes on this listing come from.