The official TrueNAS SCALE requirements are short: any 64-bit x86 Intel or AMD CPU, 8 GB of RAM, an SSD boot device of 16 GB (20 GB in the TrueNAS 27 docs) and two identically sized drives for one pool. That gets you a box that boots and serves files. For one you’ll live with for five years, plan on 16 GB of RAM, a cheap 120 GB-plus boot SSD and CMR disks.
TrueNAS Community Edition is the same Linux product under its new name, with the same hardware bar; SCALE vs CORE vs Community Edition covers the rename.
Who this is for, and who should skip
This is for someone holding a spare x86 desktop, an N100 box or an old NAS and wondering whether it clears the bar. Install and a first share take an afternoon. Getting permissions right takes longer than anyone admits.
Skip TrueNAS if your hardware is ARM (there is no Raspberry Pi build), if you have exactly one data disk, or if you want to grow a pool one mismatched drive at a time. Unraid is friendlier to junk-drawer drives, and the SCALE vs Unraid vs OMV comparison lays out that trade. If all you need is an offsite home for phone photos, a cloud subscription is fine and costs less than your weekends.
What are the official TrueNAS SCALE minimum requirements?
iXsystems lists four lines: an x86_64 Intel or AMD processor, 8 GB of memory, an SSD boot device and two identically sized drives for a single pool. The only number that moved between releases is the boot device, from 16 GB in the 25.10 hardware guide to 20 GB in the TrueNAS 27 hardware guide.
| Requirement | 25.10 (Goldeye) guide | TrueNAS 27 guide |
|---|---|---|
| Processor | 2-core Intel 64-bit or AMD x86_64 | Any x86_64 compatible (Intel or AMD) |
| Memory | 8 GB | 8 GB |
| Boot device | 16 GB SSD | 20 GB SSD |
| Storage | Two identically sized devices for one pool | Unchanged |
The 25.10 docs don’t agree with themselves. The guide’s table says 16 GB, its own boot-device paragraph calls 8 GB the recommended size, and the 25.10 install page asks for a 20 GB boot device. Treat 20 GB as the floor on any version. It’s moot in practice: any SSD you would actually buy clears it several times over.
What does each workload actually need?
File sharing runs on the official 8 GB. A few apps want 16 to 32 GB and an SSD pool for app data. VMs want 32 GB or more and a CPU from Ivy Bridge onward. iSCSI for VM storage needs at least 16 GB. The hardware guide prices RAM per feature, so the table mixes its official figures (marked) with editorial targets.
| Workload | CPU | RAM | Storage notes |
|---|---|---|---|
| SMB/NFS file sharing, up to 8 drives | Any x86_64, 2+ cores | 8 GB (official); 16 GB comfortable | Small SSD boot, HDD pool |
| Plus a few apps (Jellyfin, Immich) | 4 cores; Intel iGPU for transcodes | 16-32 GB | SSD pool for apps |
| Plus virtual machines | Ivy Bridge or newer; VT-d/AMD-Vi for passthrough | 32 GB+, plus guest RAM | SSD pool for VM disks |
| iSCSI block storage for VMs | 4+ cores | 16 GB minimum (official) | Mirrors over RAIDZ |
| Deduplication | Fast cores | Add 5 GB per TB (official) | Rarely worth it at home |
CPU: x86_64 only, and the features that matter
Any 64-bit Intel or AMD chip clears the bar, and nothing else does, so Raspberry Pis and Apple Silicon Macs are out. Features matter more than clock speed. The hardware guide calls out three:
- AES-NI for faster dataset and network encryption.
- Intel Ivy Bridge or later for virtual machines, with virtualization enabled in firmware.
- VT-d or AMD-Vi on both CPU and motherboard to pass a PCIe device, like an HBA or GPU, through to a VM.
Transcoding is where raw muscle shows. A Jellyfin or Plex app transcoding on the CPU will flatten a small chip, while an Intel iGPU with Quick Sync does the same job in hardware. Specific picks are in best CPU for TrueNAS SCALE.
RAM: 8 GB boots, 16 GB is the real floor
The official 8 GB covers basic operation with up to eight drives: no apps, no VMs, no extras. The guide’s official add-ons:
- 1 GB for each drive past eight.
- 2 GB for directory services (the Winbind cache).
- About 1 GB per 50 GB of L2ARC.
- 5 GB per TB of deduplicated storage.
- At least 16 GB when serving iSCSI for VM storage.
- Whatever your apps and VMs need on top.
ZFS uses spare memory as ARC read cache, so headroom isn’t wasted. That’s why 16 GB is the sensible floor once two or three apps are running, and 32 GB is where you stop thinking about it. Whatever you buy, run a memory test first; the guide notes RAM failures usually show up in the first three months. The full math is in TrueNAS RAM requirements by workload.
Boot device: SSD, not a USB stick
Use a SATA, SAS or NVMe SSD. TrueNAS will boot from a USB stick, but the docs discourage it because flash quality varies widely and newer releases write more to the boot pool. The 25.10 version notes repeat that USB boot devices are not recommended, and the TrueNAS 27 guide puts SATA DOMs in the same bucket.
The installer erases the drive you pick and uses it for the boot pool, so a 2 TB NVMe as the boot disk is mostly wasted space. On a machine with a single M.2 slot, that slot is usually better spent on an apps pool. A mirrored boot pair is optional. A downloaded config backup matters more, because a fresh install plus that file gets the box back.
Drives and controllers: the requirements not on the list
The official storage line is two identically sized drives. The unwritten rules matter more:
- CMR, not SMR. The guide says drive-managed and host-aware SMR drives “function poorly” with TrueNAS, and host-managed SMR is unsupported.
- No USB disks in the pool. The docs say to avoid USB-attached disks for primary storage, partly because USB bridges can misreport serial numbers. Basic backup duty is fine.
- Disks presented directly to ZFS. Onboard SATA or a Broadcom (LSI) HBA in IT mode. No hardware RAID, and switch off motherboard RAID.
Two disks make a mirror. Four or more open up RAIDZ, and RAIDZ1 vs RAIDZ2 covers the resilver risk. Model picks are in best hard drives for TrueNAS.
Apps and GPU requirements
Apps need a pool before anything else. The first time you open Apps, TrueNAS asks for one, and the TrueNAS Apps documentation recommends SSD storage for it. On a two-HDD box, that means living with slow app databases or adding an SSD mirror just for apps.
GPUs are where old hardware bites. TrueNAS 25.10 moved to NVIDIA’s open kernel drivers, which support Turing and newer (GTX 16-series and RTX). The version notes list Pascal, Maxwell and Volta as no longer supported, so the GTX 1060 or Quadro P400 in your parts bin won’t transcode on 25.10. NVIDIA drivers have also been a manual install since 24.10, under Apps, Configuration, Settings. Intel iGPUs skip all of this. Docker on TrueNAS SCALE explains the app model itself.
Can an N100 mini-PC run TrueNAS SCALE?
Yes. An N100 clears every official requirement, and its Quick Sync iGPU handles hardware transcoding, but most mini-PCs built on it fail the storage requirement in practice. Intel’s N100 spec sheet lists 4 cores, a 6 W TDP, AES-NI, VT-x and VT-d. Compute is not the problem. Memory and drive slots are.
Intel caps the chip at 16 GB on a single memory channel, with no ECC. That’s enough for a file server plus a handful of apps, and tight once VMs arrive. Then count the drive slots on your model: one for boot and two for the pool, and the docs say to keep USB enclosures out of primary storage. With nine PCIe Gen 3 lanes in total, there’s little room to hang an HBA off it either.
The setups that work:
- An N100 NAS motherboard with onboard SATA, in a real case. A legitimate low-power TrueNAS box; see the budget NAS build and the motherboard roundup.
- The mini-PC as the apps box, the NAS you already own as storage. Run compose on the mini-PC and mount shares over NFS. If that NAS is a working Synology, this is far less work than replacing it.
- TrueNAS on the mini-PC with a two-SSD mirror, if it has the slots. Fine for documents and app data, not for a media library.
The requirement nobody lists: a second copy
No hardware guide lists backups, and they’re what bites at month nine. A redundant pool survives a dead disk, not a deleted dataset, a botched upgrade or a house fire, and snapshots die with the pool they live on. Budget for a second target: another ZFS box receiving replication, or a cloud bucket through a Cloud Sync task for the irreplaceable stuff. Then drill it. Once a quarter, restore one file and one whole dataset from the backup target. The snapshot and replication strategy covers schedules.
Which TrueNAS version should you install?
Install 25.10.7, the release the software status page recommends for general users; it shipped on 2 September 2026. TrueNAS 27.0.0-RC.1 arrived on 6 October 2026 for early adopters, and iXsystems says 27.0 lands in early December 2026, built on Linux 6.18 and OpenZFS 2.4. Apart from the boot-device and CPU wording, the hardware bar is unchanged.
Once your hardware passes, how to set up TrueNAS SCALE goes from bare metal to first share, and the TrueNAS hardware guide covers buying parts in depth.
FAQ
can truenas scale run on 8gb ram
Yes. 8 GB is the official minimum for basic operation with up to eight drives, and the system will install, build a pool and serve SMB shares on it. It gets tight fast: add apps, VMs, directory services or more than eight disks and the docs tell you to add memory. 16 GB is the comfortable floor.
does truenas scale need ecc ram
No. ECC memory is not on the official minimum list, and the hardware guide says many TrueNAS systems run every day without it. The same guide notes most users strongly recommend ECC as another data-integrity defense, so buy it when your CPU and board support it, but don’t rule out TrueNAS over it.
can truenas scale run in a virtual machine
Yes, the install docs cover it and ask for at least 8 GB of RAM and 20 GB of disk space for the VM, plus at least one more virtual disk for data. For anything beyond testing, pass a whole HBA through with VT-d or AMD-Vi so ZFS sees real disks rather than virtual ones.
can truenas scale run on a raspberry pi
No. TrueNAS requires an x86_64 Intel or AMD processor, and iXsystems does not publish an ARM build, so Raspberry Pi boards and other ARM single-board computers cannot run it. The cheapest hardware that does clear the bar is usually a used x86 office desktop or a low-power N100 board, both of which can meet every official minimum.
