Excalidraw's static client is light; databases, media, AI and other apps are more likely to create CPU/RAM pressure.
All-in-one home servers.متطلبات أجهزة Excalidraw: ذاكرة الوصول العشوائي (RAM)، ووحدة المعالجة المركزية (CPU) والاستضافة الذاتية
خطّط للاستضافة الذاتية لـ Excalidraw من حيث ذاكرة RAM ووحدة المعالجة المركزية وDocker وعرض المتصفح، مع إرشادات عملية للتثبيت المخصّص على ZimaOS وحدود التعاون.
Excalidraw requirements at a glance
Excalidraw is very different from a database-heavy server app. The official Docker image builds the client and serves static assets from Nginx, so normal self-hosting has very low server-side compute demand.
- CPU
- No numerical official server minimum published. The self-hosted client is served as static web assets, so normal drawing work happens primarily in the browser.
- RAM
- No numerical official server minimum published. Server memory needs for the static client are modest; the user's browser and drawing complexity matter more.
- Storage
- No numerical official minimum. The client image and static assets are small compared with typical NAS workloads.
- Collaboration
- Official self-hosting currently does not support sharing or collaboration features; upstream says a separate local collab server is needed for collaboration development.
- GPU
- No server GPU is required. Canvas rendering is a client-browser workload.
- Best Zima starting point
- ZimaBoard 2 832 is already far more than enough for the official static self-hosted client; choose larger Zima hardware only for other apps or storage workloads.
From official requirements to the right setup
Excalidraw sizing is mostly about understanding that the server serves the client while the browser does the interactive drawing work.
-
Official requirements
Separate the official self-hosted client from collaboration. The published Docker image serves the Excalidraw client, but upstream currently states that sharing/collaboration is not included in the self-hosted instance.
-
Confirm your needs
Do not invent a RAM or CPU minimum. Upstream publishes no numerical server requirement, and the production Dockerfile serves the built app through Nginx.
-
Leave room to grow
Size the user's browser/device for large drawings, many objects and complex scenes; server upgrades will not fix a weak client rendering environment.
-
Run it on ZimaOS
On ZimaOS, use Install Custom App with the official excalidraw/excalidraw image, expose the web port, place it behind HTTPS if remote, and keep collaboration expectations separate from the static client.
Check every playback client
- Static client only or collaboration expected
- Number/complexity of drawings
- Browser/device performance
- Public or LAN-only access
- HTTPS/reverse proxy
- Docker image version
- Need for persistent external storage
- Other ZimaOS apps
Official minimum requirements
Excalidraw's official self-hosting documentation publishes a Docker image and deployment command but no numerical server hardware minimum.
Do not assign a fake 1 GB or 2 GB minimum to Excalidraw. For the official self-hosted client, server compute is minimal; the bigger limitation is that self-hosting currently does not include sharing/collaboration.
| Requirement | Official minimum | What this supports |
|---|---|---|
| CPU minimum | No numerical official minimum published | The production image serves built static client assets from Nginx. |
| RAM minimum | No numerical official minimum published | Normal interactive drawing work is handled primarily by the client browser. |
| Storage minimum | No numerical official minimum published | Static app assets are small compared with database/media applications. |
| Official container | excalidraw/excalidraw | Published by the Excalidraw project for self-hosting the client. |
| Self-hosted sharing | Not currently supported | Official docs state that self-hosting does not include sharing or collaboration features. |
| Development prerequisites | Node.js, Yarn and Git | Needed for source/development workflows, not for simply running the published client image. |
When to upgrade your hardware
Excalidraw itself rarely justifies a server upgrade. Hardware growth usually comes from adjacent services or an attempt to add collaboration/storage infrastructure.
The ZimaOS host is running many other services
You add a separate collaboration stack
You add large persistent asset or project storage
Real-time collaboration introduces another server workload and should be sized independently from the official static client.
Teams expecting multiplayer drawing rather than a private static client.External file or collaboration storage can become the capacity driver even though the Excalidraw client itself is small.
Custom integrations and broader whiteboard platforms.Plan hardware growth with confidence
For Excalidraw, growth usually means adding adjacent services rather than scaling the static web client.
Keep the Excalidraw client on the smallest available host
The official image is a static Nginx-served client, so there is little reason to overprovision server compute.
ZimaBoard 2 832 is already ample.Scale client devices for complex drawings
Large scenes and interactive rendering are browser-side workloads; more server CPU will not materially improve a weak client device.
Improve the user's browser/device before upgrading the server for drawing performance.Size collaboration services separately
If you build or adopt a collaboration backend, treat its WebSocket, database and persistence needs as a separate application.
Choose 16 GB or stronger hardware only if that adjacent stack requires it.Choose ZimaCube for the wider home-server workload
Use ZimaCube when Excalidraw is one small app among storage, backup, media or project services.
Select Standard or Pro based on those other services, not Excalidraw alone.Can it run on ZimaOS?
Excalidraw is not currently presented as a verified public one-click ZimaOS App Store page in the catalog checked for this guide. It can be deployed easily through Install Custom App using the official Excalidraw client image.
Custom install Excalidraw in ZimaOS
Use Install Custom App with the official excalidraw/excalidraw image and expose container port 80 to a ZimaOS host port. Add HTTPS/reverse proxying for remote access.
Custom install Excalidraw in the ZimaOS app ↗Use the official Excalidraw client image
Upstream publishes a Docker image specifically for self-hosting the Excalidraw client under your own domain.
Review Excalidraw self-hosting ↗Do not promise built-in self-hosted collaboration
The official docs currently state that self-hosting your own instance does not support sharing or collaboration features.
Review Excalidraw collaboration notes ↗Choose Zima hardware for Excalidraw
The official Excalidraw self-hosted client is so light that hardware selection should be driven by the rest of the ZimaOS workload rather than the whiteboard itself.
Are you only serving the Excalidraw client, or is Excalidraw part of a larger collaboration/home-server stack?
Official static self-hosted client only
Use the smallest current Zima hardware; server compute is not the limiting factor.
- Best starting pointZimaBoard 2 832
Excalidraw plus collaboration/storage/other services
Choose hardware for those adjacent workloads rather than the static Excalidraw client.
- More app headroomZimaBoard 2 1664
- Broader storage platformZimaCube 2 Standard
These recommendations apply to the official static self-hosted client. A custom collaboration backend, database, file service or other integration has separate requirements.
| Zima hardware | Best for | Example workload | Core configuration | Recommended boundary | Next step |
|---|---|---|---|---|---|
| ZimaBoard 2 832 | The official Excalidraw static client. | Nginx-served Excalidraw web app plus normal lightweight ZimaOS services. |
|
This is already far more compute than the static client needs; browser performance and collaboration limitations matter more. | Get Now |
| ZimaBoard 2 1664 | Excalidraw plus a broader lightweight collaboration/productivity stack. | Static client plus additional containers, reverse proxy and companion services. |
|
Extra RAM is for adjacent services, not an Excalidraw requirement. | Get Now |
| ZimaCube 2 Standard | Excalidraw as one small app on a larger storage/productivity server. | Whiteboard client plus shared files, backups and other NAS services. |
|
Choose ZimaCube for storage/consolidation; Excalidraw alone does not justify the larger system. | 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 Excalidraw self-hosting, RAM, CPU, Docker, browser workload and collaboration limits.
How much RAM does self-hosted Excalidraw need?
Excalidraw does not publish a numerical server RAM minimum for the official self-hosted client.
How many CPU cores does Excalidraw need?
There is no numerical official server CPU minimum. The published Docker image serves static client assets through Nginx.
How much storage does Excalidraw need?
No universal official disk minimum is published. The static client is small compared with database or media services.
Does Excalidraw need a GPU on the server?
No. Interactive canvas rendering is primarily a client-browser workload, so a server GPU is unnecessary for the official self-hosted client.
Can self-hosted Excalidraw share drawings or collaborate in real time?
Not with the official self-hosted client as documented today. Upstream explicitly states that self-hosting currently does not support sharing or collaboration features.
Does Excalidraw have an official Docker image?
Yes. The project publishes excalidraw/excalidraw for self-hosting the client under your own domain.
Can ZimaBoard 2 run Excalidraw?
Yes, easily. The 8 GB ZimaBoard 2 is far beyond what the static client requires; choose storage and RAM based on other apps instead.
What should I upgrade if large Excalidraw drawings feel slow?
Check the user's browser/device first. Complex scene rendering happens on the client, so more server CPU usually will not solve browser-side drawing performance.
What sources informed this Excalidraw hardware guide?
The guide uses Excalidraw's current development/self-hosting documentation and Dockerfile, plus current Zima product pages for hardware matching.
