Chromium/Playwright jobs are much heavier than saving bookmark metadata.
Users preserving many pages with screenshots/PDFs.Hardwarevereisten voor Linkwarden: RAM, CPU, opslag en archivering
Leer meer over de vereisten van Linkwarden voor CPU, RAM, PostgreSQL, MeiliSearch, browserarchivering en opslag en kies vervolgens geschikte ZimaOS-hardware.
Linkwarden requirements at a glance
Linkwarden does not publish a universal CPU or RAM minimum. The current official Docker Compose stack includes Linkwarden, PostgreSQL 16 and MeiliSearch. Browser-based preservation can also generate screenshots, PDFs, readable text and monolith archives, so archiving is much heavier than simple bookmark browsing.
- CPU
- No numerical official minimum. Browser preservation and indexing are the main compute bursts.
- RAM
- No numerical official minimum. The full stack includes Linkwarden, PostgreSQL, MeiliSearch and optional local Chromium/Playwright work.
- Database
- PostgreSQL is required by the current default Compose deployment.
- Search
- The current default Compose includes MeiliSearch.
- Archive storage
- Archives, previews and uploads are stored locally unless S3-compatible storage is configured.
- Best Zima starting point
- ZimaBoard 2 832 suits normal personal use; 16 GB or ZimaCube is more useful for heavier preservation and long-term archive storage.
From official requirements to the right setup
Size Linkwarden from preservation and archive volume, not bookmark count alone.
-
Official requirements
Account for the whole stack: Linkwarden, PostgreSQL and MeiliSearch.
-
Confirm your needs
Estimate preservation intensity: browser jobs can generate screenshots, PDFs, readable text and monolith HTML.
-
Leave room to grow
Plan archive storage separately from the database; S3-compatible storage is optional.
-
Run it on ZimaOS
Run a representative import/preservation workload and monitor memory, indexing and archive growth before upgrading.
Check every playback client
- Saved link count
- Browser preservation
- Screenshot/PDF/monolith formats
- Archive batch size
- PostgreSQL
- MeiliSearch
- Local vs S3 storage
- AI tagging/RSS polling
Official minimum requirements
Linkwarden documents its stack and preservation controls but no universal host CPU/RAM minimum.
A metadata-only bookmark server and a preservation-heavy archive server are fundamentally different workloads.
| Requirement | Official minimum | What this supports |
|---|---|---|
| CPU | No numerical minimum published | Browser preservation/indexing create the main peaks. |
| RAM | No numerical minimum published | Full stack includes app, PostgreSQL and MeiliSearch. |
| Database | PostgreSQL 16 in current Compose | Current official repository compose. |
| Search | MeiliSearch 1.13.3 in current Compose | Current official repository compose. |
| App port | 3000 | Current Compose mapping. |
| GPU | Not required | AI tagging can call remote providers or a separately sized Ollama backend. |
When to upgrade your hardware
Upgrade when preservation, search or archive storage is measurably constrained.
Browser archiving pushes memory high
Search/index workload grows
Archive files outgrow local storage
MeiliSearch and PostgreSQL run alongside Linkwarden and need additional headroom as collections grow.
Large multi-user collections.Screenshots, PDFs and full-page archives can dominate disk use.
Long-term web archives.Plan hardware growth with confidence
Scale browser work, search and archive storage independently where useful.
Use remote Chromium
PLAYWRIGHT_WS_URL lets Linkwarden connect to a remote browser.
Moves browser CPU/RAM to another host.Use S3-compatible storage
Archives, previews and uploads can live on S3/MinIO-style storage.
Useful when local capacity is limiting.Disable browser preservation when unnecessary
DISABLE_BROWSER skips browser-dependent tasks.
Makes bookmark-only deployments much lighter.Keep database/search on responsive storage
PostgreSQL and MeiliSearch benefit from low-latency persistent storage.
Use SSD/NVMe for appdata.Can it run on ZimaOS?
Linkwarden is currently available in the ZimaOS App Store under Productivity.
Install Linkwarden from ZimaOS
Use the packaged collaborative bookmark and preservation app.
Open Linkwarden in the ZimaOS App StoreAccount for the current full Compose stack
The official repository currently defines PostgreSQL and MeiliSearch alongside Linkwarden.
Read Linkwarden Docker ComposeTune browser/search/storage independently
Current environment variables expose preservation, MeiliSearch and S3-compatible storage separately.
Read Linkwarden environment variablesChoose Zima hardware for Linkwarden
Linkwarden can be light for bookmarks, but full preservation makes it a browser/search/archive stack.
Bookmark manager or preservation-heavy archive?
Normal personal/family use
ZimaBoard 2 832 provides useful headroom for the full stack.
- Normal Linkwarden serverZimaBoard 2 832
- More preservation/search headroomZimaBoard 2 1664
Large archive
Use ZimaCube when archive capacity drives the design.
- Multi-drive archive serverZimaCube 2 Standard
- Larger archive/search stackZimaCube 2 Pro
No fixed link-count or archive-rate guarantee is implied.
| Zima hardware | Best for | Example workload | Core configuration | Recommended boundary | Next step |
|---|---|---|---|---|---|
| ZimaBoard 2 832 | Normal Linkwarden server. | Bookmarking plus moderate preservation. |
|
Heavy simultaneous browser preservation can be the limit. | Get Now |
| ZimaBoard 2 1664 | Larger Linkwarden collection. | More preservation/indexing headroom. |
|
Archive capacity may still require external storage. | Get Now |
| ZimaCube 2 Standard | Large long-term web archive. | Preservation plus multi-drive storage. |
|
Choose primarily for storage. | Get Now |
| ZimaCube 2 Pro | Larger preservation/search/archive platform. | More CPU, RAM and storage services. |
|
Very heavy Chromium concurrency may still benefit from remote browser workers. | 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 cover RAM, PostgreSQL, MeiliSearch, Chromium preservation and archive storage.
How much RAM does Linkwarden need?
Linkwarden does not publish a host RAM minimum; the current stack includes the app, PostgreSQL and MeiliSearch, with browser preservation adding transient peaks.
Does Linkwarden require PostgreSQL?
Yes in the current official self-hosted stack.
Does Linkwarden require MeiliSearch?
The current official Compose includes MeiliSearch for indexing/search.
Why can archiving use much more RAM?
Preservation can launch Chromium/Playwright and generate screenshots, PDFs, readable text and monolith archives.
Can Linkwarden use a remote browser?
Yes, through PLAYWRIGHT_WS_URL.
Can archives be stored on S3 or MinIO?
Yes. Current environment variables support S3-compatible object storage.
Can ZimaBoard 2 832 run Linkwarden?
Yes for a normal personal/family instance with moderate preservation.
When is ZimaCube 2 useful?
When preserved content and backups make multi-drive archive capacity the main constraint.
What sources and further reading informed this Linkwarden hardware guide?
Current Linkwarden self-hosting docs, Docker Compose and environment-variable reference define the stack, browser preservation and storage model; ZimaOS confirms the app listing.
