TrueNAS CORE vs TrueNAS SCALE: Which to Choose?
TrueNAS CORE and TrueNAS SCALE are both free, open-source NAS platforms from iXsystems built around ZFS. They share the same web interface, the same storage architecture, and the same goal: making enterprise-grade storage accessible. But they run on different operating systems, and that difference shapes everything else.
TrueNAS CORE runs on FreeBSD. TrueNAS SCALE runs on Debian Linux. This is not just a trivia point -- it determines your application ecosystem, virtualization options, hardware compatibility, and long-term support trajectory.
This guide compares every dimension that matters: base OS, ZFS implementation, application support, virtualization, performance, hardware compatibility, and when to choose each.
TL;DR -- Quick Verdict
Choose TrueNAS CORE if you want a pure, battle-tested FreeBSD-based NAS focused exclusively on storage and file serving. CORE has a decade of production history, jails for lightweight application hosting, and the most mature ZFS implementation available.
Choose TrueNAS SCALE if you need Docker containers, Kubernetes apps, Linux-native applications, or broader hardware support. SCALE is the actively developed platform with the larger ecosystem and iXsystems' primary focus.
Important context: iXsystems has shifted active development to SCALE. CORE continues to receive security updates but is effectively in maintenance mode. For new deployments in 2026, SCALE is the default recommendation unless you have specific reasons to prefer FreeBSD.
Base Operating System
TrueNAS CORE: FreeBSD
CORE runs on FreeBSD, which means:
- ZFS is a first-class citizen, deeply integrated into the kernel
- Jails provide lightweight OS-level virtualization
- The network stack is mature and highly tunable (PF firewall, CARP, LAGG)
- bhyve provides Type 2 virtualization for VMs
- Hardware support is narrower than Linux, especially for newer consumer hardware
FreeBSD's strength is coherence. The kernel, userland, and ZFS are developed and tested as one unit. There are no compatibility layers or backported kernel modules.
TrueNAS SCALE: Debian Linux
SCALE runs on Debian Linux, which means:
- ZFS runs as a kernel module (OpenZFS, same codebase as FreeBSD but different integration)
- Docker and Kubernetes are native
- Broader hardware support (more drivers, more peripherals)
- Larger software ecosystem (APT packages, Linux containers)
- systemd-based init
Linux's strength is ecosystem. If an application exists as a Docker container or Linux package, it runs on SCALE.
ZFS Implementation
Both platforms use OpenZFS, but the integration differs.
ZFS on CORE (FreeBSD)
- ZFS is compiled into the FreeBSD kernel
- FreeBSD's VM subsystem is tuned for ZFS (ARC, L2ARC, SLOG integration)
- ZFS has been in FreeBSD since 2007 -- nearly two decades of production hardening
- Features like boot environments (BE) are deeply integrated
- ZFS encryption, send/receive, and scrub are stable and well-tested
ZFS on SCALE (Linux)
- OpenZFS runs as a kernel module on Linux
- Must be rebuilt or adapted for each kernel update
- Equivalent feature set (same OpenZFS codebase)
- Linux-specific optimizations exist (e.g., integration with Linux block layer)
- Occasional compatibility issues with kernel updates (resolved quickly by the OpenZFS team)
Performance Comparison
For pure storage workloads (NFS, SMB, iSCSI), performance is nearly identical between CORE and SCALE. Both use the same ZFS algorithms and data structures.
| Workload | CORE (FreeBSD) | SCALE (Linux) |
|---|---|---|
| Sequential read/write | Equivalent | Equivalent |
| Random IOPS | Equivalent | Equivalent |
| NFS serving | Slightly better (mature nfsd) | Good |
| SMB serving | Good (Samba) | Good (Samba) |
| iSCSI | Native ctld (excellent) | Linux LIO (excellent) |
| ARC efficiency | Excellent | Excellent |
| ZFS send/receive | Excellent | Excellent |
The differences are marginal. Do not choose between CORE and SCALE based on raw ZFS performance.
Application Ecosystem
This is where the platforms diverge most significantly.
TrueNAS CORE: Jails and Plugins
CORE uses FreeBSD jails for application hosting:
sh# Creating a jail from the TrueNAS CLI iocage create -n myapp -r 13.2-RELEASE iocage start myapp iocage console myapp
The plugin system installs pre-configured jails for common applications:
- Plex Media Server
- Nextcloud
- Transmission
- Syncthing
- GitLab (community)
- Home Assistant (limited)
Strengths:
- Jails are lightweight (no hypervisor overhead)
- Native FreeBSD performance
- ZFS integration for jail storage
Limitations:
- Smaller application ecosystem
- No Docker support
- Many modern self-hosted apps are Linux-only
- Plugin development has slowed since SCALE became the focus
TrueNAS SCALE: Docker and Kubernetes
SCALE uses Docker and a Kubernetes-based app system:
Custom Apps (Docker Compose):
SCALE allows deploying any Docker Compose stack directly from the web UI. If it runs in Docker, it runs on SCALE.
TrueNAS Apps Catalog:
A curated catalog of pre-configured applications:
- Plex, Jellyfin, Emby
- Nextcloud
- Home Assistant
- Vaultwarden
- Immich (photo management)
- Paperless-ngx
- *Arr stack (Sonarr, Radarr, Prowlarr, etc.)
- Hundreds more
TrueCharts:
A community-maintained catalog with over 500 additional applications using Helm charts.
Strengths:
- Massive application ecosystem (anything on Docker Hub)
- Modern self-hosted applications work out of the box
- Active development of the apps platform
- Custom Docker Compose support
Limitations:
- Kubernetes adds complexity under the hood
- Container storage management is less intuitive than jail+ZFS
- Resource overhead from the container runtime
Verdict on Applications
If you want to run self-hosted applications beyond basic file serving, SCALE wins decisively. The Docker ecosystem is orders of magnitude larger than FreeBSD's jail plugin ecosystem.
Virtualization
CORE: bhyve
CORE provides bhyve-based VMs through the web interface:
- Supports Windows, Linux, and BSD guests
- VNC console access
- PCI passthrough (GPU, USB, NIC)
- Limited but functional
SCALE: KVM/QEMU
SCALE provides KVM-based VMs:
- Mature Linux virtualization stack
- Better hardware passthrough support
- SPICE and VNC console
- Broader guest OS support
- Better GPU passthrough (important for Plex transcoding in a VM)
SCALE has the edge in virtualization due to KVM's maturity and broader driver support for passthrough hardware.
Hardware Compatibility
CORE (FreeBSD)
FreeBSD hardware support is more selective:
- NICs: Intel (excellent), Broadcom (good), Chelsio (excellent). Some Realtek issues.
- HBAs: LSI/Broadcom SAS controllers (excellent). Required for proper ZFS direct disk access.
- SATA: Generally good on major chipsets
- NVMe: Good support for most controllers
- USB: Adequate but less complete than Linux
- GPU: Basic, limited passthrough options
SCALE (Linux)
Linux hardware support is broader:
- NICs: Nearly everything works, including consumer-grade hardware
- HBAs: Same LSI/Broadcom support, plus additional Linux-only controllers
- SATA: Broader chipset support
- NVMe: Broader support including newer controllers
- USB: Better, including USB Wi-Fi and Bluetooth
- GPU: NVIDIA and AMD passthrough works well
If you are building with consumer or recent hardware, SCALE is safer. If you are using enterprise storage hardware (LSI HBAs, Intel NICs, Supermicro boards), both work equally well.
Networking
CORE (FreeBSD)
- PF firewall (powerful, clean syntax)
- LAGG (link aggregation) with multiple protocols
- CARP (failover)
- Mature NFS server (kernel nfsd)
- VNET for jail networking
- Excellent network stack tuning options
SCALE (Linux)
- nftables / iptables firewall
- Bonding (link aggregation)
- Standard Linux networking stack
- NFS via knfsd
- Docker networking (bridge, macvlan, etc.)
Both are capable. CORE's FreeBSD network stack has a reputation for better performance under extreme loads (high connection counts, heavy NAT), but for typical NAS workloads, the difference is academic.
Clustering and Scale-Out
CORE
No built-in clustering. Single-node only. For HA, iXsystems offers TrueNAS Enterprise (commercial).
SCALE
SCALE includes a clustering feature (TrueCommand integration) for managing multiple nodes:
- Centralized management of multiple SCALE nodes
- Gluster support for distributed storage (experimental)
- Better multi-node story for larger deployments
If you need to manage multiple NAS nodes, SCALE is the better platform.
Migration: CORE to SCALE
iXsystems provides a migration path from CORE to SCALE:
What Migrates
- ZFS pool configuration and data (import works natively)
- Network configuration
- SMB/NFS share configuration
- User accounts
- System settings
What Does Not Migrate
- Jails (must be rebuilt as Docker containers)
- bhyve VMs (must be recreated as KVM VMs)
- Plugins (must be replaced with SCALE apps)
- Custom FreeBSD-specific configurations
Migration Steps
- Back up the CORE configuration file
- Document all jail configurations and installed plugins
- Install SCALE on the boot drive (or a new drive)
- Import ZFS pools
- Recreate shares, users, and network settings
- Deploy Docker-based replacements for former jails
The data migration is straightforward because ZFS pools are portable between FreeBSD and Linux. The application migration requires more work.
sh# On SCALE after install, import existing pools # Via CLI: midclt call pool.import_find midclt call pool.import_pool '{"guid": "your-pool-guid", "name": "tank"}'
Long-Term Support and Development
CORE
- Security updates continue
- No new features planned
- iXsystems has stated SCALE is the future
- Community contributions still accepted
- FreeBSD base system updates continue
SCALE
- Active development with regular releases
- New features added regularly (improved apps, clustering, etc.)
- iXsystems' primary engineering focus
- Growing community
- Regular point releases with bug fixes
This is the most important consideration for new deployments. CORE is stable but stagnant. SCALE is where the future lies.
Decision Matrix
| Requirement | CORE | SCALE | Winner |
|---|---|---|---|
| Pure file server (NFS/SMB) | Excellent | Excellent | Tie |
| Docker applications | No | Yes | SCALE |
| Self-hosted apps ecosystem | Limited | Extensive | SCALE |
| ZFS maturity | 18+ years | 10+ years | CORE (slight) |
| Hardware compatibility | Narrow | Broad | SCALE |
| FreeBSD preference | Yes | No | CORE |
| Active development | Maintenance | Active | SCALE |
| VMs and passthrough | Basic | Good | SCALE |
| Clustering | No | Yes | SCALE |
| Network performance edge cases | Slightly better | Good | CORE (slight) |
| Community size (2026) | Shrinking | Growing | SCALE |
FAQ
Is TrueNAS CORE being discontinued?
Not officially. iXsystems continues to provide security updates. However, no new features are being developed for CORE. It is in maintenance mode. For new deployments, SCALE is recommended.
Can I run Docker on TrueNAS CORE?
No. Docker requires Linux kernel features that FreeBSD does not provide. On CORE, use jails for application isolation.
Will my ZFS pool survive a migration from CORE to SCALE?
Yes. ZFS pools created on FreeBSD (CORE) can be imported on Linux (SCALE) and vice versa. The on-disk format is the same. Your data is safe.
Is ZFS on Linux (SCALE) as reliable as ZFS on FreeBSD (CORE)?
In 2026, yes. OpenZFS on Linux has matured significantly. Major enterprises run ZFS on Linux in production. The early concerns about Linux ZFS stability are no longer warranted.
Which is better for Plex?
SCALE. You can run Plex as a Docker container with hardware transcoding. On CORE, Plex runs in a jail with more limited hardware transcoding support (especially for Intel Quick Sync).
Can I run both CORE and SCALE on the same hardware?
Not simultaneously. You can install one and later migrate to the other. Some users keep CORE on one boot drive and SCALE on another, importing the same data pools depending on which they boot.
How much RAM do I need for TrueNAS?
Both platforms recommend 8 GB minimum, with 1 GB per TB of storage for optimal ZFS ARC performance. 16-32 GB is the sweet spot for most home and small business deployments. ECC RAM is recommended but not required.