How to Build a Home Server in 2026: Complete Beginner’s Guide

Why Build a Home Server Instead of Buying One?

Pre-built NAS boxes from Synology or QNAP are polished products, but you pay a significant premium for the enclosure and proprietary software. A self-built home server gives you far more flexibility: you choose the processor, how much RAM you want, what storage you use, and which operating system runs it. You can repurpose old PC hardware, or build something new for a couple of hundred pounds that outperforms a £400 commercial NAS on every metric that matters.

The use cases for a home server are broader than most beginners expect. Common reasons people build one include:

• Centralised file storage — a single place for backups, documents, and media accessible from every device on your network.
• Media server — running Plex, Jellyfin, or Emby to stream films and TV to any screen in the house without relying on subscriptions.
• Self-hosting — running your own password manager (Vaultwarden), ad blocker (Pi-hole), cloud replacement (Nextcloud), or dozens of other services via Docker containers.
• Home lab — learning virtualisation, networking, and Linux in a hands-on environment without paying for cloud VMs.
• Offsite backup target — using a server at a family member’s house as a remote backup destination via tools like rsync or Duplicati.

This guide covers everything you need to go from zero to a running home server: hardware selection at different budgets, operating system choices, the basic setup process, and the mistakes that catch most beginners out.

What to Consider Before You Buy Anything

Jumping straight to a parts list is a mistake. Spend time on these questions first, because the answers drive every hardware decision that follows.

What will the server actually do?

A file and media server has very different requirements from a virtualisation host. If you only want shared storage and Jellyfin for direct-play media, a low-power processor with integrated graphics and 8 GB of RAM is perfectly adequate. If you want to run five or six virtual machines simultaneously, you need more cores, more RAM, and potentially a dedicated GPU for transcoding or compute tasks.

Budget

A functional home server can be built for as little as £150 using second-hand enterprise hardware. A mid-range build with new components sits around £300–£500. A capable virtualisation host with plenty of storage headroom can run to £800 or more. Be honest about what you need — a server that runs 24/7 doing light file-serving duties does not need a twelve-core processor.

Power consumption

This is the most overlooked factor. A server that draws 80 W continuously costs roughly £105 per year in electricity at current UK average rates (around 24p/kWh). A server drawing 15 W costs around £32 per year. The difference compounds over the life of the machine. Idle power draw is the number to optimise, not peak performance, for any always-on machine.

Noise

Enterprise rack hardware — Xeon-based servers, ex-data-centre gear — is often extraordinarily cheap on eBay but sounds like a jet engine at idle. If the server lives in a room you use, check noise ratings before buying. Consumer and small business hardware is generally far quieter.

Physical space and cooling

Tower cases are easier to cool and quieter than rack units, and they sit unobtrusively next to a router. If you have a cupboard or utility room with decent airflow, a 1U or 2U rack unit becomes more viable. Hard drives need consistent airflow — they run warm and a poorly ventilated case shortens their lifespan.

Hardware Components: What You Need and What to Buy

CPU (Processor)

The processor determines how much simultaneous work your server can handle. For most home use, eight threads or fewer is plenty. Key considerations:

• Integrated graphics (iGPU) — essential if you want hardware video transcoding in Plex or Jellyfin without a discrete GPU. Intel’s Quick Sync (available on most Intel Core processors) is exceptionally good for this. AMD’s integrated graphics on Ryzen APUs are capable but less widely supported by media server software.
• TDP (thermal design power) — lower is better for an always-on machine. Aim for 65 W or below, and check actual idle power draw in reviews if you can find them.
• Core count vs clock speed — for virtualisation, more cores helps. For a simple NAS or media server, clock speed matters more than core count.

Budget option (under £150 build): Intel N100 or N305 mini-PC or mini-ITX board. These are sold under brands like Beelink and Minisforum on Amazon UK for £150–£250 as complete mini-PCs. The N100 draws under 10 W at idle and handles multiple 4K streams with hardware transcoding. Not upgradeable, but phenomenal value for a NAS or small self-hosting setup.

Mid-range (new build, ~£300–£500): Intel Core i3-12100 or i5-12400. Both have excellent Quick Sync iGPU, reasonable TDP, and are available on Amazon UK for £100–£160. Pair with an H610 or B660 motherboard.

High-end / virtualisation host: AMD Ryzen 5 7600X or Intel Core i5-13600K if you want VM performance headroom. These draw more power at idle, so factor that into running costs.

Second-hand / budget option: Intel Core i3-8100 or i5-8400 on a B360 or H370 board. Available used on eBay UK for £40–£80 for the CPU alone. These still have Quick Sync and will run a home server comfortably.

RAM

Memory requirements depend entirely on your use case:

• Basic NAS / file server: 8 GB is sufficient. TrueNAS Scale and most Linux distributions run well on 8 GB.
• Media server with transcoding: 8–16 GB. Plex and Jellyfin themselves are not memory-hungry, but if you run other services alongside them, 16 GB gives you breathing room.
• Virtualisation (Proxmox): 32 GB minimum if you want to run several VMs. Each VM needs memory allocated to it — a VM running 4 GB needs 4 GB reserved from the host.
• TrueNAS CORE (ZFS): ZFS traditionally benefits from more RAM for its ARC cache, though TrueNAS Scale is less demanding. 16 GB is a comfortable starting point.

Buy ECC RAM if your motherboard and CPU support it and you are using ZFS for important data. ECC detects and corrects single-bit memory errors, which ZFS itself cannot protect against. Consumer Intel Core and Ryzen desktop processors do not support ECC. If ECC matters to you, look at AMD Ryzen Pro chips, Intel Xeon, or AMD EPYC — though the latter two push costs up considerably.

Storage

Storage is usually the largest expense in a home server build. The choices here matter more than almost anything else.

Operating system drive: A 120–256 GB SSD for the OS is standard. A used 2.5″ SATA SSD costs £10–£20 on eBay UK. Keep the OS drive separate from your data drives — this makes reinstalling the OS without touching your data much easier.

Data drives: Hard drives remain the cost-effective choice for bulk storage. Current prices from Amazon UK and reputable UK retailers like Scan or Ebuyer:

Avoid SMR (Shingled Magnetic Recording) drives for NAS use — they perform poorly under the sustained writes that RAID rebuilds and large file copies produce. WD Red (non-Plus) desktop-class drives have historically included SMR. Always check before buying. WD Red Plus and Seagate IronWolf are CMR.

RAID or not? RAID is not a backup. It protects against a single drive failure but not against accidental deletion, ransomware, fire, or theft. A two-drive mirror (RAID 1 or ZFS mirror) provides redundancy with 50% usable capacity. For a beginner, a mirror of two 8 TB drives gives 8 TB of usable, redundant storage for around £300 in drives.

Case

The case determines how many drives you can house and how well they are cooled. Options at different scales:

• Mini-ITX tower: Fractal Design Node 304 (discontinued but available used) or the Fractal Design Node 202 hold 6 or 2 drives respectively. Good for compact builds.
• mATX/ATX mid-tower: Fractal Design Define 7 or Meshify C — quiet, good airflow, support multiple 3.5″ drive bays. Available on Amazon UK for £90–£130.
• Dedicated NAS cases: Silverstone CS380 (8 bays, mATX, ~£120) or the Inter-Tech IPC 4U-4129-N are built specifically for storage, with hot-swap bays and good airflow for drives.
• Repurposed desktop: Any mid-tower with 3.5″ bays works fine for a beginner build. Check the number of SATA ports on your chosen motherboard before buying drives.

Operating System Choices

The operating system shapes your entire experience. The main options for home servers in 2026:

• Proxmox VE — a free, open-source hypervisor based on Debian. Runs VMs and LXC containers. Ideal if you want to run multiple operating systems on one machine and learn virtualisation. Steep-ish learning curve but excellent documentation.
• TrueNAS Scale — purpose-built NAS OS based on Linux. Uses OpenZFS for storage. Excellent web interface, strong RAID support, good Docker app support via TrueCharts or the native Apps system. Best choice if storage reliability is the priority.
• Unraid — paid licence (from around $49 USD) with a distinctive parity-based storage model that lets you mix drives of different sizes. Popular for Plex/media builds. Not open source but widely used and actively developed.
• Ubuntu Server / Debian — installing a standard Linux distribution gives you maximum control and flexibility. No web interface out of the box, but you build exactly what you need with Docker, Cockpit, or manual configuration. Best for learning Linux properly.
• Windows Server — expensive to license properly and high resource overhead. Not recommended for home use unless you have a specific need for Active Directory or Windows-specific services.

Each of these has a dedicated setup guide on this site — see the linked articles for step-by-step instructions.

Basic Setup Steps Once Hardware Is Assembled

Once you have your components together, the process follows a consistent pattern regardless of which OS you choose.

1. Flash the OS to a USB drive. Use Balena Etcher (free, available for Windows and macOS) or the dd command on Linux. A 16 GB or larger USB drive is sufficient for any of the above operating systems.
2. Enter the BIOS and check settings. Enable AHCI mode for SATA (not IDE or RAID unless you are using a dedicated RAID controller). Verify your RAM is running at its rated speed (enable XMP or EXPO if you bought fast RAM). Set the boot order so the USB drive boots first.
3. Install the OS to the SSD. Follow the installer — most home server operating systems have guided installers. Choose your OS drive for installation; double-check you are not installing to a data drive.
4. Configure network settings. Assign a static IP address to the server — either via the server’s OS settings or via a DHCP reservation in your router. A server that changes IP address is frustrating to work with.
5. Update everything. Run system updates before configuring anything else. On Ubuntu/Debian: sudo apt update && sudo apt upgrade -y. On TrueNAS or Proxmox, check for updates in the web interface.
6. Set up SSH access. Enable the SSH server on your chosen OS and connect from your main PC using a terminal (ssh [email protected] on macOS/Linux, or PuTTY/Windows Terminal on Windows). This lets you manage the server without needing a keyboard and monitor plugged in.
7. Configure storage pools. On TrueNAS, create a ZFS pool using the web interface. On Proxmox, configure storage under Datacenter > Storage. On a plain Linux install, use mdadm for software RAID or install ZFS manually.
8. Install your first services. For most beginners this means setting up Samba shares for Windows file sharing, or installing Docker and bringing up containers. On Ubuntu, Docker installation takes about five minutes: follow the official Docker documentation and install Docker Engine (not Docker Desktop).

# Example: install Docker on Ubuntu Server\
sudo apt update\
sudo apt install -y ca-certificates curl\
sudo install -m 0755 -d /etc/apt/keyrings\
sudo curl -fsSL https://download.docker.com/linux/ubuntu/gpg \
  -o /etc/apt/keyrings/docker.asc\
echo "deb [arch=$(dpkg --print-architecture) \
  signed-by=/etc/apt/keyrings/docker.asc] \
  https://download.docker.com/linux/ubuntu \
  $(. /etc/os-release && echo "$VERSION_CODENAME") stable" | \
  sudo tee /etc/apt/sources.list.d/docker.list > /dev/null\
sudo apt update\
sudo apt install -y docker-ce docker-ce-cli containerd.io docker-compose-plugin

Power and Networking Considerations

UPS (Uninterruptible Power Supply)

A server that loses power suddenly mid-write can corrupt data. This is particularly dangerous with ZFS pools and databases. A basic UPS from APC or Eaton — available on Amazon UK from around £50–£80 for a 600 VA unit — provides enough runtime to gracefully shut down the server during a power cut. Connect it via USB so your server OS can monitor battery level and trigger an automatic shutdown.

Power supply selection

For a home server, efficiency matters more than outright wattage. An 80 Plus Gold or Platinum rated PSU wastes less power as heat across the range of loads. A 450 W unit from a reputable brand (Seasonic, Corsair, be quiet!) is plenty for most builds and runs more efficiently than an oversized 750 W unit at low loads. Seasonic units are well-regarded and widely available in the UK.

Networking

Connect the server to your router via Ethernet, not Wi-Fi. A wired connection gives consistent throughput, lower latency, and no dropped connections during large file transfers. Most home routers provide Gigabit Ethernet (1 Gbps), which transfers files at roughly 100 MB/s in practice — fast enough for 4K video streaming and most backup workloads. If you are moving very large files regularly, look at 2.5 GbE NICs and a 2.5 GbE switch; 2.5 GbE network cards cost around £20–£30 on Amazon UK.

Place the server as close to the router as practical. Long cable runs are not an issue — Cat6 cable handles Gigabit Ethernet at up to 100 metres — but minimise the number of switches in the path.

Common Beginner Mistakes to Avoid

Treating RAID as a backup

RAID protects against a drive dying. It does not protect against accidentally deleting files, a ransomware attack encrypting your data, or your house flooding. Follow the 3-2-1 rule: three copies of important data, on two different media types, with one copy offsite. Backblaze B2 (very cheap cloud storage), a second local drive, or a server at a friend’s house all work as the offsite copy.

Using SMR drives in a RAID array

Already mentioned above, but worth repeating because the consequences are severe. SMR drives perform extremely poorly during RAID rebuilds — a process that already stresses drives and can take many hours for large arrays. Always verify CMR before purchasing drives for a NAS or RAID array.

Not setting a static IP address

If your server’s IP address changes after a router restart, every device on your network that was pointing to it breaks. Set a DHCP reservation in your router (using the server’s MAC address) immediately. This is simpler than configuring a static IP inside the OS and achieves the same result.

Forgetting about drive temperatures

Hard drives are happiest between 30–45 °C. Install a tool like hddtemp or use your OS’s built-in SMART monitoring to watch drive temperatures. Above 50 °C consistently shortens drive life. Poor case airflow is the most common cause — add an intake fan blowing directly across the drive bays if temperatures are high.

No monitoring or alerting

A server is only useful if it stays running. Install basic monitoring from day one. Uptime Kuma is a free, self-hosted monitoring tool you can run as a Docker container — it checks that your services are up and sends you a notification if something goes down. TrueNAS has built-in SMART test scheduling and email alerts; configure them on first setup.

Opening ports without understanding what you are doing

Port forwarding exposes services to the open internet. If you forward port 80 to a Nextcloud instance running on default credentials, you will be compromised quickly. Use a VPN (WireGuard is straightforward to set up) to access home services remotely instead of direct port forwarding. Alternatively, use Cloudflare Tunnels to expose specific services securely without opening any ports on your router.

Buying the cheapest possible drives

Desktop hard drives (WD Blue, Seagate Barracuda) are not designed for the vibration environment of a multi-drive enclosure or the continuous operation of a NAS. They are also not rated for 24/7 use in most cases. Spend the extra £10–£20 per drive for NAS-rated CMR drives. The difference in reliability over a three-to-five-year lifespan is meaningful.

Not testing drives on arrival

Run a short SMART test on every new drive before putting data on it. A significant percentage of new drives fail within the first few weeks of use (the “burn-in” phase of the bathtub curve). TrueNAS can run extended SMART tests automatically. On Linux, smartctl -t long /dev/sdX runs a thorough surface scan. Catch failures before your data lives on the drive, not after.