Linkwarden 하드웨어 요구 사항: RAM, CPU, 스토리지 및 아카이빙

Linkwarden의 CPU, RAM, PostgreSQL, MeiliSearch, 브라우저 아카이빙 및 스토리지 요구 사항을 확인한 후 적합한 ZimaOS 하드웨어를 선택하세요.

Linkwarden 하드웨어 요구 사항: RAM, CPU, 스토리지 및 아카이빙

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.

  1. Official requirements

    Account for the whole stack: Linkwarden, PostgreSQL and MeiliSearch.

  2. Confirm your needs

    Estimate preservation intensity: browser jobs can generate screenshots, PDFs, readable text and monolith HTML.

  3. Leave room to grow

    Plan archive storage separately from the database; S3-compatible storage is optional.

  4. 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.

Linkwarden self-hosting installation

A metadata-only bookmark server and a preservation-heavy archive server are fundamentally different workloads.

RequirementOfficial minimumWhat this supports
CPUNo numerical minimum publishedBrowser preservation/indexing create the main peaks.
RAMNo numerical minimum publishedFull stack includes app, PostgreSQL and MeiliSearch.
DatabasePostgreSQL 16 in current ComposeCurrent official repository compose.
SearchMeiliSearch 1.13.3 in current ComposeCurrent official repository compose.
App port3000Current Compose mapping.
GPUNot requiredAI 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

Chromium/Playwright jobs are much heavier than saving bookmark metadata.

Users preserving many pages with screenshots/PDFs.

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.

Account for the current full Compose stack

The official repository currently defines PostgreSQL and MeiliSearch alongside Linkwarden.

Read Linkwarden Docker Compose

Choose 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.
CPU
Intel N150, 4 cores, up to 3.6 GHz
Memory
8 GB LPDDR5
Storage
32 GB eMMC plus dual SATA and PCIe expansion
Network
Dual 2.5GbE
Acceleration
No dedicated GPU required.
Heavy simultaneous browser preservation can be the limit. Get Now
ZimaBoard 2 1664 Larger Linkwarden collection. More preservation/indexing headroom.
CPU
Intel N150, 4 cores, up to 3.6 GHz
Memory
16 GB LPDDR5
Storage
64 GB eMMC plus dual SATA and PCIe expansion
Network
Dual 2.5GbE
Acceleration
No dedicated GPU required.
Archive capacity may still require external storage. Get Now
ZimaCube 2 Standard Large long-term web archive. Preservation plus multi-drive storage.
CPU
Intel Core i3-1215U
Memory
8 GB
Storage
256 GB system storage with six 3.5-inch drive bays and SSD expansion
Network
Dual 2.5GbE
Acceleration
No dedicated GPU required.
Choose primarily for storage. Get Now
ZimaCube 2 Pro Larger preservation/search/archive platform. More CPU, RAM and storage services.
CPU
Intel Core i5-1235U
Memory
16 GB
Storage
256 GB system storage with six 3.5-inch drive bays and SSD expansion
Network
Dual 2.5GbE plus 10GbE on the current Pro configuration
Acceleration
No dedicated GPU required.
Very heavy Chromium concurrency may still benefit from remote browser workers. Get Now

What the Press Says

Highlights from trusted reviewers worldwide.

La Razón
“ZimaCube 2: Not just another NAS, tested with 25TB storage, local AI agents, 4K transcoding, and real homelab workflows.”
Read full review
GameRevolution
“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
TechRadar Pro
“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
FOX 8
“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.

ZimaBlade single-board server
★★★★★

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.

ZimaCube Pro personal cloud
★★★★★

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.

ZimaBlade single-board server
★★★★★

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.

ZimaBoard 2 single-board 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.

  1. Linkwarden Self-Hosting Installation
  2. Linkwarden Docker Compose
  3. Linkwarden Environment Variables
  4. Linkwarden Official Repository
  5. Linkwarden - ZimaOS App Store