The plus image runs a browser-based snapshot workflow that is heavier than standard bookmark management.
Users archiving many pages locally.Requisitos de hardware do linkding: RAM, CPU, SQLite e instantâneos
Planeie o hardware do Linkding para RAM, CPU, SQLite ou PostgreSQL, instantâneos HTML e Docker, com recomendações práticas para instalação personalizada do ZimaOS.
linkding requirements at a glance
linkding is intentionally minimal, but the selected image variant changes the hardware profile. The standard image is lightweight; the plus image adds Chromium for HTML snapshots.
- RAM
- No numerical official minimum published. The standard image is light; the plus image needs more runtime memory because it includes Chromium.
- CPU
- No numerical official core minimum. Bookmark management is light, while HTML snapshot generation adds browser/processing work.
- Storage
- No universal official minimum. SQLite/PostgreSQL data is small, but HTML snapshots can grow substantially over time.
- Database
- SQLite is the default. PostgreSQL is also supported through environment configuration.
- Image variants
- latest provides core functionality; latest-plus adds HTML snapshots and Chromium, making the image larger and increasing runtime memory/disk use.
- Best Zima starting point
- ZimaBoard 2 832 is far more than enough for standard linkding and provides comfortable headroom even for the plus image.
From official requirements to the right setup
Choose the standard or plus image first, then size storage and memory around snapshot retention and the database.
-
Official requirements
Use the standard image for the lightest deployment; choose latest-plus only if local HTML snapshot archiving is needed.
-
Confirm your needs
Keep SQLite for the simplest installation, or configure PostgreSQL when you prefer an external database service.
-
Leave room to grow
If using latest-plus, budget extra memory for Chromium and extra disk for stored HTML snapshots; snapshot retention can become the main storage driver.
-
Run it on ZimaOS
On ZimaOS, use Install Custom App with the official linkding image, map port 9090, persist /etc/linkding/data, and back up the database plus snapshot data.
Check every playback client
- Standard or plus image
- Bookmark count
- HTML snapshots enabled
- Snapshot retention
- SQLite or PostgreSQL
- Persistent data path
- Backup retention
- Other ZimaOS services
Official minimum requirements
linkding's current installation documentation explains image variants and database choices but does not publish numerical server hardware minimums.
Do not invent a 256 MB, 512 MB or 1 GB official minimum. The key distinction is standard versus plus: Chromium and snapshots increase memory and disk requirements.
| Requirement | Official minimum | What this supports |
|---|---|---|
| RAM minimum | No numerical official minimum published | The plus image explicitly needs more runtime memory. |
| CPU minimum | No numerical official minimum published | Snapshot generation adds browser/processing work. |
| Storage minimum | No numerical official minimum published | Snapshot retention can dominate disk growth. |
| Default database | SQLite | No extra database configuration required. |
| Alternative database | PostgreSQL | Supported through linkding database settings. |
| Standard image | latest | Provides core bookmark functionality. |
| Snapshot image | latest-plus | Includes Chromium and HTML snapshot support. |
When to upgrade your hardware
linkding should scale when snapshot generation, snapshot retention or the wider self-hosted stack creates measurable pressure.
Chromium snapshot jobs consume memory
HTML snapshots consume disk space
The host runs many other apps
Archived pages can grow much faster than the bookmark database itself.
Long-retention web archives.linkding may remain light while databases, media or automation services consume whole-host resources.
All-in-one ZimaOS servers.Plan hardware growth with confidence
Scale linkding primarily around snapshot retention and the wider host, not the core bookmark service.
Use the standard image when snapshots are unnecessary
Avoiding Chromium keeps the deployment lighter in memory and image size.
ZimaBoard 2 832 is already ample.Put snapshot data on SSD-backed storage
Local page archives and database backups benefit from reliable persistent storage.
Use SATA/NVMe with ZimaBoard 2 or SSD tiers on ZimaCube 2.Use 16 GB for heavy snapshot plus multi-app use
Extra RAM is most useful when Chromium snapshot jobs and many other containers share the host.
ZimaBoard 2 1664.Use ZimaCube for large web-archive retention
If snapshots become a long-term archive, larger storage capacity matters more than CPU.
ZimaCube 2 Standard.Can it run on ZimaOS?
linkding is not currently confirmed as a public official one-click ZimaOS App Store page in the sources checked for this guide. It can be deployed cleanly through Install Custom App using the official linkding container.
Custom install linkding in ZimaOS
Use Install Custom App with sissbruecker/linkding, map port 9090, and persist /etc/linkding/data. Select the plus tag only if HTML snapshots are required.
Custom install linkding in the ZimaOS app ↗Use linkding's official installation pattern
The current docs provide Docker deployment, SQLite by default and PostgreSQL as an optional database.
Review linkding installation ↗Treat the plus image as a heavier workload
latest-plus includes Chromium and explicitly requires more runtime memory and disk for HTML snapshots.
Review linkding image variants ↗Choose Zima hardware for linkding
Standard linkding is extremely light; hardware selection becomes more relevant only when using Chromium snapshots or combining it with many other apps.
Are you using standard bookmark management or the plus image with many HTML snapshots?
Standard linkding
Use ZimaBoard 2 832; CPU/RAM are far above the app's practical needs.
- Best starting pointZimaBoard 2 832
Heavy snapshot retention / broader app stack
Use more RAM or storage for Chromium jobs and archived pages.
- More memory headroomZimaBoard 2 1664
- Storage-first platformZimaCube 2 Standard
These are practical recommendations, not official bookmark-count or snapshot-throughput tiers.
| Zima hardware | Best for | Example workload | Core configuration | Recommended boundary | Next step |
|---|---|---|---|---|---|
| ZimaBoard 2 832 | Standard linkding and light snapshot use. | linkding, SQLite, background tasks and normal bookmark management. |
|
Far more compute than standard linkding needs; storage design matters only if snapshots grow. | Get Now |
| ZimaBoard 2 1664 | Heavy latest-plus snapshot use and many co-hosted apps. | Chromium snapshot jobs, PostgreSQL optional and broader productivity services. |
|
Extra RAM is for Chromium and the wider stack, not an official linkding minimum. | Get Now |
| ZimaCube 2 Standard | Long-term HTML snapshot archives. | linkding plus large local web archives, backups and broader NAS storage. |
|
Choose it for archive capacity rather than linkding compute. | 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 linkding RAM, CPU, SQLite, PostgreSQL, HTML snapshots, Docker and ZimaOS deployment.
How much RAM does linkding need?
linkding does not publish a numerical official RAM minimum. The plus image requires more runtime memory because it includes Chromium.
How many CPU cores does linkding need?
No numerical official core minimum is published; normal bookmark management is light.
Which database does linkding use?
SQLite is the default, and PostgreSQL is also supported.
What is linkding latest-plus?
It adds HTML snapshot support and includes Chromium, resulting in a larger image plus higher runtime memory and storage use.
How much storage does linkding need?
No universal official disk minimum is published. HTML snapshot retention can become the main storage requirement.
Does linkding need a GPU?
No dedicated GPU is required.
Can ZimaBoard 2 run linkding?
Yes, easily. The 8 GB model is far above standard linkding's practical needs.
When should I use ZimaCube 2?
When local HTML snapshots become a large long-term archive or linkding is only one app on a broader NAS.
What sources informed this linkding hardware guide?
The guide uses linkding's current installation, configuration and Docker documentation plus current Zima product pages.
