QNAP TS-264: capacity calculator
By Devin Chua · Data checked by Owen Nakamura · Updated In the QNAP TS-264 with 2 × 8 TB in RAID 1 you keep 7.28 TiB usable (8 TB in drive-maker terms), surviving 1 drive failing. The calculator below is preset to the 2 bays and the RAID types QTS 5.2 or QuTS hero (ZFS) actually offers on this model (there is no SHR equivalent here), with the cost to fill in Canadian dollars from live Amazon.ca prices.
As an Amazon Associate we earn from qualifying purchases on Amazon.ca.
Preset for the TS-264: 2 bays, and only the RAID types this model actually supports.
RAID 1 (Mirroring)
That is 8 TB the way drive makers label capacity. Your NAS shows you the smaller number because it counts in powers of two.
Drives: from CA$1,008 for 2 × 8 TB (CA$63.01/TB overall)
What to know about the TS-264
Two bays, but the kit of a bigger machine: two NVMe slots, two 2.5-gigabit ports and a PCIe slot. With only two drives, RAID 1 is the one sensible choice, which halves the capacity no matter how large the drives are.
The TS-264 at a glance
| Bays | 2 × 3.5-inch SATA and 2.5-inch SATA SSD |
|---|---|
| Processor | Intel Celeron N5095 (4 cores) |
| Memory | 8 GB stock, DDR4 SO-DIMM, no ECC (2 slots) 16 GB official; 32 GB is reported in forums but not endorsed. |
| M.2 NVMe | 2 slots 2 × M.2 2280 NVMe (PCIe 3.0 x1), freely populated |
| Network | 2 × 2.5GbE, expandable via the PCIe slot |
| RAID types | Single, JBOD, RAID 0, RAID 1 |
| Third-party drives | unrestricted Open. QNAP locks no drives; the compatibility list is guidance. |
No SHR: mixed drive sizes cost the TS-264 capacity
QTS 5.2 or QuTS hero (ZFS) has no flexible RAID like Synology's SHR. Put one 16 TB drive with three 8 TB drives in the TS-264 and it counts 8 TB per drive — eight terabytes sit idle. So buy matched drives for the TS-264, or work the loss out in the calculator above before you commit to this model; the "unused" figure shows exactly how much you would lose.
Two bays means RAID 1 in practice on the TS-264
With two drives there is no sensible alternative to RAID 1 on the TS-264 (or SHR with two drives, which is arithmetically the same). You pay half your capacity for fault tolerance: 2 × 8 TB becomes 8 TB, not 16. RAID 5 needs at least three drives and is not available here. For more capacity per dollar without giving up safety, a four-bay model is the move.
Which drives belong in the TS-264?
CMR NAS drives rated for 24/7 use — Seagate IronWolf, WD Red Plus, Toshiba N300 or their Pro variants. Our drive picks for the TS-264 with live prices show which of those currently offers the best capacity per dollar. If you are working back from a target capacity instead, the drive-count calculator works out how many drives you need.
Frequently asked questions
How much storage is left in the TS-264 with 2 × 8 TB?
About 7.28 TiB usable — 8 TB in drive-maker terms — computed in RAID 1, the sensible default for this model. It survives 1 drive failing. The gap from the 16 TB raw goes to parity.
Which RAID types does the TS-264 support?
QTS 5.2 or QuTS hero (ZFS) offers Single, JBOD, RAID 0, RAID 1 on the TS-264. There is no flexible RAID like Synology's SHR here, so mixed drive sizes cost the TS-264 real capacity — every drive counts only as much as the smallest in the array.
Can I put third-party drives in the TS-264?
Open. QNAP locks no drives; the compatibility list is guidance.
How much memory does the TS-264 take?
It ships with 8 GB (DDR4 SO-DIMM, no ECC (2 slots)). 16 GB official; 32 GB is reported in forums but not endorsed. There are 2 slots.
Why does my NAS show less than the calculator says?
Because the maker and the OS count differently. A drive maker calls one trillion bytes a TB; the NAS counts in powers of two and calls that a TiB — about 9 percent less. That is why this calculator leads with the TiB figure: it is the number you will read off the screen.
Devin Chua works out which drives, RAM and NVMe cache fit which NAS model at nasdrives.ca, and what the RAID choice means for usable capacity, checked against what is in stock on Amazon.ca.
Data checked by Owen Nakamura, Technical editor (data checking)