> For the complete documentation index, see [llms.txt](https://docs.cakewallet.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cakewallet.com/get-started/install/linux.md).

# Linux

Install Cake Wallet on Linux with the recommended Flatpak from GitHub releases or the manual tar.xz archive, with terminal commands to install and run it.

{% hint style="info" %}
Cake Wallet's desktop apps are being overhauled and redesigned, with the refreshed release slated for **late 2026**. Linux builds are still available and maintained below, but until that work is complete we recommend using the mobile apps — [Android](https://docs.cakewallet.com/get-started/install/android) or [iOS](https://apps.apple.com/us/app/cake-wallet/id1334702542) — for the best and most up-to-date experience whenever possible.
{% endhint %}

## Flatpak (Recommended)

If your system does not already have Flatpak installed, please do so by following the instructions on <https://www.flatpak.org/setup/>

Once Flatpak is installed (can test by running `flatpak` in the terminal), you will also need to install the [Flathub repository](https://flathub.org/) by running:

```bash
flatpak remote-add --if-not-exists flathub https://dl.flathub.org/repo/flathub.flatpakrepo
```

Now you can download the Cake Wallet Flatpak from the releases on GitHub <https://github.com/cake-tech/cake\\_wallet/releases> and select the Cake\_Wallet\_vX.X.X.flatpak file to download. (Example: Cake\_Wallet\_v4.18.2\_Linux.flatpak)

{% hint style="info" %}
Not every release includes Linux files. If the newest release doesn't list a `_Linux.flatpak` or `_Linux.tar.xz` file under **Assets**, scroll down to the most recent release that does.
{% endhint %}

Assuming the Cake Wallet flatpak is in the Downloads directory, install it with:

```bash
flatpak install ~/Downloads/Cake_Wallet_v4.18.2_Linux.flatpak
```

(Change the version number to the one you downloaded.)

After confirming the installation, launch Cake Wallet from your shortcuts, or run it manually with:

```bash
flatpak run com.cakewallet.cake_wallet
```

## Manual (tar.xz)

Download the tar.xz release from GitHub <https://github.com/cake-tech/cake\\_wallet/releases> (Example: Cake\_Wallet\_v4.18.2\_Linux.tar.xz)

Extract the archive using your file explorer or from the terminal:

```bash
tar -xf Cake_Wallet_vX.X.X.tar.xz
```

Run the executable by right-clicking and selecting "Run" in your file explorer or starting it from the terminal:

```bash
./cake_wallet
```

## Verify your download

Each GitHub release that includes Linux files lists the SHA-256 hash of every file in its release notes. After downloading, open a terminal and run:

```bash
sha256sum ~/Downloads/Cake_Wallet_vX.X.X_Linux.flatpak
```

(Use the name of the file you downloaded, including `.tar.xz` for the manual install.) The output must match the hash listed for that file on the release page. If it doesn't, delete the file and download it again. The published SHA-256 hash is the way to check a Linux download; there are no separate signature files.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.cakewallet.com/get-started/install/linux.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.