Use native camera events and compatible streams where possible; measure actual conversion and detection load before upgrading.
Cameras without suitable codecs or motion support.متطلبات أجهزة Scrypted: ذاكرة الوصول العشوائي (RAM)، والمعالج (CPU)، والتخزين وNVR، والكاميرات وتخزين التسجيلات
خطّط لأجهزة Scrypted لربط الكاميرات وتشغيل مسجل فيديو شبكي (NVR)، مع مراعاة متطلبات أقراص التسجيل الرسمية وتسريع الفيديو والشبكات السلكية وحدود ZimaOS.
APP
Scrypted hardware requirements at a glance
Scrypted camera bridging and Scrypted NVR have different hardware profiles. NVR requires at least a 1 TB drive; official Linux NVR guidance uses a sixth-generation Intel-equivalent baseline, while software motion and per-camera detection add compute work.
- RAM
- No numerical official minimum published. for the base host in the reviewed requirements. Size the selected plugins, software motion, detection and NVR workload separately.
- CPU
- For Linux NVR, official baseline guidance is sixth-generation Intel or AMD equivalent; Windows guidance is ninth-generation Intel or equivalent. These are recommendations, not universal core-count requirements.
- Storage
- Official Scrypted NVR requirement: a drive of at least 1 TB. Base camera bridging does not inherit that recording-drive requirement; retain configuration separately.
- Video / detection
- Camera-native H.264, motion events and supported plugins can avoid expensive conversion. Hardware decoding/detection needs compatible device pass-through.
- Network / host
- Wired Ethernet is required by the system requirements. Proxmox VE is preferred for dedicated Intel/AMD servers; the documented Linux Docker host is Ubuntu Server 24.04 LTS.
- Best Zima starting point
- ZimaBoard 2 832 is a candidate for modest camera bridging with compatible streams. For NVR, add a ≥1 TB recording drive and validate hardware acceleration; choose a larger system for retention and processing.
From official requirements to the right setup
Plan the complete Scrypted workload before selecting a server.
-
Official requirements
Decide whether you need camera bridging only or the separate Scrypted NVR product. Apply the NVR storage and CPU-generation recommendations only to the NVR workload.
-
Confirm your needs
List local RTSP cameras, codecs, native motion capabilities and simultaneous viewers. Account for software motion/detection and transcodes instead of assuming every camera is a cheap passthrough stream.
-
Leave room to grow
Persist the application state and back it up. For NVR, provision at least a 1 TB recording drive with an appropriate sustained-write profile; calculate additional capacity from bitrate and retention.
-
Run it on ZimaOS
Use the ZimaOS Custom Install route only after reviewing the official Docker configuration. ZimaOS is outside the named Ubuntu Docker-host recommendation; validate discovery/networking, GPU access and storage, or use the documented dedicated-host approach.
Check every playback client
- Bridging only versus Scrypted NVR
- Camera-native codec and motion support
- Local RTSP/ONVIF camera compatibility
- Simultaneous viewers and transcodes
- Wired Ethernet connectivity
- NVR recording drive at least 1 TB
- GPU driver and device pass-through
- Documented host OS versus ZimaOS validation
Official minimum requirements
Checked on October 23, 2026 against official documentation and the project repository. Latest stable release observed: v0.147.0. Numerical requirements below retain their original scope.
Do not apply the NVR 1 TB drive requirement to a bridge-only deployment or treat the example N100 camera count as a promise for every N150 system. ZimaOS container deployment must be validated against upstream host, networking and accelerator assumptions.
| Requirement | Official minimum | What this supports |
|---|---|---|
| Base-host RAM | No numerical official minimum published. | The reviewed requirements do not define one RAM minimum covering all plugins and NVR workloads. |
| NVR recording drive | At least 1 TB | An explicit NVR requirement; flash drives and SD cards are unsuitable for sustained recording. |
| Linux NVR CPU baseline | Sixth-generation Intel or AMD equivalent | Official baseline recommendation; not a guaranteed camera count. |
| Windows NVR CPU baseline | Ninth-generation Intel or AMD equivalent | Keep this platform-specific recommendation distinct from Linux sizing. |
| Network | Wired connection required | The requirements recommend disabling wireless networking on the server. |
| Host / runtime | Proxmox preferred for dedicated Intel/AMD; Linux Docker guidance names Ubuntu Server 24.04 LTS | Docker Desktop on Windows/macOS is unsupported by the Docker guide; ZimaOS is not the named recommended Docker host. |
| Container / camera support | Official ghcr.io/koush/scrypted image; NVR officially supports local RTSP cameras | Use supported camera codecs/plugins; NVIDIA deployments require the matching image and host runtime. |
When to upgrade your hardware
Use observed Scrypted workload pressure to decide when an upgrade is warranted.
Software motion or transcodes saturate compute
More plugins and viewers create contention
Recording retention exceeds the drive budget
Inspect process memory, simultaneous stream conversions and device utilization under a representative busy period.
Camera bridging combined with NVR and other containers.Start at the official NVR drive floor, then size from aggregate bitrate and desired days. A 1 TB floor does not guarantee a particular retention period.
Multi-camera continuous recording.Plan hardware growth with confidence
Address storage, memory, compute and deployment limits separately.
Use a dedicated recording drive
Separate persistent application state from a drive provisioned for NVR writes and retention.
At least 1 TB storage added to ZimaBoard 2 for NVR.Add host memory when measurements justify it
Choose more RAM when plugins and other services cause pressure, without assuming the CPU also improves.
ZimaBoard 2 1664.Expand retained video capacity
Choose multi-drive capacity for the desired retention, plus a backup of application configuration and important exports.
ZimaCube 2 Standard.Increase compute only after validating the pipeline
Check hardware acceleration, codecs and native motion first. Use a documented host topology if ZimaOS cannot provide the needed device/network behavior.
ZimaCube 2 Pro or a dedicated upstream-recommended host.Can it run on ZimaOS?
No specific public official one-click ZimaOS Scrypted page was verified. Upstream prefers Proxmox VE for dedicated Intel/AMD servers and recommends Ubuntu 24.04 for Docker; do not describe ZimaOS as a certified upstream host.
Custom install Scrypted in ZimaOS
Use Custom Install only with a review of the official image, persistent state, camera discovery, host-network assumptions and accelerator pass-through. If these requirements cannot be met, use the upstream-documented host topology.
Custom install Scrypted in the ZimaOS app ↗Use the official Scrypted deployment instructions
Keep the selected stable release, persistent paths and companion services aligned with upstream documentation.
Review Scrypted official installation ↗Preserve upstream host and runtime requirements
Review the official Linux Docker guide, including unsupported Docker Desktop and NVIDIA image/runtime differences.
Review Scrypted deployment details ↗Which Zima hardware fits Scrypted?
Start with the lowest reasonable host for the actual workload. Product specifications were checked against the current product pages.
Which workload best matches your Scrypted deployment?
Camera bridging with compatible native streams
Start modestly and validate plugins, discovery and wired networking.
- Workload optionZimaBoard 2 832
- Workload optionZimaBoard 2 1664
Scrypted NVR and longer recording retention
Provision the required drive capacity and validate the full video/detection pipeline.
- Workload optionZimaCube 2 Standard
- Workload optionZimaCube 2 Pro
These are practical workload recommendations, not official app requirements, compatibility certification, measured capacity limits or performance guarantees. Include all co-hosted services and independent backups.
| Zima hardware | Best for | Example workload | Core configuration | Recommended boundary | Next step |
|---|---|---|---|---|---|
| ZimaBoard 2 832 | Modest camera bridging | Compatible native camera streams and selected plugins. |
|
ZimaOS is not the named upstream Docker-host recommendation; compatibility must be validated. | Get Now |
| ZimaBoard 2 1664 | More plugin and shared-app headroom | Bridge/NVR services with appropriate ≥1 TB recording storage when NVR is used. |
|
More RAM does not guarantee camera capacity or resolve unsupported codecs/drivers. | Get Now |
| ZimaCube 2 Standard | NVR recording capacity | Multi-drive retention and a modest compatible stream workload. |
|
Base 8 GB RAM and device/host compatibility still need assessment; six bays do not define camera throughput. | Get Now |
| ZimaCube 2 Pro | Heavier video and mixed services | More processing headroom with larger recording capacity. |
|
Do not infer guaranteed camera counts from a different CPU model in upstream example charts. | Get Now |
What the Press Says
Highlights from trusted reviewers worldwide.
“ZimaCube 2: Not just another NAS, tested with 25TB storage, local AI agents, 4K transcoding, and real homelab workflows.”Read full review
“The ZimaBoard 2 is a compact x86 server board that can be turned into a mini NAS, home server, media box, or self-hosting hub.”Read full review
“ZimaCube 2: A modern, high-performance NAS with plenty of room to grow—built for users who want more than basic storage.”Read full review
“Coverage focused on ZimaCube 2's open hardware foundation, no monthly fee, and self-hosting flexibility.”Read full review
Loved by the Community
Stories and reviews from people who build with Zima every day.
★★★★★
Zima Blade Little yet Powerful
Maybe I am not digital natives but I live with PCs since 12 years old in 1984 when IBM PC clone come to my home. Many years have passed and many operating system I've tried. For me Zima blade and CasaOS was a quantum leap for home PC enthusiast and server lab machine to make me stay curious and relevant for this era.
★★★★★
Very good!!
I use ZimaCube Pro as 5th Proxmox cluster node. It runs several VMs and containers, including a VM with GPU passthrough to run a self-hosted LLM. A specific LXC container runs a Samba server for NAS capabilities using four of six RAID 6 SATA HDDs with ZFS.
★★★★★
Great innovation for mini server!
It is very useful and makes a powerful mini server for many purposes, including university and college students in engineering and electronics. Thank you so much for making this server.
★★★★★
Avaliação ZimaBoard 2
Construí um servidor de uso pessoal. O desempenho está muito bom e funciona perfeitamente onde quer que eu esteja. A surpresa é não dependermos de grandes estruturas para termos nosso próprio servidor de dados. Como iniciante, estou gostando bastante do ZimaOS, pois ele é simples e eficiente.
Frequently asked questions
Answers to Scrypted RAM, CPU, storage, Docker, database and ZimaOS sizing questions.
How much RAM does Scrypted require?
No numerical official minimum published. covering every base/plugin/NVR setup. Evaluate memory with your actual plugins and cameras; example machines in the guide are workload references.
Does Scrypted have a CPU-generation requirement?
For NVR, the system requirements recommend sixth-generation Intel or equivalent AMD on Linux, and ninth-generation Intel or equivalent on Windows. This is distinct from a universal number of CPU cores.
Do bridging and NVR need the same hardware?
No. Bridging compatible camera streams can be modest; NVR, software motion and object detection increase per-camera work and require recording storage.
Does Scrypted NVR really require a 1 TB drive?
Yes. The official requirements state a drive of at least 1 TB is required for NVR. Size beyond that from bitrate and retention, and avoid flash drives or SD cards for sustained recording.
Does every Scrypted installation need a discrete GPU?
No. Supported integrated graphics and compatible camera streams may be suitable. Detection/transcoding support depends on platform, drivers and container pass-through; NVIDIA requires the documented image/runtime.
Can I install Scrypted on ZimaBoard 2 with ZimaOS?
A Custom Install is a candidate deployment, not an upstream host-support guarantee. Scrypted prefers Proxmox for dedicated Intel/AMD and names Ubuntu 24.04 for Linux Docker. Validate networking, discovery, camera compatibility and device access.
Can I use cloud or battery cameras with Scrypted NVR?
The NVR requirements officially support local RTSP cameras, typically ONVIF/RTSP with H.264. Cloud, battery and non-native RTSP cameras are listed as unsupported even if some integrations work to varying degrees.
When should I choose ZimaCube 2?
Choose it for a deliberate recording-capacity or measured processing requirement. Standard emphasizes storage; Pro adds compute headroom, but neither removes host, codec or driver compatibility checks.
What sources informed this Scrypted hardware guide?
Official project requirements, installation/configuration documentation, repository/release information and the current Zima product pages were checked on October 23, 2026. Practical hardware recommendations are editorial sizing guidance rather than upstream minimums.
