Concurrent FFmpeg, LibreOffice or ImageMagick processes can multiply CPU/RAM use quickly.
Batch conversion workloads.Requisitos de hardware de ConvertX: RAM, CPU, almacenamiento e implementación
Planifica el hardware de ConvertX para la RAM, la CPU, las conversiones simultáneas, FFmpeg, LibreOffice y los archivos temporales, con orientación directa de la App Store de ZimaOS.
ConvertX requirements at a glance
ConvertX is a self-hosted multi-format file converter. Upstream publishes no numerical host CPU/RAM minimum; conversion type and concurrency drive resources, while ZimaOS currently lists 500 MB minimum memory for its package.
- Upstream RAM minimum
- No numerical whole-host minimum published.
- ZimaOS package memory
- Current official ZimaOS listing: 500 MB minimum memory.
- CPU
- No numerical official core minimum. FFmpeg, LibreOffice, ImageMagick, Calibre and other converters can create heavy CPU bursts.
- Concurrency
- MAX_CONVERT_PROCESS controls simultaneous conversion processes; 0 means unlimited and can overcommit a small server.
- Storage
- Persistent /app/data stores app data and conversion history; temporary/output files and batch jobs can create bursty disk use.
- Best Zima starting point
- ZimaBoard 2 1664 is a safer compact choice for mixed conversions; ZimaCube 2 Pro is better for frequent video/document batches.
From official requirements to the right setup
Size ConvertX from the real workload and deployment topology rather than generic server assumptions.
-
Official requirements
Install ConvertX from the official ZimaOS App Store and persist /app/data.
-
Confirm your needs
Treat the ZimaOS 500 MB memory value as package metadata, not as an upstream universal conversion requirement.
-
Leave room to grow
Set MAX_CONVERT_PROCESS to a conservative value so simultaneous FFmpeg/LibreOffice/ImageMagick jobs do not exhaust RAM or CPU.
-
Run it on ZimaOS
Use HTTPS for normal remote access; upstream warns that login may fail over plain non-local HTTP unless HTTP_ALLOWED is explicitly enabled.
Check every playback client
- 500 MB package memory
- MAX_CONVERT_PROCESS
- Video/document formats
- Temporary file size
- /app/data storage
- HTTPS
- Port 3000
- Backup/auto-delete policy
Official minimum requirements
ConvertX upstream documents deployment and converter behavior but no numerical host hardware minimum; ZimaOS adds package-level minimum-memory metadata.
Do not treat 500 MB as sufficient for every conversion workload. A single heavy FFmpeg or LibreOffice job can use substantially more CPU/RAM than the idle web service.
| Requirement | Official minimum | What this supports |
|---|---|---|
| Upstream host RAM minimum | No numerical minimum published | Depends on active converter and concurrency. |
| ZimaOS package minimum memory | 500 MB | Current public App Store metadata. |
| Port | 3000 | Current upstream Docker deployment. |
| Persistent data | /app/data | Current upstream Docker volume. |
| Concurrent process control | MAX_CONVERT_PROCESS | 0 means unlimited. |
| GPU acceleration | Optional for FFmpeg | FFMPEG_ARGS/OUTPUT_ARGS can enable supported hardware acceleration. |
When to upgrade your hardware
Scale ConvertX when these workload signals appear.
Multiple conversions run at once
Video conversion becomes frequent
Large temporary/history files accumulate
FFmpeg workloads can make CPU the dominant bottleneck.
Media-heavy use.Conversion jobs can create significant disk usage until cleanup runs.
Large-file and batch workflows.Plan hardware growth with confidence
Scale ConvertX only where the workload justifies additional resources.
Limit concurrent conversions first
Controlling MAX_CONVERT_PROCESS is often more effective than immediately buying more hardware.
Useful on all Zima hardware.Use 16 GB for mixed conversion workloads
Extra RAM helps large documents, image tools and concurrent jobs coexist.
ZimaBoard 2 1664.Use SSD/NVMe for temporary/output data
Large conversion files benefit from low-latency storage.
Use SATA/NVMe with ZimaBoard 2 or ZimaCube SSD tiers.Use stronger CPU for frequent FFmpeg/LibreOffice batches
Heavy conversion benefits from more cores and sustained CPU performance.
ZimaCube 2 Pro.Can it run on ZimaOS?
ConvertX deployment on ZimaOS should follow the verified route below.
Install ConvertX from the ZimaOS App Store
Install the current ConvertX package directly from ZimaOS, persist app data and keep conversion concurrency appropriate for the host.
Install ConvertX from the ZimaOS App Store ↗Review ConvertX upstream deployment
Use upstream documentation to understand ports, persistence and feature-specific requirements.
Review ConvertX upstream deployment ↗Keep persistent data outside disposable containers
Map configuration, database or uploaded-file paths to durable ZimaOS storage where the app uses persistent state.
Review ZimaOS download and app platform ↗Choose Zima hardware for ConvertX
ConvertX is bursty rather than continuously heavy; conversion type and concurrency matter much more than idle memory usage.
Which ConvertX workload are you running?
Occasional documents/images
Use ZimaBoard 2 832 or 1664 with limited concurrency.
- Light useZimaBoard 2 832
- Safer mixed workloadZimaBoard 2 1664
Frequent video/batch conversion
Use stronger CPU and fast SSD storage.
- Higher-processing headroomZimaCube 2 Pro
The ZimaOS 500 MB package value is not a guarantee for every converter or file size.
| Zima hardware | Best for | Example workload | Core configuration | Recommended boundary | Next step |
|---|---|---|---|---|---|
| ZimaBoard 2 832 | Occasional image/document conversion. | Single or low-concurrency jobs. |
|
Large video/LibreOffice jobs can exceed comfortable headroom. | Get Now |
| ZimaBoard 2 1664 | Mixed personal/team conversion. | More concurrent documents/images and moderate media conversion. |
|
N150 CPU can still be slow for heavy FFmpeg. | Get Now |
| ZimaCube 2 Pro | Frequent batch/video conversion. | More cores, 16 GB RAM and faster storage/network paths. |
|
Actual speed depends on converter and source formats. | 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
These answers cover ConvertX RAM, CPU, storage and ZimaOS deployment.
How much RAM does ConvertX need?
Upstream does not publish a universal host minimum; the current ZimaOS package lists 500 MB minimum memory.
How many CPU cores does ConvertX need?
No numerical official core minimum is published; converters such as FFmpeg and LibreOffice determine CPU demand.
How can I limit ConvertX resource use?
Set MAX_CONVERT_PROCESS to cap simultaneous conversion processes.
Does ConvertX need persistent storage?
Yes. The official Docker deployment maps /app/data.
Does ConvertX need HTTPS?
HTTPS is the normal safe deployment path; upstream warns that plain non-local HTTP may require HTTP_ALLOWED=true.
Does ConvertX require a GPU?
No, but FFmpeg hardware acceleration can be configured where supported.
Can ZimaBoard 2 run ConvertX?
Yes. Use the 16 GB model for a safer mixed-conversion workload.
Is ConvertX available in ZimaOS App Store?
Yes. A public official ZimaOS App Store page is available.
What sources informed this ConvertX hardware guide?
Current ConvertX ZimaOS listing and upstream deployment documentation plus current Zima product pages.
