Quick Summary (TL;DR):
For a dedicated Home Assistant system, 4GB RAM and 64GB of reliable storage is already comfortable for many homes. Home Assistant officially supports Raspberry Pi installations with at least 2GB RAM and at least 32GB storage, while virtual-machine guidance also starts at 2GB RAM. For a new N100/N150 mini PCAliExpress price, 8GB RAM and a 128GB SSD is a sensible practical configuration because the cost increase is usually small and it leaves room for database growth, backups and future apps. Move to 16GB+ RAM or 256GB+ storage only when the machine is doing more than Home Assistant—such as Proxmox, local voice processing, databases, media services or several containers. Storage planning matters more than chasing huge RAM figures because Home Assistant’s recorder database, local backups and apps are what normally grow over time.
Home Assistant RAM and Storage at a Glance
| Use case | RAM | Storage | Comments |
|---|---|---|---|
| Official minimum-class setup | 2GB | 32GB | Meets documented Pi/VM starting point; little spare capacity |
| Normal dedicated Home Assistant | 4GB | 64GB | Comfortable for many homes with sensible recorder settings |
| New mini PCAliExpress price sweet spot | 8GB | 128GB SSD | Good balance of price, headroom and easy future growth |
| Heavy HAOS with many apps/local services | 8–16GB | 128–256GB SSD | Useful if databases, voice or additional services grow |
| Proxmox / multiple VMs / home server | 16GB+ | 256GB+ | Size for all workloads, not Home Assistant alone |
The rows above are practical sizing guidance, not hard Home Assistant limits. The official minimum and installation requirements are much lower than the capacity many current mini PCs are sold with.
Official Minimum RAM: 2GB
Home Assistant’s current Raspberry Pi installation guide specifies a Raspberry Pi 4 or 5 with at least 2GB of RAM. Home Assistant’s virtual-machine documentation also lists 2GB RAM as the minimum VM allocation.
That makes 2GB the useful official baseline, but a minimum requirement is not the same thing as the best specification for a new purchase.
A 2GB system can run Home Assistant, but there is less margin for:
- Large numbers of apps.
- ESPHome compilation.
- Local databases.
- Local voice services.
- Memory-heavy integrations.
- Future Home Assistant growth.
If you already own supported 2GB hardware, there is no reason to replace it simply because larger RAM options exist. If you are buying new hardware, however, 4GB or 8GB normally makes more sense.
Is 4GB RAM Enough for Home Assistant?
For a dedicated Home Assistant OS system, 4GB is enough for many installations.
That is also a useful real-world reference because Home Assistant GreenAliExpress price—the official plug-and-play appliance—ships with 4GB RAM. Home Assistant would not choose that configuration for its mainstream appliance if normal smart-home use demanded 16GB or 32GB.
A 4GB system is a good fit for:
- Automations and scripts.
- Normal dashboards.
- Zigbee, Z-Wave and Thread integrations.
- MQTT.
- ESPHome device management.
- Typical recorder/history usage.
- A reasonable number of Home Assistant apps.
The point where 4GB becomes less attractive is when the machine is no longer really a dedicated Home Assistant appliance.
Why 8GB Is the Best New-Build Default
If you are buying an N100 or N150 mini PC today, 8GB is a sensible default. Not because Home Assistant needs 8GB, but because the extra capacity is inexpensive on many systems and avoids buying a configuration with almost no future margin.
8GB gives room for:
- Home Assistant OS plus heavier apps.
- Larger ESPHome projects.
- Local voice components.
- Database growth.
- A later move to a small virtualised setup.
- Temporary spikes during updates or compilation.
For a dedicated HAOS box, going from 8GB to 16GB rarely makes Home Assistant itself noticeably faster. The extra memory is mainly future capacity.
When 16GB or More RAM Makes Sense
16GB becomes useful when the hardware is serving the wider home lab, not just Home Assistant.
- Home Assistant OS in a Proxmox VM.
- Several Linux VMs or containers.
- InfluxDB, Grafana or other monitoring stacks.
- Local AI or speech-processing services.
- Media servers.
- Development environments.
- Databases separate from Home Assistant.
At that point, size the memory for the complete server. Home Assistant may still need only a modest allocation while the rest of the host consumes most of the RAM.
Do You Need 32GB RAM for Home Assistant?
Not for Home Assistant alone.
A 32GB mini PC can be a very good home server, but buying 32GB purely for direct Home Assistant OS is usually unnecessary. Home Assistant does not become faster simply because large amounts of unused memory are installed.
Buy 32GB because you have identified other workloads that need it—not because a retailer offers a bigger number.
Official Storage Starting Point: 32GB
Home Assistant’s current Raspberry Pi guide requires a microSD card with at least 32GB. Its virtual-machine guides also commonly start with a 32GB virtual disk.
So 32GB is a valid Home Assistant storage size. It is not, however, the configuration we would deliberately choose for a new SSD-based mini PC unless there were a specific reason to minimise cost.
Storage usage grows from several sources:
- Home Assistant recorder database.
- Backups.
- Home Assistant apps.
- Media stored locally.
- ESPHome build files.
- Logs and temporary files.
- Local voice models and services.
64GB: A Comfortable Dedicated Home Assistant Size
For a dedicated Home Assistant appliance, 64GB gives substantially more breathing room than the 32GB minimum without becoming excessive.
It provides space for normal database growth, several local backups and apps while still leaving free storage for database maintenance.
64GB is especially sensible for:
- Raspberry Pi installations using larger microSD or SSD storage.
- Home Assistant-only mini PCs.
- Users who store backups externally.
- Systems that keep the default recorder retention close to standard settings.
128GB SSD: The Practical Mini PC Sweet Spot
For a new mini PC, 128GB is a very sensible SSD size. The capacity is still modest by PC standards, but it is much larger than Home Assistant’s basic requirement.
Why choose 128GB?
- More free space for database maintenance.
- More room for local backups.
- Space for larger apps.
- Better margin for future voice services.
- Cheap and widely available SSD size.
- Easy migration later if the mini PC becomes a broader server.
For many buyers, the price difference between a very small SSD and 128GB is too small to justify squeezing Home Assistant into the minimum possible space.
When 256GB or More Storage Makes Sense
Home Assistant itself does not need hundreds of gigabytes. Larger SSDs make sense when the computer stores more than Home Assistant.
- Multiple virtual machines.
- Container images.
- Large local databases.
- Media files.
- Local AI/voice models.
- Development environments.
- Longer local backup retention.
If you are buying 500GB, 1TB or more for a dedicated HAOS machine, you should be able to explain what will use that space. Otherwise the money is usually better spent on external backups or a UPS.
The Recorder Database Is What Usually Grows
Home Assistant’s recorder integration stores state changes and events in a database. The default and recommended database engine is SQLite, stored as home-assistant_v2.db inside the Home Assistant configuration directory.
By default, recorder data is automatically purged and Home Assistant keeps 10 days of history after a purge.
The database does not have one universal size. It depends on:
- Number of entities.
- How frequently they change state.
- How many events are recorded.
- Retention period.
- High-frequency energy or power sensors.
- Weather data.
- Presence trackers.
- Devices that update every few seconds.
This is why publishing a claim such as “Home Assistant uses exactly 2GB of database space” would be misleading. Two installations with the same number of devices can generate very different amounts of recorder data.
How to Check Your Home Assistant Database Size
You do not need to guess. Home Assistant exposes the estimated recorder database size in the system information panel.
- Open Settings.
- Go to System.
- Open Repairs.
- Open the three-dot menu.
- Select System information.
- Look under the Recorder section for Estimated Database Size.
The same system-information area also shows Home Assistant Supervisor disk usage, which helps you see whether apps or backups are consuming unexpected space.
Why Free Disk Space Matters More Than People Expect
Home Assistant’s recorder documentation states that you should always have at least as much free temporary space as the current database size. Database rebuild, repair, repack or schema-change operations may temporarily create another copy of data.
For example, if the recorder database is 2GB, treating the last 2GB of the drive as usable capacity is a bad idea.
Home Assistant also notes that if SQLite encounters unrecoverable disk corruption and has to move the database aside and create a new one, having around 2.5 times the database size available as free space can be essential for that recovery path.
This is another reason not to size storage so tightly that the SSD routinely sits almost full.
Should You Increase Recorder Retention?
You can increase purge_keep_days if you want more local history, but longer retention directly increases database storage requirements.
Before keeping months of raw state history locally, ask what problem you are solving. Home Assistant’s long-term statistics already preserve selected statistical data differently from short-term recorder history.
If you genuinely need longer raw history, monitor the database size after changing retention and make sure the storage capacity remains comfortable.
Exclude Noisy Entities Instead of Buying a Huge SSD
High-frequency entities can create disproportionate database growth. Power meters, rapidly changing signal-strength sensors, uptime counters and some tracking integrations may generate far more writes than a normal temperature sensor.
Home Assistant’s recorder integration supports include/exclude filters so you can avoid storing history for entities that provide no useful historical value.
This can be a better solution than simply buying a larger drive and allowing useless data to accumulate.
microSD vs SSD for Home Assistant
Home Assistant still supports microSD storage for Raspberry Pi and specifically recommends a good A2-rated card with at least 32GB.
However, the recorder documentation warns that database writes can affect SD-card reaction time and life expectancy. Home Assistant suggests reducing database writes, limiting stored data or placing the database elsewhere when appropriate.
For a system expected to run for years, an SSD is attractive because it usually offers:
- Higher write endurance.
- Better sustained I/O performance.
- Larger affordable capacities.
- Easier replacement.
- More comfortable database maintenance headroom.
This does not make every microSD installation unreliable. It simply means SSD storage is the more server-like choice when the hardware supports it.
How Much Space Do Home Assistant Backups Need?
Backup size depends on what is included. Home Assistant full backups can include configuration, share data, apps, SSL data and media.
Home Assistant itself recommends checking the recorder database and other large content before migration because large databases and apps increase backup size and restore time.
Automatic backups can retain several generations, so local backup storage can quietly become one of the largest consumers of SSD space.
The correct solution is not simply “buy a bigger SSD.” Home Assistant recommends keeping a backup on another system and ideally off-site as well. A backup stored only on the same SSD as Home Assistant is not enough if that SSD fails.
NAS Backups Reduce Local Storage Pressure
Home Assistant OS supports NFS and CIFS network storage, including network locations configured specifically as backup targets.
That lets you retain multiple backups on a NAS without filling the Home Assistant SSD. It also separates the backup from the hardware it protects.
Our dedicated guide covers that setup in Home Assistant Backups to UGREEN, Synology or QNAP NAS.
ESPHome: RAM and Storage Impact
ESPHome firmware compilation uses CPU, RAM and temporary storage. A small installation compiling one ESP32 configuration occasionally is not demanding, but large projects or repeated compilation can create temporary spikes.
An 8GB mini PC gives more breathing room than a minimum 2GB installation, especially if other Home Assistant apps are active at the same time.
Storage impact is usually modest, but stale build data and unused apps are worth cleaning rather than treating disk space as unlimited.
Local Voice Changes the Sizing Discussion
Local speech-to-text and text-to-speech services are more demanding than ordinary automations. They can use significantly more RAM, CPU and storage than the Home Assistant core workload.
If full local voice is part of the plan, 8GB RAM and a 128GB or larger SSD is a more sensible starting point than building around the minimum specification.
If local AI models, several voice pipelines or other server applications will share the same computer, size the system as a home server rather than as a Home Assistant appliance.
Home Assistant OS vs Proxmox: Do Not Confuse Guest RAM with Host RAM
If Home Assistant runs directly on the mini PC, all installed memory is available to HAOS and its apps.
With Proxmox, the host itself consumes RAM and every VM or container needs an allocation. Home Assistant may still run comfortably with a 4GB VM, while the physical mini PC needs 16GB or 32GB because several other services also need memory.
This is why recommendations such as “Home Assistant needs 16GB RAM” are often misleading: the server may need 16GB, while Home Assistant does not.
Which SSD Type Should You Buy?
Home Assistant does not need an extreme high-end PCIe 5.0 SSD. Reliability, compatibility and endurance matter more than benchmark speed.
For an N100/N150 mini PC:
- A mainstream NVMe SSD is ideal if the machine has an M.2 slot.
- A SATA SSD is also fast enough for Home Assistant.
- Avoid no-name SSDs with unclear endurance or warranty simply to save a small amount.
- Check the mini PC’s supported M.2 length and interface before ordering.
- Do not assume every M.2 slot supports both NVMe and SATA.
Home Assistant workloads are not performance-hungry enough to justify buying a premium gaming/workstation SSD purely for HAOS.
Practical Configurations
Budget dedicated Home Assistant
- 4GB RAM.
- 32–64GB reliable storage.
- External/network backup.
- Default or modest recorder retention.
Recommended new mini PC build
- 8GB RAM.
- 128GB NVMe SSD.
- Home Assistant OS directly on the hardware.
- Automated backups to NAS/cloud/external storage.
Power-user HAOS installation
- 8–16GB RAM.
- 128–256GB SSD.
- Several Home Assistant apps.
- Local voice or larger databases.
- External backup retention.
Proxmox home server with Home Assistant VM
- 16GB+ physical RAM.
- 256GB+ SSD.
- Home Assistant VM allocated according to its actual workload.
- Additional capacity sized for other VMs/containers.
How to Tell If You Need More RAM
Do not upgrade RAM simply because a larger module exists. Upgrade because the system shows evidence that memory is a constraint.
- Apps are being killed or fail under memory pressure.
- Heavy compilation or local voice causes obvious contention.
- You are moving to virtualisation and need additional guest allocations.
- You are adding memory-intensive services outside Home Assistant.
For direct HAOS, most users will reach a storage or architecture decision long before they discover that 8GB of RAM is insufficient.
How to Tell If You Need More Storage
- The recorder database is growing faster than expected.
- Disk usage is approaching uncomfortable levels.
- Automatic backups are consuming substantial local space.
- You keep long history retention.
- Apps create large datasets.
- You plan to add local voice models or other server workloads.
Before replacing the SSD, first check whether old backups, unused apps or noisy recorder entities are the actual cause. Good storage management is better than endlessly increasing capacity.
How Much RAM and SSD Storage Does Home Assistant Need? The Bottom Line
Home Assistant’s official minimum-class hardware remains modest: 2GB RAM and a 32GB-class storage device are enough to get started on supported platforms.
For a new dedicated system, however, 4GB RAM with 64GB storage is a more comfortable baseline, while an 8GB / 128GB SSD mini PC is the practical sweet spot for buyers who want sensible headroom without wasting money.
Choose 16GB+ RAM or 256GB+ storage because your other workloads require it. Home Assistant itself rarely justifies very large memory or SSD configurations.
The most important storage rule is not capacity alone: keep enough free space for recorder maintenance, control unnecessary database growth, and store backups somewhere other than the Home Assistant boot drive.
Continue the Home Assistant Hardware Series
- Intel N100 vs N150 vs N305 for Home Assistant
- Best Mini PCs for Home Assistant Compared
- Home Assistant Backups to UGREEN, Synology or QNAP NAS
Datasheets & External Resources
- Home Assistant – Installation options and minimum hardware
- Home Assistant – Raspberry Pi hardware requirements
- Home Assistant – Virtual machine minimum resources
- Home Assistant Recorder – Database retention and disk-space guidance
- Home Assistant – Backup guidance
- Home Assistant OS – Network storage and backup targets
