Federation, media, room history and PostgreSQL—not Element Web—drive most infrastructure growth.
Larger Matrix communities.Element Webのハードウェア要件：RAM、CPU、ストレージ
RAM、CPU、Docker、ドメイン、Matrix接続に対応したPlan Element Webのセルフホスティングを計画し、実用的なZimaOSカスタムインストールの容量設計とサーバー/クライアントの役割分担を確認する。
Element Web requirements at a glance
Element Web is the browser client for Matrix, not the Matrix homeserver. Current Element Server Suite defaults request 50m CPU and 50 MiB RAM with a 200 MiB memory limit for the Element Web pod.
- CPU
- Current Element Server Suite defaults request 50m CPU for the Element Web pod; standalone Docker has no universal core minimum.
- RAM
- Current defaults request 50 MiB RAM and set a 200 MiB memory limit for the Element Web pod.
- Storage
- No universal numerical disk minimum for Element Web; static client/config storage is small compared with Matrix backend data.
- Docker
- Official Element Web images are available and support custom config.json.
- Domain security
- Element recommends not serving Element Web on the same domain as the Matrix homeserver.
- Best Zima starting point
- ZimaBoard 2 832 is far more than enough for Element Web itself; size hardware for the Matrix backend if hosted locally.
From official requirements to the right setup
Size Element Web from its real service stack and persistent data rather than using a guessed one-size-fits-all server number.
-
Official requirements
Treat Element Web as the frontend client, not the Matrix homeserver.
-
Confirm your needs
Use the published Element Web pod defaults as a reference: 50m CPU request, 50 MiB memory request and 200 MiB memory limit.
-
Leave room to grow
Size the Matrix homeserver, PostgreSQL, media repository, bridges and Coturn separately because those services drive most hardware use.
-
Run it on ZimaOS
On ZimaOS, use Install Custom App with the official Element Web image, mount config.json and use a separate hostname from the Matrix homeserver.
Check every playback client
- Element Web only or full Matrix stack
- Matrix homeserver URL
- Separate Element hostname
- config.json
- HTTPS/reverse proxy
- Media/bridges/Coturn location
- Database host
- Other ZimaOS services
Official minimum requirements
Element Web does not publish a universal standalone hardware floor, but current Element Server Suite documentation exposes explicit Kubernetes resource defaults for the web client.
Do not apply Matrix homeserver hardware figures to Element Web itself. The frontend is lightweight; backend services are a separate hardware problem.
| Requirement | Official minimum | What this supports |
|---|---|---|
| CPU request | 50m | Default Element Web pod request. |
| Memory request | 50 MiB | Default Element Web pod request. |
| Memory limit | 200 MiB | Default Element Web pod limit. |
| Standalone CPU minimum | No universal numerical minimum published | Standalone Docker serves a lightweight web client. |
| Storage minimum | No universal numerical minimum published | Mostly static client/config footprint. |
| Security boundary | Separate Element and Matrix homeserver domains recommended | Current Element security guidance. |
When to upgrade your hardware
Upgrade Element Web when measured workload, storage growth or background processing outgrows the current host.
The Matrix homeserver grows
Bridges, Coturn and media services expand
Other ZimaOS services create host contention
VoIP/video and protocol bridges add independent CPU, bandwidth and storage requirements.
Full-featured Matrix deployments.The lightweight frontend can still be affected by whole-host pressure.
All-in-one home servers.Plan hardware growth with confidence
Scale Element Web by addressing the actual bottleneck—database, storage, processing or concurrency—before simply buying a larger server.
Keep Element Web lightweight
The frontend resource defaults are tiny compared with a full homeserver.
ZimaBoard 2 832 is already ample.Add RAM for the homeserver/database
PostgreSQL and the Matrix backend are the meaningful memory consumers.
ZimaBoard 2 1664 when hosting backend services too.Use larger storage for Matrix media/history
Backend media and database history can grow much larger than Element Web.
ZimaCube 2 Standard or Pro.Use stronger CPU/network for broader communication services
Federation, media proxying and VoIP can justify stronger hardware.
ZimaCube 2 Pro.Can it run on ZimaOS?
Element Web is not currently confirmed as a public official one-click ZimaOS App Store page in the sources checked for this guide. It can still be deployed through Install Custom App.
Custom install Element Web in ZimaOS
Use Install Custom App with the official Element Web image, mount config.json and map the HTTP port behind HTTPS.
Custom install Element Web in the ZimaOS app ↗Use the official Element Web Docker image
Element publishes a prebuilt Docker image and documents custom config.json.
Review Element Web Docker installation ↗Keep Element and Matrix on separate domains
Element's security documentation recommends separate domains to reduce trust-boundary risk.
Review Element Web security guidance ↗Choose Zima hardware for Element Web
Choose Zima hardware for the complete Element Web workload, including its database, storage and background services.
Are you hosting only Element Web or the full Matrix stack too?
Element Web only
Use the smallest current Zima option; frontend compute is tiny.
- Best starting pointZimaBoard 2 832
Element Web plus local Matrix backend
Choose hardware for the homeserver/database/media workload.
- More memory headroomZimaBoard 2 1664
- Higher-headroom platformZimaCube 2 Pro
These are practical workload recommendations, not official throughput or user-count guarantees.
| Zima hardware | Best for | Example workload | Core configuration | Recommended boundary | Next step |
|---|---|---|---|---|---|
| ZimaBoard 2 832 | Element Web frontend only. | Static web client, config and reverse proxy. |
|
Far more compute than Element Web needs; do not use this to infer full Matrix capacity. | Get Now |
| ZimaBoard 2 1664 | Small all-in-one Matrix experiments. | Element Web plus modest Matrix homeserver/database services. |
|
16 GB headroom is for backend services, not the frontend. | Get Now |
| ZimaCube 2 Pro | Larger self-hosted communication stacks. | Matrix backend, media, bridges, VoIP and broader services. |
|
Actual Matrix capacity depends on homeserver implementation, federation and media load. | 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 Element Web RAM, CPU, storage, Docker and ZimaOS deployment.
How much RAM does Element Web need?
Current Element Server Suite defaults request 50 MiB RAM and set a 200 MiB memory limit for the Element Web pod.
How much CPU does Element Web need?
The same default configuration requests 50m CPU.
Does Element Web include a Matrix homeserver?
No. Element Web is the frontend client; a separate Matrix homeserver provides accounts, rooms and message history.
How much storage does Element Web need?
No universal numerical storage minimum is published; frontend storage is small compared with backend media/database storage.
Does Element Web need a GPU?
No dedicated GPU is required.
Can ZimaBoard 2 run Element Web?
Yes, easily. The 8 GB model is far above the frontend's published pod defaults.
Should Element Web use the same domain as the Matrix server?
Element recommends separate domains for a stronger security boundary.
When does Element need stronger Zima hardware?
When you also host the Matrix homeserver, database, media, bridges or VoIP services.
What sources informed this Element hardware guide?
Current Element Web resource, installation and security documentation plus current Zima product pages.
