Blue Iris requirements explained
Blue Iris Hardware Requirements: CPU, RAM, GPU & Storage
Blue Iris has published minimum and recommended system requirements, but the minimum is not a complete purchasing specification for a recorder carrying dozens of high-resolution streams. This page turns the official baseline into a workload checklist for CPU, memory, graphics acceleration, storage, network and power.
Quick answer
The official baseline is only the starting point
Blue Iris currently lists a newer Intel processor, 8GB or more RAM and a 64-bit Windows environment as minimums. Its recommended guidance moves to Intel Core or Ultra, more memory for high-megapixel cameras, optional NVIDIA graphics and 7200+ RPM and/or SSD storage. A production build should add margin for the exact cameras and features.
Live Amazon hardware
Current hardware for this Blue Iris decision
Products come from this sprint's dedicated catalogue. Complete PCs, mini PCs, NVIDIA GPUs, surveillance HDDs, internal SSDs, PoE switches and UPS systems stay in separate classes. Laptops, barebones, external drives, enclosures, injectors, replacement batteries and obvious wrong product types are rejected.
Buying decision
Translate every feature into a hardware path
Resolution and FPS increase video work, bitrate drives network and storage, AI adds compute and memory, remote users add decode/encode work, and long retention adds disk capacity. The right requirement is therefore a coordinated system rather than a single CPU recommendation.
Interactive decision tool
Blue Iris Hardware Requirements Calculator
Use the inputs to turn camera count into a workload plan. Storage math is based on the bitrate you enter; compute tiers are directional Cloudzat planning guidance, not Blue Iris benchmark guarantees. Verify the exact processor graphics, GPU codec support, drive model, PoE budget and measured camera bitrates before purchase.
Compatibility checklist
Four checks before buying Blue Iris hardware
Size from the actual camera workload
Camera count alone is not enough. Resolution, frame rate, codec, bitrate, substreams, AI analysis and remote viewing all change the compute and storage path.
Treat hardware acceleration as model-specific
Blue Iris 6 integrates Intel QSV/oneVPL and NVIDIA video acceleration, but the exact CPU or GPU must expose the required hardware features. Do not infer support from a family name alone.
Separate recording storage from the system drive
Keep Windows, the Blue Iris database and recorded video roles clear. Surveillance HDDs are designed for continuous recording, while SSDs can serve the OS/database or high-speed clip workflows.
Power and network are part of the recorder
PoE capacity, switch uplinks, UPS runtime and NIC bandwidth can stop a surveillance system even when the PC itself is fast enough. Plan the whole path from camera to disk.
Minimum requirements tell you what can run, not what to buy
A minimum specification is useful for compatibility, but it does not describe the load created by your cameras. A recorder that meets the minimum can still be overwhelmed by many high-resolution streams, heavy AI or remote viewing.
Use the minimum only as the floor. For a new system, start from the recommended Intel Core or Ultra class and work upward according to aggregate video, memory, storage and network demand.
Resolution and frame rate create an aggregate pixel workload
Each camera produces a stream of image frames. Multiplying camera count by megapixels and frames per second creates a useful comparative workload measure even though it is not a Blue Iris benchmark.
The calculator reports this aggregate pixel rate so two systems with the same camera count can be compared honestly. It does not convert that number into a guaranteed CPU model because codecs, substreams and acceleration materially change the result.
Bitrate is the number that controls storage math
Recording capacity depends on the number of bits written per second, not just the label 1080p or 4K. Two cameras with the same resolution can use very different bitrates because of scene complexity, codec settings and quality targets.
Measure or estimate the average bitrate for each stream. The storage calculator converts that bitrate into terabytes per day and retention capacity without pretending that all 4K cameras produce the same file size.
CPU headroom matters when features are layered together
Motion analysis, decoding, exports, web serving and other processing can occur at the same time. A CPU that looks comfortable during quiet periods may become saturated when multiple cameras trigger, users review clips and AI jobs queue together.
That is why the calculator uses a planning tier rather than a single utilization target. Final acceptance should come from a multi-hour test with realistic traffic and alerts.
Intel integrated graphics can reduce video-processing work
Blue Iris 6 integrates Intel QSV/oneVPL paths for hardware-assisted video processing. Intel also notes that Quick Sync depends on supported processor graphics being enabled.
Do not disable the iGPU simply because a discrete GPU is installed without checking the desired Blue Iris path. Verify the exact processor in Intel specifications and confirm the integrated graphics remains visible to Windows.
NVIDIA graphics are optional, not a mandatory checklist item
Blue Iris lists NVIDIA graphics as optional, while version 6 integrates NVIDIA NVENC for supported video encoding paths. A discrete GPU can therefore be useful for specific workloads without being required for every recorder.
The GPU decision should consider built-in AI, exports, encoding, available PCIe slots, PSU capacity and chassis airflow. A low-profile business desktop may impose stricter card-size and power limits than a tower.
Memory should cover cameras plus the operating environment
The current Blue Iris recommended guidance mentions approximately 1GB RAM per high-megapixel camera. That is a useful signal that camera resolution affects memory, but Windows and the rest of the recorder also need RAM.
Built-in AI can create additional memory pressure, especially when requests queue. Choose a standard memory tier with headroom rather than trying to purchase an exact gigabyte calculation.
Storage has three separate requirement questions
The Windows/application drive needs low latency and modest capacity. The Blue Iris database benefits from responsive storage. The video archive needs sustained writes, capacity and predictable retention.
A single disk can perform more than one role, but separating the roles makes scaling and troubleshooting easier. Surveillance HDDs are purpose-built for continuous recording workloads, while SSDs are useful for the system/database layer.
The network requirement comes from aggregate camera bitrate
Add all camera bitrates to find the main inbound stream load. Then account for playback, exports, remote viewers and any network storage path.
A gigabit link has far more practical capacity than many small installations use, so 10GbE is not a default requirement. Upgrade only when the measured aggregate or storage workflow justifies it.
PoE requirements are electrical as well as logical
A 16-port PoE switch does not guarantee that all 16 cameras can draw their maximum power simultaneously. The total power budget and per-port PoE standard must match the camera fleet.
Cameras with heaters, long-range IR or PTZ motors can demand more than fixed indoor models. Verify the exact watt requirement for each camera and keep reserve for startup and future additions.
Retention and redundancy are different requirements
Thirty days of retention answers how much footage must remain online. Redundancy or backup answers what happens when a drive or recorder fails. They should not be combined into one capacity number.
Decide how critical the footage is. Important evidence may justify a second copy, export workflow or independent backup even when the main recorder has plenty of free disk space.
Acceptance testing should reproduce the production workload
Use the Blue Iris evaluation or a controlled deployment to test all cameras, actual codecs, actual AI settings and simultaneous viewing. A synthetic CPU benchmark cannot reproduce every part of the recorder.
Record baseline utilization and temperatures so future changes can be compared. When a new camera, AI model or retention change pushes the system harder, you will know which resource moved first.
Questions people ask
Blue Iris Hardware Requirements questions
What are the minimum Blue Iris requirements?
The current official page lists a newer Intel processor, 8GB or more RAM, Windows 10 64-bit or equivalent server, and camera input hardware. Check the Blue Iris site for the latest wording before deployment.
What hardware does Blue Iris recommend?
Blue Iris currently recommends an Intel Core or Ultra processor, additional memory for high-megapixel cameras, Windows 11 64-bit, optional NVIDIA graphics, and 7200+ RPM and/or SSD storage.
Does Blue Iris need Windows?
Yes. Blue Iris is Windows video-management software and its published requirements specify 64-bit Windows.
How much CPU do 16 cameras need?
There is no official universal CPU for 16 cameras. Resolution, FPS, codec, substreams, AI and remote use determine the real load.
How much storage do Blue Iris cameras use?
Use actual average bitrate. One megabit per second recorded continuously is roughly 10.8GB per day before filesystem and reserve considerations.
Does H.265 reduce hardware requirements?
It can reduce bitrate for comparable quality, but decode and encode support also matters. Verify the exact camera stream and hardware acceleration path rather than assuming H.265 is always lighter.
Do substreams matter?
Yes. Proper substreams can reduce the amount of full-resolution video that must be decoded for routine display or analysis, depending on configuration.
Does built-in AI require a GPU?
Not universally. Blue Iris 6 includes built-in AI, and hardware needs depend on the number and complexity of AI requests. Test the intended AI workload on the exact hardware.
Should I use a surveillance HDD?
For continuous high-write recording, surveillance HDDs are specifically designed for that workload. Verify capacity, interface and model instead of buying by color or family name alone.
What should I monitor after installation?
Watch CPU, RAM, GPU, disk activity, dropped or delayed frames, network utilization, temperatures and Blue Iris logs during the busiest periods.
Official references and methodology
Verify the exact Blue Iris and hardware behavior
The page separates official minimum/recommended Blue Iris requirements from Cloudzat workload planning. Derived storage uses the bitrate entered by the visitor, and compute recommendations remain directional because Blue Iris performance varies with codecs, substreams, AI, viewing and hardware acceleration.
- Blue Iris Official Site and System Requirements
- Blue Iris Version 6 Updates and Hardware Acceleration
- Blue Iris 6.0.1 Built-in AI Notes
- Intel Quick Sync Video Verification
As an Amazon Associate, Cloudzat may earn from qualifying purchases. Prices, model revisions, CPU/GPU capabilities, drive specifications, PoE budgets and marketplace conditions can change. Verify the exact part before purchase.