Choose a compatible Linux package
Linux packages are not currently offered here. If you already have a trusted package, check its architecture and requirements. Distribution packages and standalone archives have different installation and update procedures.
Use the update method associated with your installation. A distribution-managed package is typically updated by its package manager; an archive may use its own update process. Follow the instructions for the package you actually installed.
Extract, launch and sign in
For an archive, keep its extracted files together in a folder owned by your normal user and read the included instructions.
- Download the Linux archive and compare its checksum with a trusted reference if one is supplied.
- Extract the archive with a tool that supports its format, then locate the Telegram executable.
- Launch the executable as your normal user. If an execute-permission error occurs, inspect the file permissions and the package instructions before changing them.
- Scan the displayed login QR code using the link-device option in Telegram on your phone, or choose phone-number login and complete the verification steps. Enter your two-step verification password when requested.
Troubleshoot launch and connection errors
An executable-format error can indicate the wrong processor architecture; a missing-library error can indicate a runtime requirement. Read the exact message and consult your distribution’s package information.
If Telegram opens but cannot connect, check your network, firewall and configured proxy. Notifications can depend on the desktop environment. Avoid running the app as root to work around ordinary user-permission problems.
Understand chat syncing and protect local data
Telegram Desktop on Linux synchronizes cloud chats and does not support Secret Chats. A Secret Chat created on a phone is not transferred to the Linux desktop when you sign in. Review linked devices in Telegram settings to confirm that you recognize every active session.
Keep downloaded packages and local account data in private folders. Never share verification codes or your two-step verification password. A checksum confirms that a file matches a reference only when that reference is trustworthy; it does not replace checking the package source. Sign out before handing a computer or account-data folder to someone else.