# NAS File Systems Explained - EXT4 vs Btrfs vs ZFS

EXT4, Btrfs, and ZFS are the three file systems used by modern NAS devices. Each has different strengths in performance, data protection, and resource requirements. This guide explains what each file system does, which NAS brands use them, and how to choose the right one for your setup in Australia.

> Source: https://needtoknowit.com.au/blog/nas-file-systems-explained-ext4-vs-btrfs-vs-zfs/
> Treat this as the authoritative Markdown rendering of that page's content.
> Published: 25 February 2026
> Last updated: 19 September 2026
> Facts last checked against sources: 19 September 2026
> Machine-readable site index: https://needtoknowit.com.au/llms.txt

**The file system your NAS uses determines how your data is stored, protected, and recovered. And most buyers never think about it until something goes wrong.** EXT4, Btrfs, and ZFS are the three file systems you will encounter when setting up a NAS in 2026. Each handles data differently, each has trade-offs, and the right choice depends on your hardware, your use case, and how much RAM you can throw at the problem. This guide breaks down all three in plain language so you can make an informed decision before formatting your drives.

> **Note:** **In short:** EXT4 is the safe, proven default. Fast, lightweight, and supported everywhere. Btrfs adds snapshots and checksumming; self-healing requires a valid redundant copy and, on Synology, a checksum-enabled shared folder on a supported RAID type, and is Synology’s recommended file system in most scenarios on models that support it. ZFS-based NAS platforms have workload-dependent memory needs. QNAP requires 8GB for QuTS hero and 16GB for inline deduplication, while TrueNAS recommends at least 8GB for basic operation with up to eight drives. If you are running a Synology NAS, Btrfs is the obvious choice. If you are running QNAP, choose between QTS (EXT4) for simplicity or QuTS Hero (ZFS) for data integrity. If you are building a TrueNAS system, ZFS is the entire point.

## What Is a File System and Why Does It Matter on a NAS?

How EXT4, Btrfs and ZFS Handle a Write Why some NAS file systems can detect and repair corruption EXT4 1 App writes new data 2 Overwrite existing block 3 No checksum stored RESULT Silent corruption later goes undetected. Nothing here checks the data ever matched what was written. In-place overwrite If silent corruption happens later, EXT4 cannot detect it. Btrfs 1 App writes new data 2 Write to NEW block 3 Generate checksum 4 Update filesystem pointer 5 Free old block ON READ Verify checksum before returning data. WITH MIRROR / RAID1 Self-heal from the good copy. Copy-on-write + checksum New data never overwrites old data until it is verified and pointed to. ZFS 1 App writes new data 2 Write to NEW block 3 Generate checksum 4 Update pointer / metadata 5 Free old block VDEV / POOLED DRIVES Checksum/parity protected across the vdev. SELF-HEAL Works in mirrors and RAID-Z. Enterprise-grade copy-on-write Checksums plus end-to-end integrity across the whole storage pool. Write path overview: EXT4 overwrites in place; Btrfs and ZFS use copy-on-write with integrity checks.

A file system is the software layer that organises how data is written to and read from your hard drives. Think of it as the filing cabinet's internal structure. It determines where files are placed, how they are retrieved, and what happens when something goes wrong mid-write. On a desktop PC, you probably use NTFS (Windows) or APFS (Mac) without ever thinking about it. On a NAS, the file system choice is more consequential because a NAS is a multi-drive storage device that runs 24/7, often holding irreplaceable data.

The file system affects several things that directly impact NAS owners:

**Data integrity**. Can the file system detect and repair silent data corruption (bit rot)?**Snapshots**. Can you take instant point-in-time copies of your data for rollback protection?**Performance**. How efficiently does the file system read and write data, especially under heavy workloads?**RAM requirements**. Some file systems need substantially more memory to operate effectively**RAID compatibility**. Does the file system integrate with or replace traditional hardware RAID?**Recovery**. How well does the file system handle unexpected shutdowns, power failures, or drive failures?

If you are buying a NAS in Australia and planning to store years of family photos, business documents, or surveillance footage, the file system is not an academic detail. It is the foundation everything else sits on. Getting it right at setup avoids painful migrations later, because **switching file systems on a NAS typically requires a full reinitialisation, which means wiping all data and starting fresh**.

## EXT4. The Reliable Workhorse

EXT4 (Fourth Extended Filesystem) has been around since 2008 and is the default file system on most Linux distributions. It is mature, thoroughly tested, and about as battle-proven as file systems get. On NAS devices, EXT4 is the file system used by QNAP's standard QTS operating system and is available as an option on some other platforms.

### EXT4 Strengths

**Low resource requirements**. EXT4 runs efficiently on NAS devices with as little as 2-4GB of RAM. If you have a budget NAS with limited memory, EXT4 won't choke on the hardware.**Excellent sequential read/write performance**. For straightforward file storage, backup, and media serving, EXT4 is fast and predictable.**Journaling**. EXT4 uses a journal to track pending writes. If the NAS loses power mid-write, the journal helps the file system recover to a consistent state on reboot. This protects against metadata corruption (the file system's internal records) but does not protect against data corruption within files themselves.**Universal compatibility**. Linux natively supports ext4, but NAS disks may also use RAID, storage-pool and volume-management layers. Reading pulled NAS drives can therefore require reconstructing the original array and volume layout rather than directly mounting one disk.**Proven stability**. Nearly two decades of production use across millions of Linux systems. The codebase is mature and well-understood.

### EXT4 Limitations

**No checksumming**. EXT4 does not provide transparent checksums for ordinary file data, although it can checksum metadata and journal structures. It cannot detect or repair silent data corruption (bit rot). Data could degrade over time without any warning.**No native snapshots**. EXT4 has no built-in snapshot capability. NAS vendors may implement block-level snapshots above EXT4; their storage overhead and performance depend on the vendor implementation, workload, and configuration.**No self-healing**. If a block of data becomes corrupted, EXT4 has no mechanism to detect the corruption or reconstruct the correct data from redundancy.**Maximum volume size of 1 exabyte**. Not a practical limitation for NAS users today, but the file system was not designed with the massive storage pools that ZFS handles natively.

### Who Should Use EXT4?

EXT4 suits NAS owners who want straightforward, reliable storage without complexity. If you are running a [home NAS](/blog/best-nas-for-home-australia/) for media, backups, and file sharing, and your NAS has 4GB of RAM or less, EXT4 is a solid foundation. QNAP's standard QTS operating system uses EXT4 and handles the vast majority of home and small business workloads without issue. If data integrity verification is not a priority. Perhaps because you maintain [a proper 3-2-1 backup strategy](/blog/3-2-1-backup-strategy-nas-guide/) with offsite copies. EXT4 gives you maximum performance with minimum overhead.

## Btrfs. The Modern Middle Ground

Btrfs (B-tree File System, often pronounced "butter-FS") was developed to bring modern features to Linux without the heavy resource requirements of ZFS. It has been in development since 2007 and reached production stability for the features that NAS vendors rely on. Btrfs is Synology’s recommended file system in most scenarios on models that support it; ext4 remains available on many older or entry-level models. and is the file system most Australian NAS buyers will encounter, given [Synology's dominant market position](/blog/synology-nas-australia/).

### Btrfs Strengths

**Copy-on-write (COW)**. Btrfs uses copy-on-write for file data by default, although NOCOW can be enabled for selected workloads, which also affects features such as data checksumming and compression. When a file is modified, the new data is written to a new location, and the file system pointer is updated only after the write completes successfully. This eliminates the risk of partial writes corrupting existing data during a power failure.**Data checksumming**. Btrfs supports checksums for data and metadata. On Synology, data checksumming and File self-healing apply only to shared folders created with “Enable data checksum for advanced data integrity” and using a supported redundant RAID type. If corruption is detected, Btrfs can report it. And in a RAID configuration with redundancy, it can automatically repair the corrupted block using the good copy from another drive.**Native snapshots**. Btrfs snapshots are instant, space-efficient, and built into the file system. Synology leverages this heavily for its Snapshot Replication package, which lets you schedule automatic snapshots and roll back entire shared folders or individual files to any previous point in time. This is your first line of defence against ransomware and accidental deletion.**Moderate RAM requirements**. Btrfs runs well on NAS devices with 4-8GB of RAM. It does not demand the large memory allocations that ZFS requires, making it practical on mid-range hardware like the Synology Plus series.**Subvolumes**. Btrfs supports subvolumes, which act as independent file systems within a single volume. Synology uses subvolumes to isolate shared folders, enabling per-folder snapshots and quotas.

### Btrfs Limitations

**RAID 5/6 stability concerns**. Btrfs's own RAID 5 and RAID 6 implementations have had a troubled history, with data loss bugs that led the Btrfs developers to recommend against using them in production. Synology and other NAS vendors work around this by using the Linux kernel's mdadm software RAID layer underneath Btrfs, rather than Btrfs's native RAID. On Synology, File self-healing is supported for checksum-enabled shared folders on RAID 1, RAID 5, RAID 6, RAID 10, RAID F1, and multi-drive SHR/SHR-2; SHR may combine RAID 1, RAID 5, or RAID 6 arrays depending on the drive layout.**Performance overhead**. Copy-on-write and checksumming add overhead compared to EXT4. For most NAS workloads this is negligible, but in write-heavy scenarios (databases, virtual machine storage), the overhead can become measurable.**Fragmentation**. COW file systems are inherently prone to fragmentation over time, especially with workloads involving lots of random writes or many small file modifications. Defragmentation availability and scheduling vary by NAS platform; DSM currently exposes Btrfs file-system defragmentation as a manually initiated operation, but this is worth knowing about.**No native deduplication**. Unlike ZFS, Btrfs does not offer inline deduplication. Synology now exposes post-process automatic and manual deduplication on supported Btrfs configurations; availability depends on the NAS model and volume configuration.

### Who Should Use Btrfs?

Btrfs is the right choice for most Synology NAS owners. If you are buying a [Synology Plus series NAS](/blog/synology-nas-australia/) for home or small business use, Btrfs gives you snapshot protection, data integrity checking, and copy-on-write safety without demanding enterprise-grade RAM. Synology's DSM is purpose-built around Btrfs. Features like Snapshot Replication, immutable snapshots for ransomware protection, and per-folder rollback all depend on Btrfs being the underlying file system. There is no compelling reason to choose EXT4 over Btrfs on a Synology NAS unless you are running a very old model with minimal RAM.

## ZFS. The Enterprise Powerhouse

ZFS (Zettabyte File System) was originally developed by Sun Microsystems in 2005 and is widely regarded as the most advanced file system available for storage. It combines the file system and volume manager into a single integrated layer, giving it capabilities that neither EXT4 nor Btrfs can match. In the NAS world, ZFS powers QNAP's QuTS Hero operating system and is the foundation of current [TrueNAS](/blog/truenas-australia/) Community Edition. TrueNAS SCALE was renamed Community Edition, while TrueNAS CORE is end-of-life and no longer under active development. It is a 128-bit file system designed to handle storage pools measured in zettabytes. Far beyond anything a home or business NAS will approach.

### ZFS Strengths

ZFS's core strengths are end-to-end checksumming with automatic self-healing, copy-on-write consistency, near-instant snapshots, and an integrated ARC read cache that rewards RAM upgrades with real performance gains. It also supports RAID-Z1/Z2/Z3 (up to triple parity) and inline deduplication for repetitive data like VMs and backups. For the full breakdown of how each of these actually works, see our [dedicated ZFS guide](/blog/zfs-on-nas-explained-when-and-why-to-use-it/).

### ZFS Limitations

The trade-offs are real: the NAS platforms covered here require or recommend at least 8GB of RAM: QNAP requires 8GB for QuTS hero and 16GB for inline deduplication, while TrueNAS sizes additional memory by workload, RAID-Z vdevs are harder to expand than traditional RAID arrays, and the concept set (vdevs, zpools, ARC, L2ARC, SLOG) has a steeper learning curve than EXT4 or Btrfs. Our [ZFS guide](/blog/zfs-on-nas-explained-when-and-why-to-use-it/) covers exact hardware requirements and deduplication RAM math in full.

### Who Should Use ZFS?

ZFS is the right choice when data integrity is your top priority and you have the hardware to support it. If you are running a [business NAS](/blog/best-nas-for-small-business-australia/) that holds client data, financial records, or production files, ZFS's self-healing and checksumming provide a level of protection that neither EXT4 nor Btrfs can match. QNAP's QuTS Hero brings ZFS to purpose-built NAS hardware with a familiar interface. Choose it over standard QTS if your NAS has at least 8GB of RAM (16GB+ preferred). [TrueNAS](/blog/truenas-australia/) is built entirely around ZFS and is the platform of choice for DIY NAS builders who want maximum control. ZFS also suits [virtualisation and Docker workloads](/blog/docker-virtualisation-nas-australia/) where deduplication delivers genuine storage savings. Use the [ZFS vdev Design Wizard](/tools/zfs-vdev-calculator/) to plan your pool layout before purchasing drives.

## EXT4 vs Btrfs vs ZFS. Side-by-Side Comparison

### NAS File System Comparison

| Feature | EXT4 | Btrfs | ZFS |
| --- | --- | --- | --- |
| Copy-on-Write | No | Yes | Yes |
| Data Checksumming | No | Yes (data + metadata) | Yes (data + metadata) |
| Self-Healing | No | Yes, when a valid redundant copy is available; Synology supports checksum-enabled shared folders on RAID 1/5/6/10/F1 and multi-drive SHR/SHR-2 | Yes (all RAID-Z levels) |
| Native Snapshots | No | Yes | Yes |
| Inline Deduplication | No | No | Yes |
| Compression | No | Yes (limited) | Yes (LZ4, ZSTD, gzip) |
| Minimum RAM | Platform/model-specific | Platform/model-specific | 8 GB for QuTS hero; 8 GB for basic TrueNAS operation |
| RAID Integration | Uses mdadm/HW RAID | Uses mdadm underneath | Integrated (RAID-Z) |
| Triple Parity RAID | No | No | Yes (RAID-Z3 / RAID-TP) |
| Fragmentation Risk | Low | Moderate (COW) | Low-Moderate |
| Maturity | 18+ years | 15+ years (stable features) | 20+ years |
| NAS Platforms | QNAP QTS | Synology DSM, Asustor ADM | QNAP QuTS Hero, TrueNAS |

## Which NAS Brands Use Which File Systems?

Understanding which NAS operating system uses which file system is essential because the file system is often tied to the OS. You choose the operating system, and the file system comes with it.

### Synology (DSM). Btrfs or EXT4

[Synology](/blog/synology-nas-australia/) offers Btrfs and ext4 as file-system choices when creating a volume on supported models. On Plus series models and above, Btrfs is the recommended and default option. EXT4 is available as a fallback, primarily for older or entry-level models (Value series) where the hardware may not have sufficient resources for Btrfs. DSM's best features. Snapshot Replication, immutable snapshots, and per-folder rollback. Require Btrfs. If you are buying any Synology Plus series NAS, always choose Btrfs.

### QNAP (QTS vs QuTS Hero). EXT4 or ZFS

[QNAP](/blog/qnap-nas-australia/) takes a different approach by offering two entirely separate operating systems. QTS uses EXT4 and is suitable for home users, prosumers, and general SMB use. QuTS Hero uses ZFS and targets commercial, enterprise, and advanced technical users. The decision framework is straightforward: QTS (EXT4) if the NAS is for home use or basic business needs, QuTS Hero (ZFS) if data integrity, deduplication, or compliance requirements justify the RAM investment. Switching between QTS and QuTS Hero requires a full reinitialisation. All data must be backed up first because the drives are not cross-compatible between the two file systems.

> **Warning:** **QNAP OS switching:** Moving between QTS and QuTS Hero wipes all data on your drives. Do not install QuTS Hero on a 4GB NAS and expect miracles. QuTS hero requires at least 8GB of RAM, while QNAP requires 16GB to enable inline deduplication and recommends 32GB or more for optimal deduplication performance; ARC uses available memory dynamically. If your QNAP NAS has 4-8GB of RAM, QTS with EXT4 is the practical choice.

### TrueNAS. ZFS Only

Current [TrueNAS](/blog/truenas-australia/) Community Edition is built around OpenZFS; TrueNAS CORE is an end-of-life, archived platform. There is no option to use another file system. TrueNAS is the platform of choice for DIY NAS builders who want full ZFS capabilities with a web-based management interface. Because TrueNAS runs on generic x86 hardware, you have full control over RAM allocation. TrueNAS recommends at least 8GB for basic operation with up to eight drives; additional memory is workload-dependent, and ECC is an additional integrity defence rather than a universal requirement. For a detailed head-to-head comparison of the two platforms, see [Synology vs TrueNAS Australia](/blog/synology-vs-truenas-australia/).

### Asustor (ADM). Btrfs or EXT4

[ASUSTOR](/blog/asustor-nas-australia/) added Btrfs support with ADM 3.3 in 2019, joining Synology in offering Btrfs as the recommended file system on supported models. Like Synology, Asustor uses Btrfs for snapshot and data integrity features while maintaining EXT4 as an option for older or entry-level hardware.

### UGREEN and TerraMaster. EXT4

[UGREEN](/blog/ugreen-nas-australia/) UGOS Pro and [TerraMaster](/blog/terramaster-nas-australia/) TOS releases offer both Btrfs and EXT4 as volume filesystem choices, with availability and features depending on the platform and configuration. Both brands target the entry-level and value segments where the hardware specifications (particularly RAM) favour a lightweight file system. Current TOS 7 documentation presents Btrfs, ext4 and HyperLock-WORM as selectable volume file systems.

## Data Integrity. Bit Rot and Why It Matters

Bit rot is the silent degradation of stored data over time. A single flipped bit in a photo file might go unnoticed. A flipped bit in a database or a compressed archive can render the entire file unusable. Bit rot is not a catastrophic failure. It is a slow, invisible corruption that accumulates over months and years. By the time you notice it, your backups may also contain the corrupted versions.

This is where file system choice matters most:

**EXT4** provides no protection against bit rot. Data is written and read without verification. If a block becomes corrupted on disk, EXT4 will serve the corrupted data without any indication that something is wrong.**Btrfs** checksums metadata and normally checksums file data, but data checksumming can be disabled; on Synology, it must be enabled when the shared folder is created. If corruption is detected during a read, Btrfs will report the error. On a RAID 1 or SHR-1 volume, it can automatically reconstruct the correct data from the mirror. On Synology RAID 5/6 volumes, File self-healing supports automatic corrupted-data recovery for shared folders created with data checksumming enabled, subject to DSM's documented limitations.**ZFS** provides the strongest protection. End-to-end checksumming combined with integrated RAID means ZFS can detect and self-heal corruption across all RAID-Z levels. Scheduled scrubs proactively scan the entire pool for problems before they compound.

For most home NAS users storing media and personal files, Btrfs provides sufficient bit rot protection. For business environments where data integrity has compliance or financial implications, ZFS is the stronger choice. In either case, a file system with checksumming does not replace backups. It reduces the risk of silently backing up corrupted data.

## Snapshots. Your First Line of Defence

Snapshots are point-in-time copies of your data that let you roll back files, folders, or entire volumes to a previous state. They are your first line of defence against ransomware, accidental deletion, and software errors. Both Btrfs and ZFS support native file-system-level snapshots. EXT4 does not.

**Btrfs snapshots (Synology DSM):** Synology's Snapshot Replication package leverages Btrfs snapshots to provide scheduled, automatic snapshots of shared folders. You can configure retention policies (hourly, daily, weekly), browse previous versions of files through File Station, and roll back an entire shared folder to a specific point in time. Synology also supports immutable snapshots that cannot be deleted or modified. Critical protection against ransomware that specifically targets backup files. For a [NAS security strategy](/blog/nas-security-ransomware-protection/), Btrfs snapshots on a Synology are a foundational element. To estimate how much storage overhead your snapshot schedule will consume, use the [Snapshot Space Overhead Estimator](/tools/snapshot-space-estimator/).

**ZFS snapshots (QNAP QuTS Hero / TrueNAS):** ZFS snapshots are nearly instantaneous and initially consume no additional data space, but their storage usage grows as the live dataset changes or deletes blocks retained by the snapshot. QNAP's QuTS Hero includes SnapSync for near-real-time snapshot-based disaster recovery between two QuTS Hero NAS devices. QNAP’s QuTS hero includes SnapSync for scheduled or real-time block-level replication. Synology Snapshot Replication provides remote replication on schedules as frequent as five minutes, but does not directly match QNAP’s real-time zero-RPO mode. TrueNAS exposes the full power of ZFS snapshots, including clones (writable copies of snapshots) and send/receive for efficient replication between TrueNAS systems.

**EXT4 (QNAP QTS):** QNAP's QTS provides snapshot functionality even on EXT4, but it is implemented at a layer above the file system rather than natively within it. This implementation differs from the native snapshot mechanisms provided by Btrfs and ZFS, and its storage overhead and performance depend on the workload and configuration.

## Performance Considerations

For the typical NAS workload. File sharing over a [gigabit or 2.5GbE network](/blog/nas-networking-guide-australia/), media streaming, backups. All three file systems perform well. The network link is almost always the bottleneck before the file system becomes a limiting factor. On a standard 1GbE connection (limited to roughly 110-115 MB/s throughput), all three can saturate a 1GbE link in suitable configurations, but actual throughput depends on the NAS hardware, array layout, protocol, file sizes, and workload.

Performance differences become more relevant in specific scenarios:

**Random write-heavy workloads (databases, VMs):** EXT4 generally has the lowest overhead. Btrfs and ZFS's copy-on-write behaviour adds latency for random writes because each modification creates new blocks rather than updating in place. A separate SLOG device can improve synchronous-write latency by storing the ZFS Intent Log. It is not a general write cache and does not improve asynchronous writes.**Large sequential reads (media streaming, backup reads):** All three perform similarly. ZFS may have a slight edge with ARC caching if the NAS has ample RAM.**Deduplication-heavy workloads:** ZFS offers native inline deduplication; Btrfs also supports out-of-band deduplication, and current DSM exposes post-process deduplication on supported configurations. With adequate workload-specific resources, deduplication can reduce storage use when the dataset has a verified duplication ratio; memory needs cannot be determined from a universal 32GB threshold. But with insufficient RAM, deduplication will crush performance as the DDT spills from RAM to disk.**SSD and NVMe storage:** On [all-flash NAS configurations](/blog/ssd-cache-all-flash-nas-australia/), the performance differences between file systems become more pronounced because the storage medium is no longer the bottleneck. ZFS and Btrfs's COW overhead is more visible on fast media, but both still perform well within NAS use cases.

## RAM Requirements. The Practical Constraint

RAM is the single most important factor in choosing between these file systems on a NAS. Here is the practical guidance:

- **EXT4 (QNAP QTS):** 2-4 GB minimum, runs efficiently on entry-level hardware
- **Btrfs (Synology DSM):** no universal 4GB minimum; support and practical memory needs are model- and workload-specific. Current 2GB models such as the DS225+ officially support Btrfs.
- **ZFS (QuTS Hero):** 8 GB minimum to install, 16 GB+ recommended, 32 GB+ for deduplication
- **ZFS (TrueNAS):** at least 8 GB for basic operation with up to eight drives; additional RAM is workload-dependent, and ECC is recommended as an additional integrity defence
- **Rule of thumb (ZFS):** Start with at least 8 GB for basic operation with up to eight drives, then size additional RAM for drive count and workload

If your NAS has 4GB of RAM that cannot be upgraded, ZFS is not a viable option. Btrfs or EXT4 are your choices, and Btrfs is the better one if your NAS supports it. If your NAS has 8GB of RAM, ZFS will run but without the headroom for deduplication or large ARC cache. For ZFS to truly shine, 16GB or more is the starting point. Many [QNAP NAS models](/blog/best-qnap-nas/) have user-upgradeable RAM. Check whether your model supports a RAM upgrade before deciding between QTS and QuTS Hero.

## How to Choose the Right File System for Your NAS

The decision is less about which file system is "best" and more about which file system matches your hardware, your NAS platform, and your priorities. Here is a practical framework:

### Choose EXT4 If…

You are running QNAP QTS and your NAS has 4-8GB of RAMYour primary use case is file sharing, backup, and media servingYou maintain a proper [3-2-1 backup strategy](/blog/3-2-1-backup-strategy-nas-guide/) that protects against data loss independently of the file systemYou want maximum raw performance with minimum overheadYou are running a [budget NAS](/blog/best-nas-under-500-australia/) where every megabyte of RAM counts

### Choose Btrfs If…

You are running a Synology NAS (Btrfs is the default and recommended option on Plus series and above)You want snapshot protection against ransomware and accidental deletionYou want data integrity checking without the heavy RAM requirements of ZFSYour NAS has 4-8GB of RAMYou are running Asustor ADM on a supported model

### Choose ZFS If…

Data integrity is your top priority. Business-critical storage, compliance, or archivalYour NAS has 16GB+ of RAM (or you can upgrade it)You want inline deduplication for virtualisation or development environmentsYou are running QNAP QuTS Hero or building a TrueNAS systemYou need RAID-Z3 triple parity for large arraysYou want the most comprehensive protection against bit rot and silent data corruption

> **Tip:** **Australian Consumer Law protections apply** when purchasing NAS hardware from Australian retailers. For an Australian Consumer Law remedy, the seller must assist and cannot direct you to the manufacturer. Separate manufacturer warranties may also be claimed under their terms, and consumers can pursue manufacturers for some consumer-guarantee remedies. Local service arrangements vary by brand, model, warranty or support plan, and location: Synology offers optional on-site replacement for eligible devices in select Australian metropolitan areas through Computergate, while QNAP provides an Australian RMA process with a designated repair-centre address supplied after approval. Choose a retailer with a clear warranty process, especially for business-critical NAS deployments where [where you buy](/blog/where-to-buy-nas-australia/) matters as much as what you buy.

## Common Mistakes When Choosing a NAS File System

**Installing ZFS on a low-RAM NAS:** Putting QuTS Hero on a 4GB QNAP NAS because ZFS sounds better is a common mistake. Current QuTS hero requires at least 8GB of RAM, so a 4GB QNAP system does not meet QNAP's installation requirement. Performance varies by model, workload, and configuration; systems below QuTS hero's 8GB requirement should remain on a supported QTS configuration.**Assuming snapshots replace backups:** Snapshots are not backups. They protect against accidental deletion and ransomware, but they live on the same physical drives. If the NAS hardware fails, or multiple drives fail simultaneously, snapshots go with them. Always maintain offsite or cloud backups alongside snapshots. Read our [NAS backup software guide](/blog/nas-backup-software-australia/) for options.**Ignoring the file system choice at setup:** Changing file systems later requires reinitialising the storage pool. Wiping all data. Make the right choice at setup. If you are unsure, Btrfs on Synology or EXT4 on QNAP QTS are safe defaults that serve the majority of use cases.**Enabling ZFS deduplication without enough RAM:** Deduplication sounds appealing on paper, but the DDT is persistent pool metadata that may be cached in ARC or L2ARC; insufficient RAM can substantially increase metadata I/O and reduce performance. For a 20TB pool, the DDT can easily exceed 20-40GB of RAM. If it spills to disk, performance collapses. Only enable deduplication if you have measured your dedup ratio on a test dataset and confirmed you have enough RAM.**Choosing a file system based on internet forums instead of your hardware:** ZFS is technically superior, but that superiority only materialises with adequate RAM. Match the file system to your hardware, not to forum recommendations.

## NBN and Network Considerations

File system choice does not directly affect your network performance, but it intersects with NAS networking in a few ways worth noting for Australian users. Current NBN Home Fast upload speeds depend on the access product: eligible FTTP/HFC Home Fast II services offer up to 50 Mbps wholesale upload, while Home Fast I offers 20 Mbps upload on FTTC and 5-20 Mbps on FTTN/FTTB. Retail and actual speeds depend on the RSP and connection. If you are using your NAS for [remote access](/blog/nas-remote-access-vpn-australia/) or cloud sync, your NBN upload speed. Not your file system. Is the bottleneck.

Where file systems matter on the network side is snapshot-based replication. ZFS's send/receive and QNAP's SnapSync are incremental. Only changed blocks are transmitted after the initial full sync. Over an NBN connection with limited upload bandwidth, this efficiency matters. After the initial sync, block-level replication sends changed blocks rather than necessarily retransmitting the whole file; the amount transferred is not guaranteed to equal the exact number of application bytes changed. Btrfs snapshot replication on Synology works similarly via Snapshot Replication's remote replication feature. Both are dramatically more efficient than traditional file-level backup over a slow WAN link. Also be aware that CGNAT (Carrier-Grade NAT) on some NBN connections can block inbound remote access to your NAS. A VPN or Synology's QuickConnect / QNAP's myQNAPcloud relay can work around this.

## Frequently Asked Questions

Our [Drive Failure Risk Estimator](/tools/drive-failure-risk/) shows how your choice of RAID level (RAID 5 vs RAID 6) affects the statistical probability of data loss for a given drive count and AFR. Useful context alongside filesystem choice.

Use our free [NAS Sizing Wizard](/tools/nas-sizing-wizard/) to get a personalised NAS recommendation.

See also: [our complete Synology NAS Australia guide](/brand-guides/synology/).

See also: [our complete QNAP NAS Australia guide](/brand-guides/qnap/).

**Q: Can I change the file system on my NAS without losing data?**

No. A Synology volume cannot be converted between ext4 and Btrfs in place; its data must be backed up or moved to a newly created volume. Switching a compatible QNAP between QTS and QuTS hero requires reinitialisation and a complete backup. This applies whether you are switching from EXT4 to Btrfs on a Synology, or between QTS (EXT4) and QuTS Hero (ZFS) on a QNAP. Always back up all data before switching. If you are setting up a new NAS, make the file system decision at the beginning. It is much harder to change later.

**Q: Is Btrfs stable enough for production use in 2026?**

Yes, for the features that NAS vendors use. Btrfs's core features. Copy-on-write, checksumming, snapshots, and subvolumes. Are stable and are supported and recommended by Synology for most scenarios on compatible models. The instability concerns around Btrfs relate specifically to its native RAID 5/6 implementation, which Synology and other NAS vendors avoid by using the Linux kernel's mdadm RAID layer underneath Btrfs. On a Synology NAS, Btrfs is a safe and recommended choice.

**Q: How much RAM do I need for ZFS on a NAS?**

A minimum of 8GB is required to install QNAP's QuTS Hero. For practical use, 16GB is recommended. If you plan to use inline deduplication, 32GB or more is advisable. For TrueNAS, start with at least 8GB for basic operation with up to eight drives, then size additional memory for the actual services and workload; deduplication has separate, dataset-dependent requirements. For TrueNAS builds, 16-32GB of ECC RAM is the standard starting point. Do not plan a current QuTS hero or TrueNAS installation with 4GB: QNAP requires at least 8GB for QuTS hero, and TrueNAS specifies at least 8GB.

**Q: Does EXT4 support snapshots on a QNAP NAS?**

QNAP's QTS (which uses EXT4) does include a snapshot feature, but it is implemented at a higher layer rather than natively within the file system. QTS snapshots work at the block/storage-pool layer above EXT4; their storage overhead and performance depend on the workload, volume type, and configuration. For most home and small business users running QTS, the snapshot functionality is still useful for ransomware protection and accidental deletion recovery.

**Q: Should I choose Synology (Btrfs) or QNAP QuTS Hero (ZFS) for data integrity?**

Both provide data integrity protection through checksumming, but ZFS is stronger. ZFS can self-heal corrupted data when a valid redundant copy exists, such as in a mirror, RAID-Z vdev, or suitably configured copies. Checksums can still detect corruption in a non-redundant pool, but cannot reconstruct user data without redundancy. On Synology, File self-healing is supported for checksum-enabled shared folders on RAID 1, RAID 5, RAID 6, RAID 10, RAID F1, and multi-drive SHR/SHR-2. For the typical home or small business NAS with 4-8GB of RAM, Synology with Btrfs provides excellent data integrity protection. For business-critical environments where you need maximum integrity guarantees and have the RAM budget (16GB+), QNAP QuTS Hero with ZFS offers stronger end-to-end protection. Read our [Synology vs QNAP comparison](/blog/synology-vs-qnap-australia/) for a broader look at the two platforms.

**Q: Does the file system affect NAS performance for Plex media streaming?**

For [Plex media streaming](/blog/best-nas-for-plex-australia/), the file system has negligible impact on performance. Plex reads large sequential video files, which all three file systems handle efficiently. The bottleneck for Plex is typically the NAS CPU (for transcoding) and the network connection, not the file system. Any of EXT4, Btrfs, or ZFS will work well for Plex. Choose your file system based on data protection needs, not Plex performance.

**Q: What is bit rot and should I be worried about it?**

Bit rot is the gradual, silent corruption of stored data caused by physical degradation of storage media, cosmic rays, electrical interference, or firmware bugs. A single flipped bit can corrupt a file without any visible warning. For most home users with a proper backup strategy, bit rot is a low-probability risk. However, for long-term archival storage. Years of family photos, irreplaceable documents, or business records. Choosing a file system with checksumming (Btrfs or ZFS) adds a meaningful layer of protection. With file-data checksumming enabled, Btrfs or ZFS can detect checksum mismatches when affected blocks are read or scrubbed; repair still requires a valid redundant copy or backup.

**Q: Can I use ZFS on a Synology NAS?**

No. Synology's DSM operating system supports Btrfs and EXT4 only. ZFS is not available on Synology hardware. If ZFS is a priority, your options are QNAP with QuTS Hero or building a TrueNAS system on compatible hardware. For most Synology buyers, Btrfs provides a strong balance of data integrity, snapshot support, and moderate resource requirements without needing ZFS.

**[Browse NAS Buying Guides →](https://needtoknowit.com.au/blog/best-nas-australia/)** -- Not sure which NAS is right for your needs? Our buying guides cover every budget and use case for Australian buyers.