Frigate SSD buying guide
An SSD can play several very different roles in a Frigate system: boot drive, Docker storage, configuration and database volume, cache, or the actual recording destination. Those roles should not be collapsed into one vague recommendation. This guide separates low-capacity random-I/O work from high-volume video retention, shows current SSD listings near the top, and explains when NVMe performance matters, when a SATA SSD is already sufficient, and when an HDD is still the better bulk-storage purchase.
Quick answer
What this Frigate workload needs
Use a reliable SSD for the host operating system, Docker data and Frigate configuration/database. A 1–2 TB NVMe drive gives comfortable room for the application stack and other services, while long continuous video retention is usually more economical on surveillance HDDs. If you want an all-SSD recorder, calculate the daily write volume and compare endurance as carefully as capacity.
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
For most home Frigate systems, buy the SSD for responsiveness and endurance rather than maximum sequential benchmark speed. A premium 7 GB/s NVMe drive does not make a low-bitrate camera stream record seven times better. Choose capacity, thermal behavior and write endurance first, then pay for speed only where the host workload can use it.
Interactive decision tool
Frigate SSD Role & Endurance Planner
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.
Separate the database role from the recording role
Frigate uses /config for its configuration and sqlite database while recordings live under /media/frigate. That separation is useful when designing storage. The database and host stack benefit from low-latency SSD access, while the recording volume is dominated by sustained sequential writes and capacity. A single SSD can serve both on a small installation, but treating them as separate roles makes future upgrades and troubleshooting much easier.
NVMe is valuable for the host but not mandatory for every stream
A modern NVMe SSD gives fast application startup, database access, updates and container operations. Camera recordings themselves usually arrive at far lower aggregate bandwidth than an NVMe drive can sustain. If the host only has SATA, a good SATA SSD can still be a perfectly capable boot and database drive. Buy NVMe because it fits the platform and broader workload, not because Frigate footage inherently needs flagship sequential speeds.
Continuous recording makes endurance relevant
An all-SSD NVR can write many terabytes over time. Estimate annual writes from the same bitrate calculation used for storage sizing, then compare that workload with the drive's published endurance and warranty terms. Consumer SSDs differ substantially in TBW ratings and warranty conditions. If the recording volume is large enough to dominate lifetime writes, a cheaper surveillance HDD plus SSD host drive may be the more rational architecture.
Database and metadata activity favors low latency
The Frigate database, configuration and surrounding host services generate smaller random I/O that feels very different from video recording. Keeping those operations on SSD helps the UI, database and container stack remain responsive while the large recording disk is busy. It also isolates an HDD replacement from the core application. This is one reason a small SSD plus large HDD is such a practical default for self-hosted NVRs.
SATA SSDs remain useful in constrained systems
Many small PCs and NAS-style enclosures have limited M.2 slots but available 2.5-inch bays. A reputable SATA SSD can be a good fit for Frigate configuration, database and moderate recording loads. Sequential bandwidth is far above typical home camera traffic. The tradeoff is that some SATA models have lower endurance or use older controllers, so compare the exact capacity and warranty rather than assuming all 2.5-inch SSDs are equivalent.
Thermals matter in tiny NVR boxes
NVMe drives can throttle in compact fanless or poorly ventilated mini PCs. An NVR is an always-on appliance, so stable sustained performance is more useful than a short benchmark burst. Check whether the host includes an M.2 heat spreader and whether airflow reaches the SSD. A cooler midrange drive can be a better long-term choice than a hotter flagship model if the chassis cannot remove its heat.
An all-SSD recorder is a deliberate choice
SSD-only storage can make sense when silence, shock resistance, compact size or power draw matter more than cost per terabyte. It is especially attractive for a few cameras with shorter retention. For 10, 20 or more terabytes of continuous video, HDD economics usually win. Use the calculator to identify whether the installation is truly small enough that all-SSD storage is still cost-effective.
Faster storage does not fix camera-side problems
Dropped frames, unstable RTSP sessions or excessive CPU use are not automatically storage problems. Frigate recommends appropriate camera streams and hardware video decoding. If a camera sends an awkward codec or the host lacks acceleration, replacing a SATA SSD with a flagship NVMe model will not solve the root cause. Measure storage copy times, CPU load and network stability separately before buying a faster drive.
Plan power-loss protection for database integrity
An SSD does not make sudden power loss harmless. The Frigate database and filesystem still benefit from a clean shutdown. A UPS gives the host time to stop containers and flush writes, and it also keeps the switch and cameras alive during short outages when those devices share the protected circuit. Storage reliability is a system property, not a feature of the SSD alone.
Keep meaningful free space on the SSD
SSDs work best when they are not permanently filled to the last few gigabytes. Leave capacity for Docker layers, database growth, updates, logs and temporary operations. If recordings also live on the SSD, include a larger headroom margin. A 2 TB drive that is constantly at 98 percent usage is less comfortable to operate than a larger drive with predictable free space.
Verify exact capacity and model on marketplace listings
Amazon search results can combine 1 TB, 2 TB and 4 TB variants under one title. This sprint filters targeted SSD families and capacities, but the final product page may still expose variant selectors. Confirm exact capacity, heatsink version, condition and seller before purchasing. The live price is useful only when it corresponds to the exact storage configuration you intend to install.
Benchmark the real Frigate workload after deployment
After installation, use host monitoring to check disk utilization, I/O latency and free-space growth. A drive that appears slow in a synthetic benchmark may be completely idle under the actual NVR workload, while an undersized drive may have plenty of speed but run out of capacity. The operational metrics should guide the next upgrade rather than benchmark rankings alone.
Questions people ask
Best SSD for Frigate FAQs
What SSD size should I use for Frigate?
For the OS, Docker stack, configuration and database, 500 GB to 2 TB is comfortable for many systems depending on other services. If recordings also live on SSD, size from bitrate and retention instead.
Does Frigate need NVMe?
No. NVMe is convenient and fast, but a good SATA SSD can handle Frigate host and database workloads. The recording workload usually needs capacity and endurance more than extreme sequential speed.
Can Frigate recordings live on an SSD?
Yes. It can be a good silent option for short retention or a small camera count. Check annual write volume, endurance and cost per terabyte.
Should the Frigate database be on SSD?
It is a sensible choice because the database and application stack benefit from low-latency random I/O, while bulk recordings can be placed on a separate HDD.
Is a Samsung 990 PRO overkill for Frigate?
It can be more performance than Frigate alone needs, but it may still be useful in a multi-purpose host. Compare price, endurance, thermals and the other workloads on the machine.
Should I use a heatsink on an NVMe SSD?
Follow the SSD and host guidance. In compact systems a heat spreader or airflow can help avoid sustained thermal throttling.
How do I calculate SSD endurance for recording?
Estimate the terabytes written per day from camera bitrate and retention behavior, multiply by annual operation, then compare with the manufacturer's endurance and warranty terms.
Can the OS and recordings share one SSD?
Yes for modest systems, but separating the application SSD from bulk recordings simplifies capacity management and future storage replacement.
Will a faster SSD improve object detection?
Usually not directly. Object detection depends on the detector and model pipeline. SSD speed mainly affects storage and application I/O, not inference throughput.
Should I buy a renewed SSD for an NVR?
Only when the exact condition, seller, warranty and expected wear are acceptable. For continuous-write roles, uncertain prior write history deserves extra caution.
Official references and methodology
Verify current Frigate support before deployment
Cloudzat separates Frigate application/database storage from recording storage, estimates write volume where relevant, and presents only accepted SSD listings from this sprint's Amazon refresh. Model, capacity and condition are normalized, but endurance and warranty should be verified against the exact manufacturer documentation and seller listing.
- 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.