64Gram has three names, a struck-through founding reason, and a GPL with an exception
64Gram (unofficial Telegram Desktop)
At a glance
- What is it?
- TDesktop-x64/tdesktop is an unofficial fork of Telegram Desktop published as 64Gram, with the upstream source vendored in-tree and a CMake build. Its project goal says Windows 64-bit while its supported list says Linux and macOS, its original justification is struck through rather than replaced, and its features live in a separate file.
- Who is it for?
- 64Gram is worth following if you want a Windows 64-bit Telegram Desktop build with a visible fork policy, because the licence, the OpenSSL exception, and the separate legal file are all present rather than left implicit, and releases carry the fork's own version numbers. Three things to check first.
- Can I use it commercially?
- Yes, with conditions. GPL-3.0 is a copyleft licence: if you distribute software that includes it, you must release that software's source code under the same licence. Running it internally without distributing it does not trigger that obligation.
- Is it still maintained?
- Yes. The repository received new commits within the last day.
- What is it written in?
- Mainly C++, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.
Star history
- TDesktop-x64/tdesktop3,017 ★ · +87
| Repository | 2026-09-24 | 2026-11-15 |
|---|---|---|
| TDesktop-x64/tdesktop | 2.9k | 3k |
87 Stars in the last 52 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
Three identities for one piece of software
Follow the names through this repository and there are three of them. The owning account is a generic name for a 64-bit build. The repository is named tdesktop, which is the same name as the upstream project it forks, so the fork's repository and its upstream repository share a repository name and differ only by owner. And the product is 64Gram, which is what the readme title uses, what the release titles use, and what the project's own changelog file is named. The repository description is the shortest statement of all: an unofficial Telegram Desktop. So the artefact you download is 64Gram, the code lives under a name that belongs to somebody else, and the page tells you in one word that it is not the official client.
The founding rationale is struck through rather than replaced
The project goal section has two parts and the interesting one is deleted. The surviving sentence is a statement of purpose: provide a Windows 64-bit build with some enhancements. Underneath it, the entire original justification is wrapped in strikethrough markers, and it read as the reason the project existed at all: because the official Telegram Desktop did not provide a Windows 64-bit build, this project aimed to provide a native 64-bit build with a few enhancements to everybody. The strikethrough leaves the sentence visible in the rendered page, so a reader sees the claim and its retraction at the same time. No replacement reasoning is given, and the surviving sentence quietly drops the premise while keeping the word enhancements. That is the whole story of why the project still exists, told in two lines, one of them crossed out.
The goal says Windows x64 and the supported list says Linux and macOS
The project goal names one platform. The supported systems section names three: Windows 7 and above, Linux 64 bit, and macOS above 10.12. Those two lists are describing different projects. A project whose purpose is a Windows 64-bit build does not usually list Linux and macOS as supported systems, and a project that lists Linux and macOS is not primarily a Windows 64-bit build. What the readme does not offer is any statement about what the enhancements are, which is where the supported-systems list becomes the more useful of the two. The macOS floor is stated as greater than 10.12 and above, and the Windows floor as version 7, both of which are considerably older than anything currently shipping.
The Linux build is a container and the Windows build is two architectures
Three build instructions are linked, and they are not symmetric. Windows has one document covering both 32-bit and 64-bit. macOS has its own. GNU/Linux is documented as a build using Docker. So the platform the project does not claim as its purpose is the one whose native build is not documented at all, and the platform it does claim is the one with the most complete coverage, including a 32-bit target that a project aiming at 64-bit would not obviously need. The build system underneath is CMake, with a static analysis configuration for C++ at the root, and the upstream source is vendored into the tree rather than fetched at build time, which means building the fork means compiling the whole client.
The entire feature list is one link away
The readme's features section contains no features. It is a heading and a link to a separate markdown file in the same repository. Everything this fork adds to the upstream client, which is the entire reason to use a fork rather than the official build, is documented somewhere the readme does not summarise, in a file whose size and structure are not indicated. The roadmap section is two words long, and they are a joke: no roadmap, yes. Both of those choices are defensible for a project that wants to avoid maintaining a changelog narrative in its front page, and both leave a reader with two things to fetch before they can decide anything. The changelog situation is the same: the releases are titled with the fork's own version numbers, but the root carries two changelog files, one named for the product and one not.
GPLv3 with an OpenSSL exception, a legal file, and plain GPL-3.0 in the metadata
The licence needs reading in three places. The licence field attached to the repository reads GPL-3.0, with no exception. The readme says the source is published under GPLv3 with an OpenSSL exception. And the tree carries both a licence file and a separate file whose name is simply legal. All three can be true at once, because a copyleft licence with an exception is still a copyleft licence as far as a scanner is concerned, and a licence scanner reading only the metadata field will report the weaker of the two facts. For a fork that vendors a large upstream codebase, the presence of a dedicated legal file alongside the licence text is a sign that the boundary between upstream code and fork additions has been thought about, which is more than most forks bother with.
Three agent instruction sets and two changelog files at the root
The root of this repository is busy in a way that says something about how the project is worked on. There are three hidden directories whose names are the names of AI coding assistants, each with a matching instruction file at the root beside the human-facing ones. So three assistants' conventions are checked into the same tree as the build system. Next to them sit a review file, a dev container configuration, a changelog file named for the product and a second one that is not, and a snap packaging directory that the readme never mentions. The snap directory in particular is the kind of thing a packager looks for in the releases and does not find documented anywhere in the readme, because the readme covers Windows, macOS, and a containerised Linux build and stops there.
The preview image is served from the development branch
Small thing, and it is the kind that ages badly. The readme's preview image has two link targets, and both are pinned to the development branch rather than to a release or to the default branch's stable state. The default branch here is named dev, so the image at the top of the readme changes whenever anything changes on that branch, including an in-progress edit to the image itself. The same is true of the localisation instructions and the preview asset path. Nothing else in the readme is version-pinned, so the difference is easy to miss. It matters mostly for anyone mirroring the readme, since the rendered content on the readme page will drift from the copy in any release tag.
Editorial conclusion
64Gram is worth following if you want a Windows 64-bit Telegram Desktop build with a visible fork policy, because the licence, the OpenSSL exception, and the separate legal file are all present rather than left implicit, and releases carry the fork's own version numbers. Three things to check first. The project describes itself as unofficial and the repository is named identically to the project it forks, so nothing in the naming tells you which code you are running. The feature list is one link away in a separate file and the roadmap is two words long, so you have to fetch both yourself. And the metadata records a plain GPL-3.0 while the documentation says GPLv3 with an OpenSSL exception, which matters if you redistribute.
Frequently asked questions
What is 64Gram, and is it the official Telegram Desktop?
No. The repository description calls it an unofficial Telegram Desktop, and the readme title identifies it as 64Gram based on Telegram Desktop. The owning account is named for a 64-bit build and the repository is named after the upstream project, so only the product name distinguishes it in the release titles.
What platforms does 64Gram support?
The readme lists three: Windows 7 and above, Linux 64 bit, and macOS above 10.12. That list does not match the stated project goal, which is to provide a Windows 64-bit build with some enhancements. The feature list itself is a link to a separate file rather than a summary in the readme.
How do you build 64Gram?
Three build documents are linked. One covers Windows for both 32-bit and 64-bit, one covers macOS, and the GNU/Linux one is documented as a Docker build rather than a native one. The build uses CMake with a C++ static analysis configuration, and the upstream source is vendored into the repository, so building the fork compiles the whole client.
What licence is 64Gram published under?
The readme says GPLv3 with an OpenSSL exception. The licence field attached to the repository reads a plain GPL-3.0 with no exception, and the tree carries both a licence file and a separate legal file. All three statements can hold at once, but a scanner reading only the metadata will report the weaker fact.
How do I translate 64Gram?
Translations live in a separate localisation repository rather than in this one, and there is a translation template keyed by language. The instruction is to find your language identifier in Telegram's own log file, where a line records the current language pack identifier, and then name your file after it. The note also says to ignore the base identifier, whose translation is described as a work in progress.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/tdesktop-x64-tdesktop)Star history chart for your README
[](https://hysenlabs.com/projects/tdesktop-x64-tdesktop)Was this useful?