How to reduce your homelab's power consumption
The fastest way to cut a homelab's power bill is to attack idle draw, because always-on gear spends most of its time idle. In rough order of impact: consolidate workloads onto one efficient low-power host (a mini-PC idles under 15 W versus 90-110 W for a rack server), enable CPU C-states and power management, spin down idle hard drives, right-size the power supply, and schedule machines off when they are not truly needed. Each idle watt removed saves about $1.49 per year at $0.17/kWh.
Where the watts actually go
Before changing anything, measure your real draw. Most people discover one machine dominates the bill — typically a secondhand enterprise server or an oversized custom build idling far higher than its workload needs. Networking gear and SSDs are usually a small, fixed background cost; spinning disks and idle GPUs are not.
High-impact changes, with annual savings
| Change | Watts saved (typical) | Saved / year (US) |
|---|---|---|
| Consolidate a 110 W rack server onto a 10 W mini-PC | 100 W | $148.92 |
| Enable CPU C-states / power management (typical) | 10 W | $14.89 |
| Spin down 4 idle 3.5" HDDs (~5 W each) | 20 W | $29.78 |
| Replace 80 Plus White PSU with Titanium at low load | 8 W | $11.91 |
| Undervolt / power-limit a GPU left idling | 10 W | $14.89 |
Estimates only — savings scale with your kWh price. Run your own numbers in the calculator. Source: HomelabWatts, data as of 2026-06-13.
The single biggest win: consolidation
The classic mistake is running a power-hungry old server 24/7 for workloads a tiny x86 box would handle. A modern Intel N100 mini-PC idles around 7 W and runs Proxmox, Docker and a dozen self-hosted services comfortably. Moving from a 110 W rack server to a 10 W mini-PC saves roughly $148.92 a year — often more than the mini-PC costs. See the mini-PC vs rack server breakdown.
Free software tweaks
- Enable C-states in BIOS and verify idle package states with
powertop(Linux) — frequently worth 10-20 W on used enterprise boards. - Spin down idle drives via
hdparmor your NAS power settings; each 3.5" HDD saves ~5 W when parked. - Power-limit or undervolt idle GPUs — a discrete GPU left in a host can idle at 15-25 W doing nothing.
- Schedule it off. If nothing needs 24/7 uptime, sleep + Wake-on-LAN cuts energy roughly in proportion to the hours saved.
What is usually not worth it
Chasing the last watt on networking gear, swapping efficient SSDs, or buying an exotic PSU for a low-power system rarely pays back. Focus on the one or two machines that dominate your measured draw.
Frequently asked questions
What uses the most power in a typical homelab?
For most people it is one always-on machine with a high idle draw — usually an old enterprise server or a workstation pressed into service. Spinning hard drives and idle GPUs are the next biggest contributors. Networking gear is usually a small, fixed cost.
Do CPU C-states really save power?
Yes. Disabled or shallow C-states (common on used enterprise boards and some mini-PC BIOSes) can add 10-20 W of needless idle draw. Enabling deeper package C-states and checking with powertop on Linux is one of the highest-impact, zero-cost changes.
Is it worth buying a more efficient PSU?
Only if your current PSU is badly oversized or low-efficiency. PSUs are least efficient at very low load, so a 750 W unit running a 40 W system wastes more than a right-sized 300-450 W unit. The savings are real but modest — usually a few watts.
Should I just turn the homelab off when not using it?
If your workloads are not truly 24/7 (no NAS access, no monitoring, no remote access), scheduling sleep or Wake-on-LAN can cut the bill dramatically — running 8 hours a day instead of 24 cuts energy use by two-thirds.
Last updated: 2026-06-13