TAILS Linux: Create a Secure Air-Gapped Environment for Crypto Keys

If you need to handle a 24-word seed phrase, recover wallet access, or generate new keys without exposing them to your normal computer environment, TAILS Linux is one of the best practical tools I use. It gives you a disposable, isolated system that boots from USB and wipes temporary data when you shut down.

In this guide, I’ll walk through how to download TAILS, verify it, flash it to USB, boot into it, and configure it for an air-gapped crypto workflow. This is the written version of my video: Watch the video.

TAILS install page with verification steps highlighted
Use the official TAILS instructions and do not skip image verification

Why use TAILS for cryptocurrency key handling?

The main reason I recommend TAILS is that it lets you work in a temporary environment. You boot from USB, do your sensitive task, then shut down. When you shut down TAILS properly, it wipes the temporary data you entered during that session. That is much safer than opening a browser tab on your normal computer, typing in a seed phrase, and hoping nothing logged it.

For crypto key work, I treat any machine as potentially untrusted unless I have taken specific steps to isolate it. TAILS helps with that because:

  • It runs from USB rather than installing into your main operating system.
  • It can be used offline or with networking disabled.
  • Tor Browser is built in for the parts where you do need network access.
  • Non-Tor traffic is blocked by default, which adds protection against background leaks.
  • Shutting down wipes temporary data instead of leaving it on disk.

That said, TAILS is not magic. The biggest risk is still human error: using the wrong USB stick, skipping verification, entering keys while online, or trusting a fake download site. So the process matters as much as the tool.

Step 1: Download TAILS from the official website

First, go to the official TAILS website: tails.boum.org. I put a link in the video description, but you should still be careful when searching for it. If you search for “TAILS” on Google or another search engine, paid ads can appear that look similar but are not the real site.

When you get to the official TAILS website, click Install. You will then choose which operating system you are installing from. In my video I used Windows, but the same general process applies if you are using another supported host system.

You need a USB stick that is at least 8GB. Smaller sticks can fail in annoying ways: the flash may look like it succeeds, but then TAILS will not boot properly. USB sticks are cheap enough now that I would just use one with plenty of space and avoid the headache.

Before you start flashing anything, make sure you understand what you are doing. This process wipes whatever is on the selected USB device. If your stick contains personal files, back them up first. Even better: for a dedicated crypto TAILS setup, use a USB stick that does not contain anything you care about.

Step 2: Verify the downloaded image before burning it

This is the step I do not want you to skip.

After downloading the TAILS image file, verify it. The official instructions explain how to do this, and they provide a browser extension for verification in Chrome. If you download using BitTorrent, the torrent client can also help with integrity checking. If you are more technical, you can use OpenPGP verification as well.

For most people, the TAILS Verification browser extension is a practical option. It helps protect against one specific risk: what if someone compromised or spoofed the website you were using? The extension adds another layer of separation between the download page and the verification process. In other words, it makes it harder for an attacker to simply hand you a fake image with fake-looking signatures.

TAILS download page showing verification options
Download TAILS from the official site and verify the image

Install the extension from the Chrome Web Store if you are using Chrome. Once installed, use it to select your downloaded TAILS image file. The verification process may take a minute or two depending on your computer. Do not rush this part.

If verification fails, do not burn the USB stick and hope for the best. Delete the download, get it again from the official source, and verify again. If you are keeping multiple copies of the TAILS image on your network or old computers, I would still verify before flashing a new USB stick. It may feel paranoid, but this is exactly the kind of step that protects you from subtle tampering.

TAILS verification progress in Chrome
Wait for verification to complete before proceeding

Step 3: Flash TAILS to USB using Etcher

Once your image is verified, download Etcher as recommended by the TAILS instructions. In my video I used Balena Etcher. It has a simple workflow: select image, select target, flash.

Before you begin:

  1. Plug in the USB stick you want to use for TAILS.
  2. Unplug every other USB drive from your computer if possible.
  3. Confirm that Etcher is selecting the correct device.
  4. Select the verified TAILS .img file.
  5. Click Flash.

This step wipes the selected USB device, so double-check the target. If you have a 64GB stick and you are only using part of it for TAILS, that is fine. The important thing is that Etcher writes to the correct physical device.

Etcher ready to flash TAILS to USB
Select the correct image and target before flashing

Wait until Etcher finishes. Depending on your USB speed, this can be quick or slower than expected. Do not pull the stick out while it is still writing.

Step 4: Reboot and boot from the TAILS USB stick

When Etcher finishes, shut down your computer with the TAILS USB stick still plugged in. Turn the computer back on. If everything works automatically, you should see the TAILS bootloader menu.

If not, many laptops require you to press a boot-menu key during startup. This can be something like F11, F12, Esc, or another key depending on the manufacturer. The exact key varies by device. You may need to check your laptop documentation or look through the TAILS troubleshooting page for guidance.

Some machines also have BIOS settings that affect USB booting, such as fast boot or secure boot options. This part is very device-specific, so I will not try to cover every possible computer in this article. The important point is: if it does not automatically boot from USB, use your computer’s boot menu or BIOS/UEFI settings to make it do that.

Why running TAILS in a virtual machine is not enough for private-key work

In the video I demonstrated parts of TAILS inside VirtualBox because it was easier to record. The appearance and basic behavior are similar, but I want to be very clear: running TAILS in a virtual machine is not sufficient security for serious private-key work.

A VM can help isolate software from your host system, but it does not protect you from everything. If your host computer has malware that logs keystrokes or captures screen content, running TAILS inside a VM may still expose what you type. For sensitive crypto key handling, I want the environment to be as isolated as possible: real hardware booting from USB, with networking disabled when entering seed phrases or private keys.

So if you are doing high-value recovery work or generating new long-term keys, do it on a physical machine booted from TAILS USB, not just inside VirtualBox on your normal desktop.

Step 5: Configure keyboard layout and additional settings

After TAILS boots, you may need to adjust the keyboard layout. If your keyboard is not detected correctly, make sure the language and keyboard layout match what you expect. This matters because typing a seed phrase with the wrong layout can produce a completely different result.

You can also change formats if needed. There are additional settings for things like setting an administrator password if you plan to install software that requires superuser access. For this crypto workflow, I usually do not need to install extra software. Everything we want to run is local files opened in Tor Browser, so I keep the setup simple.

The important setting here is networking. If you are handling private keys or seed phrases, disable all networking. You can also unplug network cables or turn off Wi-Fi, but disabling it inside TAILS adds another layer of protection against forgetting something.

TAILS Additional Settings with Disable all networking selected
Disable all networking when handling private keys

For crypto key entry, I treat “offline” as the default state. If you do not need network access, do not use it. That simple habit reduces a lot of risk.

Step 6: Mount USB tools and understand Tor Browser file restrictions

You can plug in a second USB stick containing offline tools. In my example, I used a stick with files for seed recovery and key derivation, including Ian Coleman’s BIP39 tool. TAILS will usually mount the USB automatically. You should be able to see it under your Home folder or in the file manager.

Mounted USB stick with local crypto tools
TAILS can auto-mount a second USB drive containing offline tools

Here is where many people get confused: Tor Browser in TAILS has restricted file access. It cannot open just any file from anywhere on the system. If you try to open an HTML tool directly from the USB stick or desktop, you may get an “Access to the file was denied” error.

Tor Browser denying access to a local file
Files outside the Tor Browser folder are not accessible by default

This is a security feature, not a bug. Tor Browser can only access files placed inside its own sandbox folder. In TAILS, that folder is usually called Tor Browser in your Home directory. So if you want to run an offline HTML tool, copy it into the Tor Browser folder first.

Once the file is in the correct location, open it from there. In my video I used Ian Coleman’s BIP39 Mnemonic Code Converter as a local file. This kind of tool can be useful for generating phrases or deriving keys while staying offline. You do not need to trust an online website with your seed material if you are using a verified local copy.

Ian Coleman BIP39 tool loaded from a local file in Tor Browser
Run the local BIP39 tool from inside the Tor Browser folder

Step 7: Understand what “air-gapped” means in practice

When I say air-gapped, I mean no unnecessary network access. For key entry and seed phrase work, that usually means:

  • No Wi-Fi.
  • No Ethernet cable plugged in.
  • Networking disabled inside TAILS if possible.
  • No online tools involved in the sensitive step.

TAILS is also useful because even when Tor is active, non-Tor traffic is blocked by default. In my video I demonstrated this with a ping test and a Python script that tried to connect directly to an external server. The browser could use Tor, but direct network access from normal system tools was still blocked.

Non-Tor network attempts blocked while Tor Browser is available
Direct non-Tor traffic remains blocked even when Tor is connected

This does not make TAILS a perfect malware shield. It does, however, reduce the chance that some background process or poorly written script silently phones home with data it should not have access to. For crypto key handling, I like those extra layers.

Best practice for entering seed phrases and private keys in TAILS

My recommended workflow is simple:

  1. Boot into TAILS from USB on a physical machine.
  2. Verify your offline tools before you need them if possible.
  3. Disable networking.
  4. Confirm your keyboard layout is correct.
  5. Copy any local HTML tool into the Tor Browser folder.
  6. Open the tool and perform the key task while fully offline.
  7. Shut down TAILS when finished so temporary data is wiped.

Do not treat TAILS like a normal desktop. Do not leave it running for hours, install random software, browse online casually, and then type in your seed phrase. The safer habit is: boot up, do one specific sensitive task, shut down.

If you are new to this, think of TAILS as a clean room. You enter with the tool you need, do the work carefully, leave, and wipe the room when you close it.

A note on hardware wallets

If you have not used a hardware wallet yet, I still recommend one for many people. Devices like Ledger Nano S or Nano X give you an air-gapped-style signing experience with a device that can be used safely even on a compromised computer. You buy directly from the official vendor and keep the recovery process offline.

TAILS is especially useful when you need to work with seed phrases, recover access, generate new keys, or use local tools without trusting your normal operating system. A hardware wallet and TAILS are not mutually exclusive; they solve related problems in different ways.

Final thoughts

The most important things from this guide are:

  • Use the official TAILS website.
  • Verify the downloaded image before flashing it.
  • Use a USB stick of at least 8GB.
  • Unplug other USB drives to avoid wiping the wrong device.
  • Do not rely on a VM for serious private-key security.
  • Disable networking when entering seed phrases or private keys.
  • Copy local tools into the Tor Browser folder before opening them.
  • Shut down TAILS after sensitive work so temporary data is wiped.

If you are stuck with a recovery phrase, lost access to funds, or unsure whether it is safe to enter your seed somewhere, be careful and avoid websites that ask for your 24 words online. You can also see my recovery services consultations page if you need help understanding your options.

The goal is not just to use a “secure” tool once. The goal is to build good habits around key material: verify, isolate, stay offline when it matters, and shut down cleanly when you are done.

Questions from viewers

Common questions from the comments on this video, with my answers.

Why is Tails preferred over Whonix or running a standard Linux distro for handling private keys?

The key feature you want is being fully amnesic, which Tails does by default. This ensures no trace of your activity remains on the system. While a secondary OS like Mint or Kali could work if you are very careful, you still have to trust the integrity of that OS and the virtualization environment. Tails is designed so that even if you make mistakes, the environment wipes itself on reboot, making it much safer for sensitive key material than persistent systems.

How do I send transactions if the network connection is disabled in Tails?

You can use a 'watch-only' wallet on an online machine to create the transaction. You then pass that unsigned transaction to your offline Tails environment to sign it with your private keys. Once signed, you move the transaction back to the online machine to broadcast it. This way, your private keys never touch the internet.

Is it safe to store my mnemonic seed phrase in Tails persistence?

Yes, you can use Tails persistence to store your seed, but you must be extremely careful. If you do this, you should always keep a separate, physical, offline copy of your seed as a backup. Relying solely on the digital persistence file increases risk if the USB stick is compromised or lost.

Why did you use a second USB drive with files instead of downloading tools inside Tails?

I used a second USB stick containing offline files (like Ian Coleman's BIP39 tool) so that I could run them without needing an internet connection at all. This allows you to disable networking immediately upon booting into Tails, rather than having to download software first and then remembering to disconnect. It’s a cleaner workflow for ensuring your keys are generated or derived completely air-gapped.

Can I use closed-source software wallets like Exodus within Tails?

No, I would not recommend that. Tails is a minimal operating system, so installing complex software isn't straightforward. More importantly, using a closed-source wallet undermines the security benefits of being air-gapped and running on Tails. If you prefer a user-friendly interface like Exodus, it is better to use a standard OS like Ubuntu where such apps are supported, rather than trying to force them into a secure, minimal environment.

Is it risky to write down my 24-word seed while using an online tool?

If you are using a tool like Ian Coleman's BIP39 generator, it is important to understand how it runs. In the video, I demonstrate running it as an offline file in the browser within Tails. Because Tails wipes itself on reboot and the file is local, even if the code were malicious, the environment is isolated. However, generally speaking, you should avoid entering seeds into websites that require an active internet connection. Always verify you are working with local, offline files when possible.

Stuck with a wallet recovery?

I maintain BTCRecover and have helped people recover seed phrases, passphrases and wallet passwords since 2019. Book a one-hour video session and I’ll walk you through doing the recovery yourself, without sharing your seed. Or, if you’d rather I run it, a trusted recovery is charged only if it succeeds.

Private sessions: US$100 per hour. Trusted recovery: 10% of recovered funds. I never contact people first and will never ask for your seed phrase over chat or email.

Found this useful?

These guides are free and ad-free. You can support them by sharing them, subscribing on YouTube, or sending a tip.

Stuck on this?

Book a one-hour session and I’ll walk you through it, or ask about a trusted recovery.

Recovery guides

More guides