Our Proxmox vs TrueNAS vs Unraid comparison recommends TrueNAS for anyone whose priority is safe, ZFS-backed file storage — but "TrueNAS" is actually two separate products with a shared name and a shared storage engine underneath. A lot of older forum posts and YouTube videos still recommend whichever one was better a few years ago, which is exactly the kind of outdated advice that trips up beginners searching this today. Here's what actually differs, and which one we'd install if we were starting fresh right now.
They share ZFS, but not much else under the hood
Both products are built around OpenZFS, the same battle-tested filesystem responsible for TrueNAS's reputation: checksummed data (so silent corruption gets caught, not silently written to disk), snapshots, and flexible storage pools. That shared foundation is where the similarity mostly ends — the two products are built on entirely different base operating systems:
- TrueNAS CORE is built on FreeBSD. It uses FreeBSD "jails" for lightweight app isolation and bhyve for virtual machines. This is the older of the two product lines, and for years it was considered the more mature, rock-solid option specifically for pure file storage.
- TrueNAS SCALE is built on Debian Linux. It runs apps as Docker containers (managed through TrueNAS's own app catalog) and can scale out across multiple nodes for clustered storage — hence the name. It's the newer product, first released as a stable version in 2022.
The part that actually matters for a beginner deciding today
iXsystems, the company behind TrueNAS, has been putting essentially all of its new feature development into SCALE for several years now. CORE still exists, still works, and still gets security and bug fixes, but it is functionally in a maintenance phase rather than an actively growing product — new apps, new integrations, and new features are landing on SCALE first, and in many cases, only on SCALE. If you search "TrueNAS" tutorials, guides, and Docker Compose examples from the last year or two, the overwhelming majority now assume SCALE, not CORE.
This is a meaningful shift from the advice that was correct a few years ago, when CORE's FreeBSD foundation had a real edge in stability and jail-based isolation was considered lighter-weight than Docker. That gap has narrowed significantly, and it keeps narrowing in SCALE's direction as development effort continues to concentrate there.
Side-by-side comparison
| TrueNAS SCALE | TrueNAS CORE | |
|---|---|---|
| Base OS | Debian Linux | FreeBSD |
| App format | Docker containers, built-in catalog | FreeBSD jails (legacy "plugins" mostly discontinued) |
| Virtual machines | KVM | bhyve |
| Active development | Primary focus, ongoing | Maintenance mode — security/bug fixes |
| Clustering / multi-node storage | Yes (the "scale-out" feature) | No |
| Best for | Everyone starting today, especially anyone who also wants to self-host apps | Existing CORE installs, or a narrow preference for FreeBSD/jails specifically |
| Cost | Free | Free |
What we'd actually install today
SCALE, for almost everyone reading this. Unless you're maintaining an existing CORE server and have a specific reason to stay (a working jail setup you don't want to rebuild, for instance), a new install in 2026 should be SCALE. You get the same ZFS data protection at the core of TrueNAS's reputation, plus a Docker-based app ecosystem that matches what the rest of the self-hosting world — including guides on this site — is written around.
The one case where CORE is still a defensible pick is a machine dedicated purely to file storage with no interest in running apps or VMs on it at all, where FreeBSD's smaller footprint and jail model are a genuine, if narrow, fit. Even then, most people are better served running SCALE and simply not installing any apps, so you keep the option open later without having to migrate a ZFS pool between fundamentally different operating systems if your needs change.
Migrating an existing CORE pool to SCALE
Because both products use OpenZFS, a storage pool created on CORE can generally be imported on SCALE — export the pool cleanly from CORE first (Storage > Pools > Export/Disconnect), physically move or keep the same drives connected, then import the pool from SCALE's storage screen. Back up anything critical before attempting this regardless, and check the official TrueNAS documentation for the specific ZFS feature flags supported by the SCALE version you're moving to, since very old CORE pools occasionally used ZFS features that need updating during the move.
Where TrueNAS fits alongside Proxmox
A common and genuinely good setup is running TrueNAS SCALE as a virtual machine inside Proxmox, with physical storage drives passed through directly to the VM. This gives you Proxmox's flexibility for running other services (Home Assistant, a media server, a Portainer-managed Docker host) alongside a dedicated, ZFS-protected storage layer, rather than choosing one platform to do everything. If you're deciding between running TrueNAS bare-metal versus inside Proxmox, bare metal is simpler for a single-purpose NAS, while running it as a VM makes more sense once you already know you want Proxmox for everything else.