TriliumNext explicitly documents a roughly 2 GB memory spike during large import/export testing. Heavy migration workflows therefore need more headroom than idle server use.
Users migrating multi-gigabyte Evernote/Notion/HTML archives or regularly exporting full knowledge bases.Requisiti hardware di Trilium: RAM, spazio di archiviazione, ARM e database di grandi dimensioni
Scopri i requisiti attuali di TriliumNext per CPU, RAM, Docker, ARM, SQLite e database di grandi dimensioni, quindi scegli l’hardware ZimaOS più adatto.
Trilium requirements at a glance
The current ZimaOS Trilium package follows TriliumNext, the actively developed successor/fork of the original Trilium Notes project. TriliumNext does not publish a normal CPU or RAM minimum. Official system requirements focus on Docker/platform support: native Linux x64 and ARM64 are supported, while ARMv7/ARMv8 Docker builds are legacy/best-effort. Large import/export work is the clearest official memory sizing evidence: a 2.4 GB database with about 21,000 notes was tested with memory peaks around 2 GB.
- CPU
- No numerical official minimum. Normal personal-note serving is lightweight; search, scripts, large imports/exports and sync activity create the heavier bursts.
- RAM
- No normal-running RAM minimum is published. Community reports often place an idle/small TriliumNext server in the low hundreds of MB, while official large-import/export testing can peak around 2 GB.
- Architecture
- Native server binaries are available for Linux x64 and ARM64. Docker also offers ARMv7/ARMv8 builds, but TriliumNext marks those as legacy/best-effort because current Node.js support is experimental.
- Database
- Trilium stores notes, tree structure, metadata and most configuration in a SQLite `document.db` inside the persistent data directory.
- Large data operations
- Official import/export documentation says memory can spike to around 2 GB during large operations; this was tested with a 2.4 GB database containing about 21k notes.
- Best Zima starting point
- ZimaBoard 2 832 provides ample x86-64 CPU and 8 GB RAM for normal TriliumNext hosting plus large import/export headroom. The 1664 or ZimaCube tiers are mainly for a larger Productivity stack, big attachments/databases and storage/backup growth.
From official requirements to the right setup
Trilium sizing starts with architecture and database scale, then separates daily use from large import/export peaks.
-
Official requirements
Use current TriliumNext rather than sizing from the retired/maintenance-era original Trilium project. ZimaOS currently lists TriliumNext changes in its Trilium App Store entry.
-
Confirm your needs
Prefer Linux x64 or ARM64. TriliumNext's current system requirements classify ARMv7/ARMv8 Docker builds as legacy/best-effort because they must remain on an older Node.js line.
-
Leave room to grow
Size storage and memory from the SQLite database and attachments. Normal server RAM can be modest, but large import/export operations have an official tested memory peak around 2 GB on a 2.4 GB / ~21k-note database.
-
Run it on ZimaOS
Install Trilium from the ZimaOS App Store, map persistent `trilium-data`, test search, sync, backup and any large import/export workflow, then monitor database size and real memory before choosing more hardware.
Check every playback client
- Current TriliumNext version rather than legacy original Trilium
- x64/ARM64 versus legacy ARMv7/ARMv8
- Total note count and SQLite database size
- Large attachments and file notes
- Large import/export operations
- Search scope and heavy saved searches
- Desktop-client synchronization
- Backup and data-directory storage
Official minimum requirements
TriliumNext's current System Requirements page does not publish a numerical CPU or RAM minimum. It specifies supported deployment platforms and architecture support.
Use architecture compatibility as the hard baseline and the official ~2 GB large-import/export peak as heavy-operation evidence. Do not mislabel a Reddit idle-memory number as an official RAM minimum.
| Requirement | Official minimum | What this supports |
|---|---|---|
| CPU | No numerical minimum published | Current System Requirements does not specify core count or clock speed. |
| RAM | No normal-running numerical minimum published | Official heavy import/export testing provides a useful peak reference instead. |
| Native Linux architectures | x64 and ARM64 (aarch64) | Current officially provided native server binaries. |
| Legacy Docker ARM | ARMv7 and ARMv8 best-effort | Current docs mark these builds legacy because Node.js platform support is experimental. |
| Large import/export memory | Around 2 GB peak in official testing | Tested against a 2.4 GB database with approximately 21,000 notes. |
| Database | SQLite document.db | Contains notes, tree structure, metadata and most configuration. |
When to upgrade your hardware
Upgrade Trilium when the knowledge base or wider server workload—not ordinary note editing—creates measurable pressure.
Large imports/exports push memory toward the official ~2 GB peak
Search slows across a very large database
Trilium shares the host with backup, sync and other Productivity apps
Current Trilium FAQ recommends Fast Search, limiting the ancestor/scope and result count, and archiving old notes for large databases before simply upgrading hardware.
Users with tens of thousands of notes or broad full-content searches.The SQLite server can remain modest while file services, databases, reverse proxy and backups consume the remaining RAM/storage.
All-in-one ZimaOS Productivity servers.Plan hardware growth with confidence
Scale Trilium by keeping the SQLite data directory responsive and controlling expensive searches/imports.
Keep `trilium-data` on reliable local persistent storage
The data directory contains `document.db`, configuration, automatic backups and logs. Fast/reliable local app storage is more important than bulk NAS throughput for ordinary note operations.
Use reliable eMMC/SSD/NVMe/SATA appdata storage and back up the entire data directory.Use Fast Search and archive old notes
Trilium's FAQ recommends title/attribute-only Fast Search, narrower ancestor scope, result limits and archiving old notes to improve large-database search.
Optimize search scope before assuming a CPU upgrade is required.Plan roughly 2 GB of free memory for large import/export bursts
Official testing on a 2.4 GB / ~21k-note database observed memory peaks around 2 GB during large import/export operations.
ZimaBoard 2 832 leaves comfortable margin for this plus ZimaOS and normal companion services.Back up the data directory outside the live host
Trilium creates daily, weekly, monthly and pre-migration database backups, but official docs explicitly call this a basic backup and encourage an additional external/cloud/computer backup.
Use separate disks, another NAS or off-site storage for a real recovery plan.Can it run on ZimaOS?
Trilium is currently available in the ZimaOS App Store and the listing tracks TriliumNext releases.
Install the current Trilium package from the ZimaOS App Store
The ZimaOS listing currently references TriliumNext features, so the hardware page should follow TriliumNext documentation rather than the legacy original project.
Open Trilium in the ZimaOS App StorePersist the Trilium data directory
The Docker server stores data under the mounted `trilium-data` directory; the current guide defaults the service to port 8080.
Read TriliumNext Docker installationDo not sync document.db with Dropbox/Google Drive/OneDrive
Trilium's FAQ explicitly warns that generic file-sync tools can corrupt the live SQLite database. Use Trilium's sync/web-server mechanism instead.
Read TriliumNext synchronization FAQChoose Zima hardware for TriliumNext
Normal TriliumNext hosting is modest, while large imports/exports and the rest of a Productivity server can require more headroom.
Is Trilium a normal personal knowledge base or part of a large Productivity/storage server?
Normal personal knowledge base
ZimaBoard 2 832 has ample x86-64 CPU, 8 GB RAM and storage expansion for TriliumNext.
- Normal TriliumNext serverZimaBoard 2 832
- Large knowledge base plus more Productivity appsZimaBoard 2 1664
Large attachments, backups or multi-drive Productivity platform
Move to ZimaCube when storage and wider application workloads—not Trilium's idle process—justify it.
- Integrated knowledge/storage serverZimaCube 2 Standard
- Large all-in-one Productivity and 10GbE workflowZimaCube 2 Pro
There is no official normal-running TriliumNext CPU/RAM minimum or fixed note-count benchmark. Database size, attachments, search scope, scripts, import/export and co-hosted services can change real resource use.
| Zima hardware | Best for | Example workload | Core configuration | Recommended boundary | Next step |
|---|---|---|---|---|---|
| ZimaBoard 2 832 | A normal self-hosted TriliumNext personal knowledge base. | Daily notes, search, sync and occasional large imports/exports. |
|
Even though ordinary RAM use can be modest, leave headroom for official ~2 GB import/export peaks. | Get Now |
| ZimaBoard 2 1664 | A larger Trilium database plus more Productivity services. | Large searches/imports, backups and additional containers. |
|
16 GB is for whole-server and growth headroom, not a TriliumNext requirement. | Get Now |
| ZimaCube 2 Standard | A multi-drive knowledge/storage server with TriliumNext. | Large attachments, backups and other Productivity/storage applications. |
|
Choose it for integrated storage and broader workloads rather than basic note serving. | Get Now |
| ZimaCube 2 Pro | A larger all-in-one Productivity platform. | Trilium plus large databases, backups, storage and fast local workflows. |
|
10GbE and Core i5 resources mainly benefit the wider server stack. | 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 FAQ topics follow query fan-out around TriliumNext versus legacy Trilium, RAM use, ARM support, large imports, SQLite syncing, search performance and backups. Reddit/community figures are used as field experience, not official minimums.
Is the current ZimaOS Trilium app the old Trilium or TriliumNext?
The current ZimaOS App Store listing references TriliumNext releases and features. Hardware guidance should therefore follow TriliumNext's current documentation, not the old maintenance-era upstream project.
How much RAM does TriliumNext need for normal self-hosting?
TriliumNext does not publish a normal-running RAM minimum. Community users report small server instances in the low hundreds of megabytes, including reports around 170–280 MB, but those are field observations rather than specifications.
Why does TriliumNext need around 2 GB RAM during large imports or exports?
That figure is an official heavy-operation reference, not idle usage. TriliumNext says a large import/export can spike to around 2 GB of memory and tested this with a 2.4 GB database containing roughly 21,000 notes.
Can TriliumNext run on Raspberry Pi or ARM?
Yes, but prefer ARM64. Native Linux ARM64 binaries are officially provided. ARMv7/ARMv8 Docker builds remain available but are marked legacy/best-effort because modern Node.js support on those platforms is experimental.
Can I put Trilium document.db in Dropbox, Google Drive or OneDrive?
No. Trilium explicitly warns that generic file-sync tools can corrupt a live SQLite database. The supported network-sync model is Trilium's own sync/web server.
How can I make search faster in a very large Trilium database?
Current Trilium guidance recommends Fast Search, restricting searches to an ancestor/subtree, limiting results and archiving older notes to reduce the search scope before changing hardware.
Are Trilium's automatic backups enough?
They are useful but intentionally basic. Trilium keeps daily, weekly, monthly and pre-migration database backups, while its documentation still recommends backing up the database/data directory to another computer or cloud/off-site location.
Can ZimaBoard 2 832 run TriliumNext?
Yes. Its Intel N150 and 8 GB RAM provide substantial headroom for normal operation and the official ~2 GB large import/export peak, while leaving room for ZimaOS and other Productivity services.
What sources and further reading informed this Trilium hardware guide?
TriliumNext's current System Requirements and Docker docs define x64/ARM64 support and the current container model. The official Import & Export guide provides the ~2 GB peak-memory test for a 2.4 GB / ~21k-note database. The FAQ defines SQLite sync and large-search constraints. Reddit was used for query fan-out and typical idle-memory field reports, while the ZimaOS App Store confirms the current TriliumNext-based package.
