The relevant Obsidian forum discussion includes an 8,000-file vault using roughly 700 MB with many plugins enabled, while Obsidian staff explains that low-RAM systems can swap heavily. Large vault/plugin combinations are a practical reason to add memory, but not a universal minimum.
For users with thousands of files, many community plugins, Dataview-style queries or complex dashboards.Obsidian Hardware Requirements: RAM, CPU, Storage & ZimaOS
Learn Obsidian hardware requirements for RAM, CPU, storage, large vaults, plugins, Docker remote desktop and ZimaOS hardware.
Obsidian hardware requirements at a glance
Obsidian does not publish a universal desktop CPU, RAM or storage minimum. Hardware demand depends on vault size, note length, attachments, graph/index work, community plugins and—on ZimaOS—the additional LinuxServer remote-desktop container layer.
- CPU
- Obsidian publishes no universal minimum CPU model or core count. Normal Markdown editing is light, while large vault indexing, search, graph views and plugin-heavy workflows can create short CPU bursts.
- RAM
- There is no current official Obsidian RAM minimum. A 2020 Obsidian staff forum reply explicitly said there were no known technical requirements and that memory use depends heavily on vault size and note length. The current ZimaOS container reserves 512 MB, but that reservation is not a hard application minimum.
- Container shared memory
- The current ZimaOS Obsidian manifest configures 1 GB shm_size. LinuxServer states that a shared-memory setting is needed for Electron applications to function properly. This is separate from normal system RAM sizing.
- Storage
- Obsidian itself has no universal disk-capacity requirement. Storage is driven by the vault: Markdown text is small, while PDFs, images, audio, video, canvases, plugins, caches and backups can dominate capacity. SSD improves startup, search and indexing responsiveness for large vaults.
- GPU
- A dedicated GPU is not required for note-taking. The LinuxServer browser-access container can optionally use Intel/AMD/NVIDIA hardware acceleration for its Wayland/Selkies remote-desktop rendering and encoding, but that is container-display acceleration rather than an Obsidian content requirement.
- Best Zima starting point
- ZimaBoard 2 832 is already far beyond the current ZimaOS container reservation with 8 GB RAM and is the natural starting point for personal Obsidian. Choose 1664 for very large vaults, many plugins or more co-hosted services; ZimaCube 2 is justified mainly by much larger attachment/archive storage.
From official requirements to the right setup
Obsidian sizing starts with the ZimaOS container architecture, then checks vault size, attachment volume, plugins, shared-memory configuration and remote-desktop behavior.
-
Official requirements
Separate Obsidian Notes from unrelated products named Obsidian or ONYX. The ZimaOS app is the Markdown knowledge-management application, packaged through a LinuxServer Obsidian desktop container.
-
Confirm your needs
Estimate the vault, not just note count. Plain Markdown takes little space, but large numbers of attachments, PDFs, images, audio/video and plugin-generated data can materially increase storage and indexing work.
-
Leave room to grow
Preserve the ZimaOS container's 1 GB shared-memory configuration. The current manifest reserves 512 MB system memory and sets shm_size to 1 GB; do not confuse either value with a universal upstream Obsidian RAM requirement.
-
Run it on ZimaOS
Test a representative vault with the intended plugins, search, graph view and browser-based GUI. Monitor host RAM, container RAM, CPU and storage latency before upgrading hardware.
Check every playback client
- Vault file count and total attachment size
- Number and complexity of community plugins
- Graph view, Dataview/search and indexing workload
- ZimaOS LinuxServer Obsidian container version
- 1 GB container shared-memory configuration
- SSD versus eMMC/HDD vault and config storage
- Browser remote-desktop latency and display resolution
- Other ZimaOS containers and home-server workloads
Official minimum requirements
Current Obsidian documentation provides supported installation methods for Windows, macOS and Linux but does not publish a universal CPU/RAM/disk hardware table. The ZimaOS package adds its own LinuxServer container settings, which should be described separately from upstream requirements.
Do not publish 4 GB, 8 GB or 16 GB as an official Obsidian Notes minimum. For the current ZimaOS package, the strongest concrete deployment facts are a 512 MB Docker memory reservation and 1 GB shared-memory setting, while practical host sizing still depends on vault size, plugins and other services.
| Requirement | Official minimum | What this supports |
|---|---|---|
| CPU minimum | No universal official minimum published | Current Obsidian install/help documentation does not define a processor model or core-count floor. |
| RAM minimum | No universal official minimum published | The relevant Obsidian forum staff response says requirements depend on vault size and notes and does not establish a fixed RAM floor. |
| Disk minimum | No universal official capacity published | Vault attachments and backups determine practical storage far more than the application binary. |
| ZimaOS container reservation | 512 MB memory reservation | The current official ZimaOS/CasaOS App Store manifest reserves 512 MB for the Obsidian container. This is a Docker resource reservation, not a published Obsidian application minimum. |
| ZimaOS shared memory | 1 GB shm_size | The current ZimaOS manifest configures 1 GB shared memory, and LinuxServer documents --shm-size as necessary for Electron applications. |
| ZimaOS architectures | amd64 and arm64 | The current ZimaOS manifest lists both architectures, matching LinuxServer's multi-architecture Obsidian image. |
When to upgrade your hardware
Upgrade Obsidian hardware only when the vault, plugins, browser GUI or the rest of the ZimaOS stack creates measured CPU, memory or storage pressure.
Large vaults and plugin-heavy workflows keep memory high
Search, graph and indexing become noticeably slow
The ZimaOS browser GUI competes with many other containers
A large vault can create bursty CPU and storage work during startup, indexing, graph rendering and plugin operations. Faster CPU and SSD storage help when these tasks are the measured bottleneck.
For large research, documentation and personal-knowledge vaults.The ZimaOS package is not just a static Markdown server; it runs a desktop Obsidian application through LinuxServer's Selkies browser-access layer. More simultaneous applications and services can make system RAM and CPU headroom valuable.
For all-in-one ZimaOS servers running Obsidian beside media, AI, automation and storage services.Plan hardware growth with confidence
Obsidian scales most cleanly when the vault, container configuration and bulk attachments are treated as separate storage and performance concerns.
Move a growing vault and config to SSD
Markdown files are light, but search indexes, plugin state and large attachment sets benefit from low-latency storage. SSD is especially useful for vaults with thousands of files.
Use SATA or NVMe SSD on ZimaBoard 2 instead of relying indefinitely on onboard eMMC for a large active vault.Keep large attachments on storage sized for capacity
PDFs, screenshots, audio, video and other assets can dominate vault size even though notes remain small. Storage capacity should follow attachment growth rather than a generic Obsidian app number.
Use larger SATA disks or ZimaCube 2 multi-drive storage when the knowledge base becomes a large document/media archive.Reduce plugin load before assuming more RAM is mandatory
Community plugins can materially affect startup time, indexing, memory and background work. Disable unused plugins and compare a clean vault before attributing all performance issues to hardware.
Keep ZimaBoard 2 832 when the workload is light after plugin cleanup; move to 16 GB when the combined vault and service stack genuinely needs headroom.Enable display acceleration only for the remote-GUI layer
LinuxServer's current Wayland/Selkies stack can use GPU acceleration to reduce remote-desktop encoding CPU and latency. This does not make Obsidian note indexing or Markdown processing GPU-accelerated.
Validate /dev/dri exposure and container configuration before claiming Intel iGPU acceleration is active.Can it run on ZimaOS?
Obsidian is currently listed in the ZimaOS App Store under Productivity. The current official manifest packages Obsidian 1.12.7 through LinuxServer and exposes the desktop GUI through browser-access ports.
Use the current ZimaOS Obsidian package
The official App Store manifest currently uses lscr.io/linuxserver/obsidian:1.12.7, supports amd64 and arm64, and classifies Obsidian under Productivity.
Open Obsidian in the ZimaOS App StorePreserve the container's shared-memory configuration
The current ZimaOS compose definition reserves 512 MB memory and configures shm_size: 1gb. LinuxServer says shared memory is required for Electron applications to function properly.
Review the ZimaOS Obsidian manifestSecure browser access
LinuxServer states that HTTPS is required for full functionality and warns that the container exposes a GUI with powerful terminal access. Remote Internet exposure should use a properly secured reverse proxy and authentication.
Read LinuxServer Obsidian documentationChoose Zima hardware for your Obsidian workload
The current ZimaOS Obsidian container reserves only 512 MB, so every current Zima system in this comparison has substantial host-memory headroom. The real choice is vault/plugin scale, attachment storage and the number of other services sharing the server.
Is this a personal Markdown vault, or a large attachment-heavy knowledge archive sharing the server with many applications?
Personal/light-to-moderate Obsidian vault
Start with ZimaBoard 2 832. Its Intel N150 and 8 GB RAM are far above the current container reservation. Choose 1664 only when very large vault/plugin workloads or many other containers independently justify additional RAM.
- Personal Obsidian vault and normal pluginsZimaBoard 2 832
- Large plugin-heavy vault plus more servicesZimaBoard 2 1664
Large document/media archive or broader NAS workload
Choose ZimaCube 2 from the storage requirement rather than Obsidian's compute needs. Standard is suitable for a storage-first archive; Pro provides more RAM and CPU headroom for a larger all-in-one server. Creator Pack adds no meaningful Obsidian-specific advantage.
- Large multi-drive document and attachment archiveZimaCube 2 Standard
- Large archive plus heavier multi-service workloadZimaCube 2 Pro
- Only when unrelated GPU/AI workloads also require itZimaCube 2 Creator Pack
This is a workload guide, not a guaranteed vault-size or plugin-count benchmark. Performance depends on Obsidian/container version, file count, note length, attachments, plugins, graph/search workload, browser resolution, storage latency and other ZimaOS services.
| Zima hardware | Best for | Example workload | Core configuration | Recommended boundary | Next step |
|---|---|---|---|---|---|
| ZimaBoard 2 832 | The best-value current Zima option for personal Obsidian and browser-based remote access. | Personal Markdown vaults, normal attachments, community plugins and several lightweight ZimaOS services. |
|
The 32 GB eMMC can become restrictive for a large attachment-heavy vault and broader Docker stack. Use SSD expansion before moving to a larger server solely for Obsidian. | Get Now |
| ZimaBoard 2 1664 | A compact Obsidian host with more memory for large plugin-heavy vaults and additional self-hosted applications. | Large vaults, many plugins, heavier search/graph workflows and more co-hosted Docker services. |
|
Do not claim Obsidian requires 16 GB. The 1664 is useful when the entire workload needs more memory, not because the base app has a 16-GB requirement. | Get Now |
| ZimaCube 2 Standard | A storage-first Obsidian knowledge archive with large PDFs, images, audio/video attachments and backups. | Large document collections, attachment-heavy vaults, backups and moderate NAS/self-hosted services. |
|
Standard still has 8 GB RAM. ZimaBoard 2 1664 may provide more memory headroom at smaller scale if multi-drive attachment storage is not required. | Get Now |
| ZimaCube 2 Pro | A larger all-in-one knowledge/NAS server where Obsidian shares the system with many applications and substantial local storage. | Large Obsidian archive, many containers, document/media storage, backups and heavier multitasking. |
|
Do not recommend Pro just to make ordinary note editing faster. The larger platform is justified by storage and multi-service workload, not the base Obsidian app. | Get Now |
| ZimaCube 2 Creator Pack | An Obsidian-accessible knowledge server already purchased for separate local AI, creator or GPU workflows. | Obsidian archive plus unrelated local LLM, image, video, creator or GPU applications. |
|
Extreme overkill for Obsidian alone. Never recommend Creator Pack because the vault is large or has many Markdown files; choose it only when separate GPU/AI workloads independently justify the hardware. | 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
Several supplied URLs contain the word 'Obsidian' but refer to unrelated products. These answers separate Obsidian Notes from Obsidian Control Systems ONYX, Plesk Obsidian and Obsidian Entertainment games.
How much RAM does Obsidian need?
Obsidian Notes does not publish one universal current RAM minimum. In the supplied official-community forum thread, an Obsidian staff member said there were no known technical requirements and that needs depend strongly on note count, note length and available memory. The current ZimaOS container reserves 512 MB, but that is not a hard upstream minimum.
Is 4 GB RAM enough for Obsidian?
It can run Obsidian, but 4 GB is not an official requirement. The supplied 2020 forum thread began with an i3/4-GB laptop experiencing system hangs; staff explained that low RAM can trigger swapping. Modern ZimaBoard 2 832 provides 8 GB and much more practical headroom.
Why does the ZimaOS Obsidian container use 1 GB shared memory?
The current ZimaOS manifest sets shm_size to 1 GB. LinuxServer documents shared memory as necessary for Electron applications to function properly. This 1-GB shared-memory configuration is not the same thing as saying Obsidian requires 1 GB total system RAM.
Does Obsidian need a GPU?
No dedicated GPU is required for normal notes, search or vault management. The LinuxServer ZimaOS container can optionally use Intel/AMD/NVIDIA acceleration for its browser-streamed desktop display, which can reduce remote-GUI CPU/latency but does not GPU-accelerate Markdown or vault indexing.
Are Obsidian Control Systems ONYX requirements relevant to Obsidian Notes?
No. The supplied support.obsidiancontrol.com page is for ONYX professional lighting-control software and specifies Windows, sixth-generation Intel Core-class CPUs, DirectX 11 graphics, 8 GB RAM and 40 GB SSD space. Those requirements have nothing to do with the Obsidian Markdown knowledge-management app in ZimaOS.
Can I use Plesk Obsidian's 1–2 GB RAM requirements for Obsidian Notes?
No. Plesk Obsidian is a web-hosting control panel. Its Linux/Windows server RAM and 20–32 GB disk figures belong to Plesk hosting infrastructure, not the Obsidian Notes application.
Are the Obsidian Entertainment system requirements relevant?
No. The supplied support.obsidian.net article is for the game Pillars of Eternity II and lists 4 GB RAM, 45 GB storage and DirectX-compatible graphics. Obsidian Entertainment is a game developer and is unrelated to Obsidian Notes.
Can ZimaBoard 2 run the ZimaOS Obsidian App?
Yes. The current ZimaOS manifest supports amd64, reserves 512 MB for the container and sets 1 GB shared memory. ZimaBoard 2 832 provides an Intel N150 and 8 GB RAM, leaving substantial host headroom for personal Obsidian and other light services.
What sources and further reading informed this Obsidian hardware guide?
The supplied Obsidian Forum thread is the only source in this set directly about the Obsidian Notes application. It records a 2020 staff statement that no fixed technical requirements were known and that CPU/RAM behavior depends on vault size and note length; a later user reports roughly 700 MB usage with around 8,000 files and many plugins. The supplied Obsidian Control Systems page is for ONYX lighting-control software, not Obsidian Notes. The Plesk page is for the Plesk Obsidian hosting control panel. The Obsidian Entertainment support page is for Pillars of Eternity II. The supplied CastlerockGC 'Obsidian Onyx' page returned 403 during this audit and search results associate 'Obsidian Onyx' with ONYX lighting-control requirements; it is therefore not used to establish any Obsidian Notes hardware claim. Current Obsidian official install documentation, ZimaOS/CasaOS manifest data and LinuxServer Obsidian container documentation were separately used as higher-authority evidence for the current ZimaOS deployment.
