Continuous channel and playlist downloads can accumulate far more storage than Pinchflat itself consumes.
Long-term YouTube archive users.Requisitos de hardware do Pinchflat: RAM, CPU, armazenamento e yt-dlp
Conheça os requisitos do Pinchflat em termos de CPU, RAM, SQLite, yt-dlp, armazenamento para transferências e simultaneidade e, em seguida, escolha o hardware ZimaOS adequado.
Pinchflat requirements at a glance
Pinchflat does not publish a numerical CPU or RAM minimum. Upstream describes it as a lightweight, self-contained YouTube media manager built around yt-dlp in one Docker container. The real hardware requirement is usually download storage and post-download processing rather than the web UI.
- CPU
- No numerical official minimum. Normal scheduling/UI work is light; yt-dlp extraction, remuxing/post-processing and custom scripts can add CPU work.
- RAM
- No numerical official minimum. Current default yt-dlp worker concurrency is 2, so memory/network/processing pressure grows with concurrent jobs.
- Database
- Pinchflat uses SQLite in /config. Upstream prefers local config storage because WAL mode is not well suited to network shares.
- Storage
- Downloaded media under /downloads is the main capacity driver. Long-lived channel/playlist archives can grow rapidly.
- Port
- Current official Docker examples expose port 8945.
- Best Zima starting point
- ZimaBoard 2 832 is ample for normal Pinchflat. ZimaCube becomes useful when YouTube archives and backups need multi-drive capacity.
From official requirements to the right setup
Pinchflat sizing starts with archive volume and concurrent yt-dlp work.
-
Official requirements
Keep /config on local persistent storage when possible. Upstream warns that SQLite WAL mode and network shares are a poor combination.
-
Confirm your needs
Estimate how many channels/playlists and how much media you will retain. Downloaded video/audio capacity will dominate disk usage far before the app database does.
-
Leave room to grow
Leave YT_DLP_WORKER_CONCURRENCY at the default 2 unless you have a clear reason to change it; upstream specifically recommends lowering it to 1 when IP-limited.
-
Run it on ZimaOS
Install Pinchflat from ZimaOS, run representative channel/playlist downloads and monitor network, CPU and disk growth before increasing concurrency or storage.
Check every playback client
- Number of channels/playlists
- Video/audio quality
- Retention and auto-delete rules
- yt-dlp worker concurrency
- Local /config storage
- SQLite journal mode
- /downloads capacity
- Media-center import workflow
Official minimum requirements
Pinchflat upstream calls the app lightweight and self-contained but does not publish a universal host CPU/RAM minimum.
Do not manufacture a RAM number. Storage and concurrent downloads/post-processing are much more important than the base web process.
| Requirement | Official minimum | What this supports |
|---|---|---|
| CPU | No numerical minimum published | yt-dlp/post-processing and custom scripts determine heavier CPU use. |
| RAM | No numerical minimum published | Worker concurrency and post-processing determine practical peaks. |
| Container | Single self-contained Docker container | Current upstream deployment model. |
| Port | 8945 | Current official Docker example. |
| Default yt-dlp concurrency | 2 workers per queue | Current YT_DLP_WORKER_CONCURRENCY default. |
| GPU | Not required | Pinchflat does not document a dedicated-GPU requirement. |
When to upgrade your hardware
Upgrade Pinchflat when download storage, processing or combined media-server workload proves the current host insufficient.
The YouTube archive grows beyond attached storage
Concurrent downloads/post-processing create sustained CPU or disk load
Pinchflat shares the host with Plex/Jellyfin and other media apps
Multiple yt-dlp jobs can overlap network writes and media post-processing, especially with higher quality media or custom options.
Users archiving many active channels.Media scanning, thumbnails, transcoding and downloads can overlap, so the combined stack may justify more memory and faster storage.
All-in-one media servers.Plan hardware growth with confidence
Scale Pinchflat by controlling concurrency and separating appdata from bulk media.
Keep /config local
Upstream recommends local config storage because SQLite WAL mode on a network share can be unsafe or slow.
Use local eMMC/SSD/NVMe for /config.Use network or multi-drive storage for /downloads when capacity grows
The media archive can be placed separately from the lightweight application config.
Use capacity-oriented HDD/NAS storage for retained videos.Tune retention and redownload rules
Pinchflat supports automatic deletion and redownload policies, which can materially change long-term storage growth.
Software retention policy can delay or eliminate a storage upgrade.Keep yt-dlp concurrency conservative
The default is 2 workers per queue and upstream advises 1 when IP-limited.
Higher concurrency should be justified by real throughput needs rather than enabled automatically.Can it run on ZimaOS?
Pinchflat is currently available in the ZimaOS App Store under Media.
Install Pinchflat from ZimaOS
Use the packaged YouTube media manager with persistent /config and /downloads paths.
Open Pinchflat in the ZimaOS App StoreKeep SQLite config storage local when possible
Current upstream guidance warns about SQLite WAL mode on network shares and provides JOURNAL_MODE=delete only as an advanced workaround.
Read Pinchflat Docker storage guidanceUse current yt-dlp worker controls
The current container exposes YT_DLP_WORKER_CONCURRENCY with a default of 2 and advises lowering it when IP-limited.
Read Pinchflat environment variablesChoose Zima hardware for Pinchflat
Pinchflat is lightweight as an application; archive storage and the broader media stack are the main reasons to move beyond ZimaBoard 2.
Are you downloading a modest set of channels or building a large long-term archive?
Normal personal/family Pinchflat archive
ZimaBoard 2 832 provides ample compute and dual 2.5GbE for normal download jobs.
- Normal Pinchflat serverZimaBoard 2 832
- More media apps/download headroomZimaBoard 2 1664
Large multi-drive YouTube archive
Use ZimaCube when retained video capacity and backups drive the server design.
- Multi-drive YouTube archiveZimaCube 2 Standard
- Larger media/archive stackZimaCube 2 Pro
No fixed download speed, archive size or concurrent-job guarantee is implied. YouTube behavior, yt-dlp version, quality, post-processing, storage and network all matter.
| Zima hardware | Best for | Example workload | Core configuration | Recommended boundary | Next step |
|---|---|---|---|---|---|
| ZimaBoard 2 832 | A normal Pinchflat YouTube archive. | Scheduled yt-dlp downloads, metadata and media-center handoff. |
|
Retained media capacity can outgrow the board long before Pinchflat needs more RAM. | Get Now |
| ZimaBoard 2 1664 | Pinchflat plus a larger media/download stack. | More concurrent services and processing headroom. |
|
16 GB does not reduce YouTube throttling/IP limits. | Get Now |
| ZimaCube 2 Standard | A large multi-drive Pinchflat archive. | Long-term video/audio storage, backups and media-center integration. |
|
Choose it primarily for storage capacity. | Get Now |
| ZimaCube 2 Pro | A larger all-in-one download/media server. | More media apps, stronger CPU, multi-drive storage and 10GbE-capable workflows. |
|
Pinchflat alone does not justify the Pro tier. | 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
FAQ topics follow query fan-out around RAM, yt-dlp concurrency, SQLite, network shares, storage growth and media-server integration.
How much RAM does Pinchflat need?
Pinchflat does not publish a RAM minimum. Upstream describes it as lightweight and self-contained, while actual peaks depend on concurrent yt-dlp jobs and post-processing.
Does Pinchflat need a database server?
No. It uses SQLite inside /config.
Can Pinchflat /config live on NFS or SMB?
Upstream prefers local storage because SQLite WAL mode does not behave well on network shares. JOURNAL_MODE=delete is provided only as an advanced workaround.
How many yt-dlp workers should Pinchflat use?
The current default is 2 workers per queue. Upstream advises setting it to 1 if you are being IP-limited and otherwise generally leaving it alone.
Does Pinchflat transcode video?
Pinchflat is built around yt-dlp and can perform media post-processing/remuxing according to download options, but it is not a Plex/Jellyfin playback transcoder.
Can ZimaBoard 2 832 run Pinchflat?
Yes. Its N150 and 8 GB RAM provide substantial headroom for normal Pinchflat use.
What is the main Pinchflat storage requirement?
The downloaded media archive under /downloads. Long-term channel and playlist retention can grow much faster than the application database.
When is ZimaCube 2 useful for Pinchflat?
When long-term YouTube video/audio storage and backups need multiple drive bays or Pinchflat is part of a larger media server.
What sources and further reading informed this Pinchflat hardware guide?
The official Pinchflat repository defines the lightweight single-container architecture, /config and /downloads paths, SQLite network-share warning, port 8945 and yt-dlp worker concurrency. ZimaOS confirms the current Media app.
