PC replacement costs
Should you replace an old PC to save electricity?
Only if the replacement does the same job and the measured electricity saving repays the complete purchase cost soon enough. A more efficient computer can still be a bad purchase.
I run two kinds of computer workload that make a bad comparison look tempting. Home Assistant wants a small, dependable host that remains available all day. Local Ollama inference on an RTX 5070 Ti wants a capable GPU when I ask it to work. A tiny replacement may beat the GPU machine at idle power while failing the only job that made the GPU necessary.
So I start with the work, not the age of the case. If the new machine cannot provide the same storage, acceleration, ports, reliability, or software support, the electricity calculation is comparing different products.
Compare your measured wattage and purchase cost
The arithmetic is the easy part
For two machines doing the same work, the annual electricity saving is:
(old watts − new watts) × hours per day ÷ 1,000 × price per kWh × 365
Divide the complete net purchase cost by that annual saving to get simple payback. This does not include financing, future electricity prices, or a discount rate. It is a blunt test designed to stop a purchase from being called “free” because the new box uses fewer watts.
| Daily runtime | Annual saving | $250 payback | Five-year net saving |
|---|---|---|---|
| 24 hours | $113.88 | 2.20 years | $319.40 |
| 16 hours | $75.92 | 3.29 years | $129.60 |
| 8 hours | $37.96 | 6.59 years | −$60.20 |
| 4 hours | $18.98 | 13.17 years | −$155.10 |
Those are labeled example inputs, not claims about a particular old desktop or mini PC. Runtime changes the decision. These rows count operating hours only: they assume zero consumption outside those hours, or equal off-hours energy use that cancels out. If one machine sleeps at 2 W and the other at 8 W, calculate that difference too. For a fixed batch job, compare total kWh to finish the same work; a lower-power machine that runs much longer may use more energy.
First, prove both machines can do the same job
I write down the workload before looking at replacement hardware:
- Does it need to run continuously, or can it sleep?
- How much memory and storage does the real workload use?
- Are attached drives, capture devices, serial adapters, or special ports part of the system?
- Does the job need a GPU, hardware video encoder, virtualization feature, or instruction set?
- What happens to the service while the machine is rebooting or unavailable?
For Home Assistant, reliability and access to the required radios or USB devices may matter more than peak performance. For the local Ollama assistant, GPU memory and measured token speed are part of the job. A low-power machine that moves inference back to a paid cloud service did not necessarily save money; it moved the bill.
Measure the whole system at the wall
I do not compare a processor’s TDP with a mini PC product page. Neither number is the electricity bill. I want average wall power under comparable work, including the power bricks and external devices needed for the job.
If the old machine uses internal storage while the replacement needs a separate enclosure, the enclosure belongs in both the wattage and purchase totals. If a scheduled GPU job runs for an hour, a week-long measurement captures that better than a two-minute idle reading.
The always-on cost guide shows how I convert a meter’s kWh reading back into average watts and why an apparently idle service may still need to remain available.
The purchase price is not the sticker price
My net purchase cost includes what I actually need to pay to make the replacement usable:
- memory and storage that are not included;
- drive enclosures, adapters, network cards, or power supplies;
- a replacement license or paid software migration;
- shipping and tax;
- minus resale value only when there is a realistic plan to sell the old machine.
I keep setup time out of the first calculation because it is hard to price honestly, but I do not pretend it is zero. A two-year electrical payback can still be unattractive if the move creates a fragile system or consumes several weekends.
Test the existing machine before replacing it
Check whether an abandoned service prevents sleep or keeps disks and a GPU awake. If the workload can be scheduled or moved, measure the resulting system again. Consolidation may remove a host’s base load, but it also puts more services behind one failure.
When I would replace it anyway
Electricity is not the only legitimate reason to retire a computer. Unsupported software, unreliable storage, excessive noise, missing performance, or unavailable replacement parts can force the decision. In that case, I use the energy result to compare viable replacements rather than asking electricity savings to justify the entire purchase.
That distinction matters. “I need a supported machine and this one also saves $80 a year” is an honest decision. “This $600 computer pays for itself” is not, unless the measured saving actually reaches $600 within the period being claimed.
Check whether the result survives uncertainty
Repeat the calculation with a higher replacement draw, fewer operating hours, and the extras you have not priced yet. Keep measured inputs separate from estimates. If the proposed machine has not been measured doing this workload, the result is a projection, not a demonstrated saving.
Compare the payback with how long you expect to keep the machine. If replacement is already necessary, compare the incremental cost of the more efficient option with the alternative you would otherwise buy, rather than charging the entire purchase to energy savings.
Recalculate with your inputs
The payback calculator uses the same arithmetic. The table is a hypothetical comparison, not a test of a named mini PC. The linked local-AI article supplies workload context, not measured power for this calculation.