Installing Telegram on Linux: Flatpak, Snap or Tarball

terminal One application, three packages — and two different publishers

Telegram itself publishes one Linux build: a compressed archive from desktop.telegram.org. You unpack it, you run it, and it updates itself. That is the build that comes directly from the people who wrote the software, signed the way Step 002 described.

The Flatpak and the Snap are packaged from the same source by people in those ecosystems. This is entirely normal on Linux — it is how most software reaches most distributions — and the packagers in question are visible and accountable. But it is worth knowing, because it explains the two things people notice: the packaged builds sometimes trail the direct one by a few days, and they behave differently with files and screens because the packaging confines them.

Your distribution's own repository may also carry a Telegram package. Those vary enormously in how current they are, and a very old client is eventually refused by the servers. If your distribution ships a recent one, use it; if the version is a year behind, take the archive.

public The two things that actually go wrong

Almost every Linux-specific complaint about Telegram is one of two problems, and both have short answers.

Screen sharing shows a black rectangle. On Wayland an application cannot simply grab the screen; it has to ask through a desktop portal, and the portal is a separate package matched to your desktop environment. Install the portal for GNOME, KDE or wlroots as appropriate, make sure PipeWire is running, and the monitor picker appears as it should. Nothing is wrong with the client — it is asking a component that is not installed.

The tray icon is missing. Several desktop environments no longer show legacy tray icons without an extension, which makes an app that minimises to the tray appear to vanish. Either add the extension your desktop uses, or stop treating the tray as the place the app lives. This is not a Telegram decision and no setting inside Telegram fixes it.

A third, smaller one: if you want the client to start quietly with your session rather than opening a window across your screen, it takes a start-minimised flag on the command line, or the equivalent switch in the application's own settings. Tiling window manager users generally want the flag in their session file.

folder_open Where your session lives

As on Windows, Telegram Desktop keeps its authorisation and its cache in a folder called tdata. Where that folder sits depends on the packaging: under your local share directory for the archive build, inside the Flatpak's own application data directory, and under the Snap's directory in your home folder for a Snap.

The warning from Step 003 applies identically here, and on a multi-user machine it deserves repeating. That folder is a signed-in session. Anyone who can read it — another account on the same machine with loose permissions, a backup you copied to a shared drive, a home directory on a network mount — can open your account elsewhere with no password and no code. Turning on the local passcode in Settings, under Privacy and Security, encrypts it and closes that door.

It also means there is nothing to back up. Copying tdata to preserve your chats is unnecessary, because the chats are not in it; signing in on a new machine produces the same history. The only thing that folder saves you is typing a code, which is a poor trade for leaving your account lying in a backup archive.

touch_app Try it now — five minutes

Four things worth settling on the day you install it. Each one prevents a problem that otherwise surfaces weeks later, when you have forgotten what you configured.

1. Install the desktop portal for your environment now Not when a call starts. Screen sharing is the single most common Linux complaint about this client, the fix is a package rather than a setting, and testing it takes thirty seconds against your own second monitor.
2. Cap the cache and restrict automatic downloads Settings, then Advanced, then Data and Storage. A desktop client left open in a busy channel will fetch a great deal of video nobody watches. Capping the cache controls the disk; restricting automatic downloads is what controls both disk and bandwidth.
3. Turn on the local passcode Settings, then Privacy and Security. This is the setting that makes the session folder useless to anyone who copies it, and on a shared or networked home directory it is not optional.
4. Decide how it starts with your session Either enable the option in the client's own settings, or add the start-minimised flag to your session file if you run a tiling window manager. A client that opens a full window on every login is a client you will disable and then miss messages from.

help Common questions at this stage