Tails USB image
Use this path to create a bootable Tails USB stick from Windows, macOS, or Linux.
- Best for normal Tails use
- Runs as a live operating system
- Supports Persistent Storage
Get the right Tails image for a bootable USB or virtual machine, then follow a clear path from download to first boot. We send you to the official Tails source and never repackage the files.
Buttons lead to the official tails.net download flow. No repackaged files.
The USB image is the normal choice. The ISO has a narrower job and should not be treated as a universal replacement.
Use this path to create a bootable Tails USB stick from Windows, macOS, or Linux.
Use the ISO for a virtual machine, DVD, or a workflow where the official instructions specifically request it.
Tails is designed to start from removable media on a compatible 64-bit computer. Check your hardware and keep a backup of anything already stored on the USB drive because writing the image erases it.
Read the complete system requirements →Open the official installer for your current operating system and select the recommended image.
Verify the image when prompted, then use the recommended writing tool to create the USB.
Restart, open your computer's boot menu, select the USB device, and wait for the Tails welcome screen.
A Tails OS download is a complete live operating-system image, not a Windows installer, macOS application, browser extension, or ordinary folder of portable programs.
When the verified image is written correctly, the computer starts Tails from removable media instead of loading its internal operating system. This separation lets you use the Tails desktop and included applications without installing them into Windows, macOS, or Linux. The USB remains connected throughout the session because the running system continues to read from it.
The normal Tails OS download path uses a USB image. An ISO serves virtual machines, DVDs, and documented advanced workflows, but a VM depends on the host and does not reproduce every property of starting directly on compatible hardware.
Tails is designed to route supported network traffic through Tor and to reduce accidental direct connections. That design supports privacy-focused research and communication, but it is not a promise that every action becomes anonymous. Signing into an identifying account, opening a revealing document, sharing personal details, or using compromised hardware can still expose information.
Before depending on a Tails OS download, read current official guidance for network connection, bridges, unsafe browser behavior, documents, metadata, and application limitations. Good operational decisions remain necessary after the welcome screen appears.
A normal Tails session is intended to forget local activity at shutdown. Persistent Storage can preserve selected settings and files on the Tails USB when configured and unlocked, but it does not turn the device into a conventional permanent installation. Only supported features should persist, and sensitive data still needs a separate recovery plan.
Test the Tails OS download and complete a clean boot before creating persistence. Then restart, unlock the storage, and confirm that the intended features return while ordinary session data does not. Keep important persistent information backed up outside the boot drive.
The filename and version label are not enough. Start from tails.net, complete the verification method provided with the current release, and write only the verified local file.
If verification fails, delete the image and obtain a fresh copy. Do not use a third-party mirror, rename the failed file, or rely on a malware-scan badge as a substitute for release verification.
Before reusing an older image, compare it with the release currently offered by the Tails Project. A previously verified Tails OS download can remain internally unchanged while becoming outdated after security fixes or hardware updates. Record when the file was checked, review official release notes, and rebuild the USB when the supported update path or current security guidance requires it.
Keep only one clearly identified candidate image in the download folder. Browser-added suffixes, copied files, and similar version names make it easy to verify one file and write another. Select the exact verified Tails OS download in the image writer, then preserve the verification result only as operational evidence, not as a permanent guarantee for future releases.
A successful Tails OS download is only the first stage. Keep the release current, review security announcements, and retest after firmware or hardware changes.
These answers explain file choice and source safety. The linked guides cover the full steps.
Yes. Tails is free software. Use the official tails.net installation flow so you receive the current image and the matching verification instructions.
Most people creating a bootable USB should follow the official USB image instructions for their current operating system. The ISO is mainly for virtual machines, DVDs, and workflows that specifically require it.
Tails targets 64-bit x86-64 computers. Check the current official requirements and known hardware limitations before erasing a USB drive or relying on Tails for a trip.
Use a dedicated USB stick that meets the capacity listed in the current official installation guide. Capacity recommendations can change, and writing the image erases the selected drive.
An ISO can be used in a virtual machine, but a VM does not provide the same isolation and hardware behavior as booting Tails on a computer. Read the ISO guide before choosing that route.
No. This is an independent download and installation guide. Tails Project operates tails.net, which is the authoritative source for current downloads, documentation, and security announcements.
Follow the verification method provided by the official download page before writing the image. Verification helps detect an incomplete, corrupted, or unexpected file.