Overview
Telegram Desktop is the native client rather than a wrapper around the web version, and the difference shows in the things people use it for: dragging a multi-gigabyte file into a chat and having it upload without a browser holding it in memory, searching years of history instantly, and keeping dozens of channels readable without the machine slowing down.
History lives on the service side, so a new install signs in and everything is already there rather than syncing from a phone. Groups scale to enormous membership with admin roles, slow mode, permissions and pinned content, and channels give a one to many broadcast with reactions and comment threads attached. File transfer allows single files far larger than the usual messenger limits, with any file type accepted.
The desktop client adds things the mobile application has no room for. Multiple accounts running side by side in one window, a folder system for sorting chats into tabs, a proper keyboard shortcut set, chat export to a readable local archive, and a settings panel that exposes the network, proxy and storage behaviour rather than hiding it.
What it does well
Cloud history
Every chat is available on any signed in device instantly, with search across the entire archive rather than a local window of it.
Large file transfer
Send single files far past the limits of the usual messengers, any file type, with resumable transfers on both ends.
Multiple accounts
Several accounts open in one window with independent notification settings and quick switching.
Folders and filters
Sort chats into tabs by type, unread state or custom rules, which is what makes a hundred channels manageable.
Export and storage control
Export any chat to a readable local archive, and set exactly how much of the cache lives on disk and for how long.
Changes in this build
- Media viewer rebuilt with faster loading on long photo and video sequences.
- Folder rules extended with per-folder notification settings.
- Reduced memory use on accounts with very large channel subscriptions.
- Improved proxy handling with per-account proxy selection.
- Fixed a notification duplication issue when several accounts were signed in.
What is in the package
- Telegram Desktop installer, 32-bit and 64-bit
- Portable build for running from removable storage
- Multilingual interface files, 40 languages
- Chat export module
- Default emoji and sticker sets
System requirements
| Processor | Any x86 or x64 processor |
| Memory | 1 GB minimum, 4 GB for heavy channel use |
| Graphics | Any GPU with a current driver |
| Storage | 300 MB plus cache space |
| Display | 1024 x 768 minimum |
| System | Windows 7 through Windows 11 |
Installation
- Extract the archive and choose the installer or the portable build.
- Run setup, or copy the portable folder to the drive you want it on.
- Sign in and let the chat list populate before opening large media.
- Set the cache size limit in advanced settings.
- Add a second account from the account menu if you use more than one.
Before you start
The cache grows quickly on media heavy channels, set a limit rather than clearing it by hand.
The portable build keeps its data in its own folder, which makes it suitable for removable storage.
Chat export writes a plain local archive, which is worth doing before wiping a machine.
Questions about this title
Does it need the phone application running?
No, the desktop client signs in on its own and history comes from the service.
How large a file can it send?
Far larger than the usual messenger limits, and any file type is accepted.
Can I run two accounts?
Yes, several at once in the same window.
Is there a portable version?
Yes, it is included alongside the installer.
About this listing
This entry was checked on a clean install of Windows 7 / 8 / 10 / 11 (32-bit and 64-bit) before it was published, and it is rechecked whenever the package is rebuilt. The figures on this page come from the site index rather than from the publisher, so the download count is what people here have actually pulled.
If a mirror stops answering, use the contact form and it gets replaced. Reports about a specific title are handled faster than general messages because they name the file, the mirror and the point at which the transfer stopped.
Requests for a different version, a different language build or an older release go on the requests page. Older versions of a title are usually still held even when only the current one is listed.