Frigate surveillance storage buying guide
Choosing a Frigate recording drive is primarily a sustained-write, capacity and reliability decision. Frigate writes retained recording segments from the camera stream rather than turning every frame into a newly encoded file, so the storage plan should start with the real record-stream bitrate, the percentage of time you retain, and the number of days you need. This page keeps current surveillance-drive listings near the top, then shows how to translate a camera plan into practical drive capacity without treating one fixed terabyte-per-camera number as universal.
Quick answer
What this Frigate workload needs
For most always-on Frigate NVRs, a surveillance-class SATA HDD is the sensible bulk-recording target. Calculate the footage requirement from measured bitrate and retention, add free-space headroom, then choose a capacity that leaves room for bitrate spikes and future cameras. Keep the Frigate host, database and container files on SSD when possible so the recording disk can focus on sequential footage writes.
Live Amazon hardware
Current products that fit this decision
Compare current Amazon listings relevant to this guide. Product availability and prices can change.
Buying decision
Match the hardware to the bottleneck
Buy the drive for the recording workload, not for desktop benchmark scores. A lower-cost drive is not a bargain if the exact capacity, interface, condition or warranty is unclear. Compare SkyHawk and WD Purple-class listings only after the storage calculator says how much usable capacity your camera plan actually needs.
Interactive decision tool
Frigate HDD Capacity Selector
Use the workload inputs to size a practical Frigate hardware tier before comparing live products. Results are planning guidance; verify current Frigate support, camera bitrates and the exact hardware configuration before deployment.
Compatibility checklist
Four checks before you purchase
Keep live products near the decision
Current Amazon listings appear above the long guide so capacity, interfaces and prices can be checked before deep reading.
Measure the real workload
Use camera bitrate, retention, PoE draw and network aggregation instead of relying on fixed per-camera rules.
Separate application and recording storage
Keep the Frigate configuration/database role distinct from bulk video retention so each storage tier can be sized correctly.
Verify the complete data path
Camera, switch, NVR, storage and UPS are one recording system; a weak link anywhere can affect reliability.
Start with the recording stream bitrate
A storage estimate is only as good as the bitrate assumption behind it. Frigate recordings are based on the configured record stream, so use the bitrate from the camera or from measured network traffic rather than a generic resolution label. Two 4K cameras can consume very different storage when one records at 5 Mbps and another at 14 Mbps. Multiply average Mbps by camera count, active recording time and retention days, then add operational headroom before choosing a drive.
Surveillance HDDs fit continuous write workloads
SkyHawk and WD Purple families are marketed for surveillance duty, where drives see long sequential writes, frequent reads during review, and continuous operation. That workload is different from a desktop disk that spends much of its time idle. Frigate does not require a particular brand, but a surveillance-oriented drive is a practical starting point for a dedicated recorder because the workload and warranty terms are easier to reason about than an unknown bargain HDD.
Local recording storage keeps dependencies simple
Local SATA storage removes a network hop from the recording path. That matters because a recorder has to keep ingesting segments even when the rest of the home network is busy. Network storage can work, but it adds the NAS, switch, cabling and mount behavior to the write path. If the goal is a simple dependable NVR, local recording storage is usually easier to diagnose and recover than a remote share.
Slow storage can become a recording problem
Frigate troubleshooting guidance specifically calls out storage performance when recording copy times become slow. If the recording destination cannot keep up, the problem is not solved by adding more nominal terabytes. Check disk health, mount options, filesystem behavior and network-share performance before assuming Frigate itself is at fault. A healthy recording path should have enough sustained throughput and latency headroom for peak camera activity plus maintenance tasks.
Continuous and event-focused retention need different capacity
A continuous-retention design assumes every camera contributes footage around the clock. Event- or motion-focused retention can cut storage dramatically, but only if the duty-cycle assumption reflects the property. A quiet back garden and a busy street-facing camera should not share the same guessed activity percentage. Model each camera group separately when accuracy matters, especially if you are trying to fit a long retention window on one disk.
Leave free space instead of sizing to the decimal
A calculator may produce 11.4 TB, but that does not mean a nominal 12 TB drive is a comfortable target. Filesystem overhead, bitrate variation, temporary files and operational safety margin all consume space. Planning 15 to 25 percent headroom gives the recorder room to breathe and makes later camera additions less disruptive. The goal is not to fill a disk as efficiently as possible; it is to keep the recording system predictable.
One large drive versus several drives
One large surveillance drive is simple, quiet and power-efficient for modest systems. Multiple drives become useful when a single capacity is no longer enough or when the server architecture benefits from redundancy. More drives also mean more spin-up power, heat, vibration and potential failure points. Size the footage first, then decide whether the physical layout should be one large disk, a mirrored pair or a larger storage pool.
Redundancy is not a backup of important footage
RAID or mirroring can keep storage online after a drive failure, but it does not protect against accidental deletion, filesystem corruption, theft or a power event that damages the whole recorder. Export important clips and maintain a separate backup strategy for anything you cannot afford to lose. Do not double the recording-drive budget just to say the NVR is backed up when there is no independent copy.
Power, noise and cooling matter in an always-on NVR
Large 3.5-inch hard drives add heat and acoustic noise that tiny mini-PC guides often ignore. A compact enclosure that is quiet with one SSD may be unsuitable once two high-capacity HDDs are installed. Check airflow across the drive bays, power-supply spin-up capacity and the location of the recorder. A drive that stays cool and stable in a ventilated chassis is more useful than a theoretically faster model trapped in a hot box.
Use an SSD for the operating stack when practical
The Frigate configuration and database live separately from the recording directory. Putting the operating system, Docker data and Frigate configuration on SSD improves general responsiveness and keeps random host I/O away from the bulk recording disk. That split also makes it easier to replace or expand the video volume later without rebuilding the whole host. A small, good-quality SSD plus a large surveillance HDD is a strong default architecture.
Verify the exact Amazon listing before buying
Marketplace listings can mix capacities, renewed drives, OEM units and multiple family variants on one product page. This sprint normalizes only listings that match the intended drive family and capacity query, but the buyer should still confirm the exact model, condition, seller and warranty on Amazon before checkout. A low displayed price is not enough evidence that a listing is the same drive discussed in the guide.
Measure the installed system and revisit retention
After deployment, compare actual daily storage growth with the estimate. Camera bitrate settings, night scenes, audio and recording rules can shift consumption. If the real system uses 15 percent more than planned, adjust retention or add capacity before the disk becomes chronically full. Capacity planning should be a feedback loop: estimate, deploy, measure, then tune the system using real footage rather than assumptions.
Questions people ask
Best Hard Drive for Frigate FAQs
What type of hard drive is best for Frigate?
A surveillance-class SATA HDD is a strong default for bulk Frigate recordings because it is designed for continuous camera workloads and large capacities. Exact capacity should be calculated from bitrate and retention.
Can Frigate use a normal desktop HDD?
It can, but desktop drives may have different workload and warranty assumptions. For an always-on recorder, compare the exact drive specification, recording load and replacement risk before choosing purely on price.
How many terabytes do I need for Frigate?
There is no fixed answer per camera. Multiply the average recording bitrate by camera count, recording duty cycle and retention days, then add headroom.
Can I record Frigate to a NAS?
Yes, but network storage adds network and NAS dependencies. Frigate troubleshooting guidance notes that network-share performance can affect recording copy times, so the path must be stable and fast.
Is SkyHawk AI required for Frigate?
No. Frigate does not require SkyHawk AI. It is one surveillance-drive option; standard SkyHawk and WD Purple-class drives may also fit depending on capacity, workload and price.
Should I use RAID for Frigate recordings?
RAID can improve availability, but it also reduces usable capacity and does not replace a backup. Decide whether continuous availability is worth the extra disks for your installation.
Should Frigate recordings be on SSD or HDD?
HDDs usually provide better cost per terabyte for long retention. SSDs make sense for small silent systems or where their endurance and capacity economics fit the workload.
How much free space should I leave?
A planning margin around 15 to 25 percent is practical for bitrate variation, filesystem overhead and future changes. Avoid sizing a drive to the calculator result with no margin.
Does Frigate re-encode recordings before writing them?
Frigate documentation says recordings are written directly from the camera stream without re-encoding in normal recording operation. That is why record-stream bitrate is central to storage sizing.
How often should I recalculate Frigate storage?
Recheck after the first few weeks and whenever camera bitrate, recording mode, retention or camera count changes. Real daily growth is better than a generic estimate.
Official references and methodology
Verify current Frigate support before deployment
Cloudzat calculates the storage requirement from bitrate, recording duty cycle and retention, then compares current accepted surveillance-drive listings from this sprint's isolated Amazon catalogue. Drive family, capacity, condition and listing evidence are checked independently; current seller and warranty terms should still be verified before purchase.
- Frigate - Recording
- Frigate - Installation
- Frigate - Restream
- Frigate - Configuring go2rtc
- Frigate - Troubleshooting Recordings
- Frigate - Camera Setup
As an Amazon Associate, Cloudzat may earn from qualifying purchases. Prices, seller terms, exact configurations, camera firmware and Frigate support can change.