Unraid vs TrueNAS

Open the cupboard where you keep spare drives. If it contains a 4 TB, an 8 TB, a 12 TB and a 14 TB pulled from various machines over six years, you want Unraid. If it contains four identical 16 TB drives bought together, you want TrueNAS. That is genuinely most of the decision, and everything below is the detail behind it.

The rest of the marketing, both directions, is noise. Both run Docker containers. Both run VMs. Both have a web UI a normal person can use. Both are x86-64 only. Since Unraid 7.0 both can even do ZFS. What they do not share is the storage model, and the storage model is the thing you cannot change later without buying a second set of drives.

In the table below, look first at license and ram_idle_mb. Unraid is proprietary and paid; TrueNAS Community Edition is free with an LGPL-3.0 middleware. The RAM figures are not observed footprints: TrueNAS's 8192 is its documented minimum, while Unraid publishes no hard floor at all and the 2048 is an estimate for a working server. That asymmetry is real and it favors Unraid on old hardware.

The parity array: what it actually protects#

Unraid's array is not RAID. Data is not striped. Each data disk holds a complete, independently mountable filesystem, and one or two dedicated parity disks hold the XOR of every data disk.

The consequences are specific and they are why people pay for it:

• You can add one drive at a time, of any size up to the parity disk's size, without rebuilding anything or matching what is already there.
• Reads touch one disk. A movie plays from disk 4 while disks 1, 2, 3, 5 and 6 stay spun down. On a twelve-bay media box that is a genuine 40 to 60 watt difference against a ZFS pool that spins everything for any read. What a home server costs to run turns that into an annual number.
• Failure beyond parity is survivable. Lose three disks with dual parity and you lose those three disks' contents. The other nine still mount. Put any surviving drive in a Windows machine with an XFS reader and the files are there. In ZFS, losing a third disk in a RAIDZ2 vdev takes the entire pool, including every other vdev in it.

Now what it does not protect, which the Unraid marketing page will not tell you.

Parity is XOR, not a checksum. It can rebuild a disk that has died in a way the controller reports. It cannot tell you that disk 4 quietly returned a wrong byte. Worse, the default monthly parity check is a correcting check: when it finds a mismatch it assumes the data disks are right and rewrites parity to match them. If the mismatch came from silent corruption on a data disk, the check just made the corruption permanent and reported success.

Unraid 7.0 added ZFS and btrfs as filesystem options for individual array disks, which gets you checksums so at least you are told when a file is bad. But a single-disk ZFS filesystem has no redundancy to heal from, so you learn that the file is corrupt and then restore it from backup. That is better than silence. It is not what ZFS gives you in a real pool.

The other hard constraint: parity must be at least as large as your largest data disk. If parity is a 12 TB drive you cannot add a 20 TB data disk without first replacing parity and rebuilding it, which is a multi-day operation on a full array during which you have no redundancy at all. Buy the biggest drive you own as parity first, not last.

ZFS integrity: what you buy and what it costs#

TrueNAS gives you the thing Unraid structurally cannot. Every block carries a checksum. A scrub reads everything, verifies it, and where a vdev has redundancy it repairs the bad copy from a good one and tells you which file was affected. Snapshots are instant and near-free. Replication sends the differences to a second box over SSH.

Those four properties together are why TrueNAS is the right answer for anything irreplaceable. Photos, documents, the family archive: you want the filesystem that notices rot, not the one that averages it into parity.

The price is rigidity. A vdev uses the smallest member's capacity across every disk in it. Adding capacity historically meant adding a whole new vdev, which meant buying drives in sets. RAIDZ expansion, available in recent TrueNAS releases, softens this: you can add a disk to an existing RAIDZ vdev. Read the fine print, though, because it is the thing people get wrong. Existing data keeps the stripe width it was written with, so the usable capacity you gain immediately is less than the arithmetic suggests, and you only realize the full benefit after the data has been rewritten. Plan capacity as if expansion did not exist and treat it as a bonus.

Two more TrueNAS-specific costs. RAM: 8 GB documented minimum, roughly 1 GB more per drive past eight, plus a dedicated 16 GB or larger boot device. And version churn: the apps platform has been rebuilt twice in three years (Kubernetes, then Docker in 24.10 Electric Eel), and 25.10 "Goldeye" removed the built-in certificate authority, removed SMART test scheduling from the UI, and dropped NVIDIA GPUs older than Turing. If a P400 is doing your transcoding, that upgrade will silently take it away. Proxmox vs TrueNAS goes deeper on the current naming, since the SCALE and CORE lines merged in 25.04.

The Unraid licence, exactly#

The 2024 change replaced the old Basic, Plus and Pro lifetime keys. Anything you read that mentions those tiers predates it.

The part people misread: the update extension is optional. Let it lapse and you keep running the version you have forever, you just do not get new major releases. Also note "storage devices" counts cache pool SSDs and NVMe drives, not just array disks, so a Starter licence with four data disks, one parity and an NVMe cache is already at five of six.

Two hardware details worth knowing before you buy. Unraid still requires a USB flash drive with a unique GUID to start a new server, even though 7.3 added internal SSD and NVMe boot: the documented flow is boot from USB, then convert through the onboarding wizard. And 7.3's TPM-based licensing means your key can now survive a boot device change, which was previously a support ticket. Current stable is 7.3.2 with 7.4 in beta.

The other paid-product tax is plugins. Unraid 7.2 auto-uninstalls plugins incompatible with the new responsive WebGUI, including Theme Engine, Dark Theme, Dynamix Date Time and Flash Remount. Upgrade every plugin, especially Unraid Connect and the NVIDIA driver plugin, before you upgrade the OS, not after.

Neither of these is a backup#

Both products are sold with an implication that they keep your data safe, and both leave the same gap. Parity survives a disk failure. Snapshots survive a mistake you notice quickly. Neither survives a deleted share, a ransomware run through an SMB mount, a power supply that takes several drives with it, or a house fire.

Unraid's array has no snapshot of itself at all, so an accidental rm -rf over SMB is simply gone. TrueNAS snapshots are excellent and are still on the same pool as the data. Send them somewhere else: replication to a second TrueNAS, or restic or BorgBackup to an off-site repository. Backup planner will size it, Backups that actually restore covers the restore rehearsal, and The backup blind spot has the numbers on how often people skip it.

Track disk health on either platform with Scrutiny, especially on Unraid where 25.10-style UI SMART scheduling was never the strong point and where a failing disk is discovered during a rebuild if you are not watching.

Verdict by situation#

What to do next#

Count your drives and their sizes before you read another comparison. If the answer is "mixed", the 49 USD Starter licence and a 30-day trial cost you almost nothing to prove out; check the device count against that six-device limit first, because a cache SSD and a parity disk both count.

If the answer is "matched", install TrueNAS Community Edition on a spare 16 GB SSD, build the pool, and spend the money you did not spend on a licence on a second machine to replicate to. ZFS, btrfs, mdadm or one disk covers the vdev layout decision, and Mini PC vs NAS vs used enterprise covers whether the box should be a purpose-built NAS chassis at all.