How Tails Forgets Everything the Amnesic Design Explained
Boot, work, shut down - and the computer behaves as if you were never there. That trick is the heart of Tails. Here is exactly how it works, and the fine print nobody should skip.
✍️ Technical Anshu🐧 Linux Privacy⏱️ 7 min read
🎥 Watch the full Tails OS review in the video - first boot, features and settings shown live
The word amnesic in Tails' full name - The Amnesic Incognito Live System - is a promise: the system forgets. But how does an operating system forget on purpose, and how far does that promise really go? This page explains the mechanism step by step, then lists the limits honestly, because trusting a privacy tool means knowing exactly where its protection ends.
One Tails session - where your data actually lives
Running programsRAM only
Downloads and editsRAM only
Internal hard diskNever written
At shutdownRAM is wiped, session ends
During a normal session, everything exists in memory alone. Nothing is committed to any disk unless you deliberately save it to Persistent Storage or an external encrypted drive.
1
Step One - The System Runs From RAM
A normal operating system lives on your hard disk and constantly writes to it: logs, caches, temporary files, swap. Tails inverts this. The whole system image sits on the USB stick, loads into the computer's RAM at boot, and runs from there. The internal disk is not mounted, not used, and not written to.
RAM has one property that makes this design possible: it is volatile. Cut the power and its contents vanish. Tails adds one more layer - on shutdown it actively overwrites the memory before powering off, so the session is erased rather than merely abandoned.
2
Step Two - Every Write Goes to a Temporary Layer
Programs expect to write files, so Tails gives them a writable layer that exists only in RAM. Your home folder, your downloads, your settings - all real while you work, all stored in that memory layer. This is why a file you save to the Desktop in Tails is simply not there tomorrow. It was never on a disk at all.
The one deliberate exception is Persistent Storage: an encrypted area on the USB stick that you may create if you want chosen things - documents, bookmarks, keys - to survive between sessions. Without it, there is no exception. With it, only what you put there survives.
3
What This Protects You From
Traces on a shared or borrowed computer. After a Tails session, the machine's owner finds no history, no files, no logs of your work on their disk - there is nothing to find, because nothing was written.
Persistent malware. A system that resets completely at every boot gives everyday infections no permanent home. Each session starts from the same clean, read-only image.
Your own mistakes. Forgot to clear history or delete a sensitive file? The design clears the entire session for you, every time.
4
The Real Limits - Say Them Plainly
Amnesia protects the local machine. It does not rewrite the rest of the world:
Network-side records exist. Your internet provider can see that Tor was used (though not what you did inside it), and a website you log into knows its own account was used. Amnesia erases your side of the story, not theirs.
The computer itself must be trustworthy. A machine with a hardware keylogger or a compromised firmware can record you before Tails ever starts. Tails cannot fix hostile hardware.
Anything you export leaves the bubble. A file you copy to an unencrypted stick, print, or send from a personal account is outside the design from that moment.
Forensic edge cases exist. The memory wipe is strong, but no software can make absolute promises against a well-funded lab examining a machine seized while still running. Tails' own documentation is honest about this, and so is this page.
5
Using the Design the Way It Was Meant
Three habits keep the promise intact. Shut down properly instead of just pulling the stick out, so the memory wipe runs. Keep sessions focused - do the sensitive work in Tails and everyday work in your everyday system, rather than mixing identities in one session. And decide before you boot whether this session needs Persistent Storage, because everything outside it is designed to disappear.
Understood this way, amnesia is not a parlour trick. It is a disciplined default: nothing survives unless you consciously choose that it should.
🔴 Do not run Tails inside a virtual machine on an untrusted host system. The host can see and record everything the virtual machine does, which quietly cancels the amnesic design. Tails is meant to boot directly on the hardware, as shown in the video.
🎬 Watch the Complete Video for Full Knowledge and Installation
See the amnesic system working live - boot, a full session, and the clean shutdown - in the complete review video.
If Tails forgets everything, how do I save my work?
Save it into the encrypted Persistent Storage on the USB stick, or onto another encrypted external drive. Anything saved anywhere else inside Tails disappears at shutdown - that is the design working as intended.
Can someone recover my Tails session from the computer afterwards?
From the computer's disk, no - Tails never wrote there. From RAM after a proper shutdown, the memory wipe makes recovery impractical. A machine seized while still running and unlocked is a different, much stronger attack, which no live system can fully promise against.
Does the amnesic design slow Tails down?
Running from RAM is actually fast. The slowness people notice in Tails comes from the Tor network routing, not from the amnesic design.
This guide is based on the Technical Anshu video Tails OS Review Is This the Most Private Linux OS • Stuck on any step? Ask in the video comments - you will get an answer there 🙏