Kotatogram Desktop: Telegram fork with local folders and bulk forwarding

Kotatogram's place beside official Telegram Desktop

Kotatogram Desktop addresses a specific gap: users of Telegram Desktop who want local folder organization and more control over forwarding and presentation. Its audience is not developers looking for a Telegram API library. It is desktop users who already rely on Telegram accounts and chats but want a client with additional interface behavior. The README describes the repository as an "experimental Telegram Desktop fork," and its default branch is `dev`.

That distinction matters because Kotatogram remains tied to the upstream Telegram Desktop client rather than operating as a separate messaging service. Its listed features include local folders, forwarding to multiple chats, forwarding without the author, custom fonts, a compact chat list, custom text replacements, configurable sticker size, and adaptive chat bubbles. This is a focused client customization project, not a general-purpose chat automation platform.

The trade-off is release confidence. The repository's release history lists k1.4.9 as a beta based on TD 3.5.2, dated 2022-03-08. Earlier entries are k1.4.8 from 2021-12-31 and k1.4.7 on the same date. The README also says the full feature list will be rewritten later and points to a separate repository for deprecated control branches. A prospective user therefore cannot use the README as a complete compatibility matrix.

The repository is not archived, and its last push was on 2026-10-06. That establishes source activity, but it does not establish that a current tagged binary exists. Recent commits and an old published beta answer different questions, so both require inspection.

Local folders, forwarding, and interface controls

The clearest adoption case is a Telegram Desktop user who needs the documented local folders feature. The README lists "Local folders" first among the features. It does not describe their storage format, synchronization behavior, or limits, so the exact semantics should not be inferred from the feature name.

Forwarding is the second major differentiator. Kotatogram can forward a message to multiple chats and can forward it without the author. The latter removes attribution from the item as presented by the client. That can fit users reorganizing content across chats, although the README does not explain how this interacts with protected content, message metadata, or account restrictions. Any adoption decision should treat these as client capabilities, not permission to bypass Telegram controls.

The presentation options are more conventional but still useful. A custom font and compact chat list can alter density and readability. Custom text replacements can turn frequently typed fragments into substituted text. Change sticker size and adaptive chat bubbles affect how media and message containers are displayed. These are client-side choices by category, but the README does not confirm where each setting is stored or whether it synchronizes.

These features make Kotatogram more relevant than an unmodified client only when at least one addresses a recurring need. A user with no interest in local folders, forwarding behavior, or visual controls has little documented reason to take on an unofficial fork.

From Telegram source tree to desktop builds

The repository layout shows the implementation and build machinery expected from a Telegram Desktop-derived C++ project. `Telegram/` is the principal source area, while `lib/` contains supporting library content and submodules are declared through `.gitmodules`. Build orchestration begins at `CMakeLists.txt`, with additional configuration under `cmake/` and build-related files under `tools/`. A `snap/` directory is also present, and the README lists Windows, Linux, and macOS as build targets.

The upstream inheritance is explicit. The README says the original README with licenses can be found in the Telegram Desktop repository, and Kotatogram keeps project-specific change information in `kotatogram_changes.txt` and `changelog.txt`. Based on this structure, build evaluation requires checking Kotatogram's branch instructions and documentation alongside Telegram Desktop's upstream requirements. The README does not document the compiler versions, dependency initialization commands, build options, or generated configuration files needed to reproduce a build.

Build-platform support is uneven at the documentation level. Windows and Linux build instructions are said to be updated, while macOS is listed as a build target without a corresponding updated macOS guide in the README. The repository includes Windows, Linux, and macOS workflow badges, but badges alone do not establish current artifact availability.

For engineering adoption, the absence of a complete command sequence is a material limitation. A team should identify the exact branch, upstream revision, dependency state, and packaging output before committing to internal builds. The repository layout suggests those concerns are centralized enough to inspect, but the README does not document them in a self-contained way.

Installing Kotatogram and choosing the first build

The safest first action for an end user is to use a published binary rather than build from source. The README directs users to `https://github.com/kotatogram/kotatogram-desktop/releases` for binaries and separately provides `https://github.com/kotatogram/kotatogram-desktop/releases/latest` for the latest stable release. There are no installation commands in the README, so no package-manager invocation can be confirmed.

Before downloading, inspect the release title and notes. The repository's release listing can contain beta releases. The newest release shown in the repository's release history is `k1.4.9`, described as a beta based on `TD 3.5.2`, rather than a release labeled as the current stable version.

If the intent is to compile the code, start with the platform guide rather than the download page. Windows users are directed to `docs/building-win.md`, and Linux users to `docs/building-linux.md`. Those documents are the correct source for commands and prerequisites. The README does not provide those command sequences, and no macOS build guide is linked there.

Linux has an additional documented distribution route through Flathub with application identifier `io.github.kotatogram`. Packaging status for other repositories is linked through Repology. These options are alternatives to the GitHub binary listing, not guarantees of version parity. Verify the published Kotatogram version and its Telegram base before signing in to an account.

Release age, upstream drift, and upgrade work

Kotatogram's largest adoption cost comes from its position between two moving targets. It must track Telegram protocol and client behavior while carrying fork-specific features such as local folders, forwarding controls, and interface changes. The release label connecting k1.4.9 to TD 3.5.2 gives a compatibility marker, but it does not show which upstream Telegram Desktop revision is present on the current `dev` branch.

The last push was on 2026-10-06, so the repository is receiving source activity. However, the most recent listed release is still k1.4.9 from 2022-03-08. This gap matters for production use. A current commit can contain changes that have never appeared in a tagged binary, while an old binary may lack fixes or compatibility work accumulated later on `dev`.

Upgrade planning is not documented. The README does not define a migration guide from one Kotatogram release to another, a rollback procedure, or rules for moving local folder data between installations. Because local folders appear to be client-managed, an engineer should not assume that Telegram account synchronization can recreate local state. The exact data directory and migration behavior need inspection in the selected build.

Kotatogram is licensed under GPL-3.0. That matters for organizations considering redistribution or modified builds because source and license obligations can apply to distributed derivatives. This is not legal advice. The repository's `LICENSE` and `LEGAL` files should be reviewed for the intended build and distribution model.

Why official Telegram Desktop or source builds may fit better

The practical alternative is official Telegram Desktop. It is the upstream client from which Kotatogram derives, so it is the relevant comparison for users who do not need Kotatogram's documented features. Choosing upstream avoids maintaining a separate fork relationship, although the README does not provide a feature-by-feature comparison.

A second alternative is building Kotatogram from a reviewed `dev` commit. That suits an engineering team that can reproduce the build and assess source changes directly. It does not solve upstream drift by itself. The team still needs to identify the Telegram Desktop base, inspect submodules, compile the C++ application, package the result, and decide whether changes on `dev` are acceptable for its users. None of those procedures is supplied as a complete recipe in the README.

Kotatogram is the wrong tool when supported binaries, predictable upgrades, complete platform documentation, and a concise release record matter more than its custom features. It may also be unsuitable for users who cannot distinguish a current `dev` build from a maintained stable release. The experimental label signals that the project does not present itself as a routine drop-in release channel.

The decision should therefore turn on one named requirement. If that requirement is local folders or multi-chat forwarding, Kotatogram has a documented purpose. If it is simply "a Telegram desktop client," the additional fork and release-management cost is difficult to justify from the repository information.

Editorial conclusion

Kotatogram Desktop fits users who specifically need its local folders, multi-chat forwarding, or presentation controls and can tolerate an experimental Telegram fork. It is a poor choice for routine corporate deployment or users who require a current, clearly documented release trail. Verify the selected artifact, Telegram compatibility, account and data migration procedures, platform build status, and the GPL-3.0 obligations first; the latest listed beta remains k1.4.9 from 2022-03-08.

Frequently asked questions

Official sources

1. kotatogram/kotatogram-desktop on GitHub
2. License: GPL-3.0
3. Project website
4. README
5. Releases