A Raspberry Pi 4 8GB running Shairport Sync turns any wired speaker or amp into an AirPlay endpoint in an afternoon. The Raspberry Pi 4 8GB has more than enough headroom for the AirPlay audio pipeline, mDNS discovery, and even AirPlay 2 features on capable installs, so the board can sit in a closet as an always-on receiver while the actual audio comes out of a proper amp or powered speakers.
Why a Pi 4 AirPlay receiver keeps coming back as a project
Every 18 months the same request cycles through r/homelab, r/raspberry_pi, and the Adafruit forums: someone has a nice pair of powered speakers, a decent stereo amp, or a set of in-ceiling speakers, and they want them to appear as an AirPlay target next to the HomePod and Apple TV in the iOS AirPlay picker. Commercial receivers exist, but the ones that actually work with AirPlay 2 cost as much as the speakers themselves. Meanwhile, a used Pi 4 8GB, a decent SD card, and a small USB DAC come in well under a hundred dollars and give a receiver that a competent user can maintain for years.
The Raspberry Pi 4 Model B product page lists the board's key specs — quad-core Cortex-A72 at 1.5 GHz, up to 8 GB of LPDDR4, gigabit Ethernet, dual-band 802.11ac Wi-Fi, and USB 3.0. Every one of those matters here. Wired Ethernet solves the single most common AirPlay complaint (dropouts). USB 3.0 hosts a class-compliant USB DAC without hub weirdness. 8 GB of RAM is overkill for audio streaming alone, but leaves the whole board available for a second job (Home Assistant, Pi-hole, a small music server) on the same physical device.
The MSI Raspberry Pi 4 Model B 8GB kit is the specific SKU featured here because it ships as a complete package — board, power supply, case, SD card — meaning the build starts with one Amazon order rather than five, and every part is known-good together.
What you'll need for the build
Minimal bill of materials for a functional receiver:
- A Raspberry Pi 4 8GB, ideally with the official 5.1 V / 3 A USB-C power supply. Undervoltage stutters are the second most common cause of dropouts after Wi-Fi congestion.
- A microSD card of at least 16 GB, U1 or better. Cheap slow cards work but drag boot times to a minute-plus and can corrupt after enough power-cycles.
- A wired Ethernet connection if physically possible. Wi-Fi works; wired eliminates the single biggest source of user complaints.
- A USB DAC or an I2S HAT for the audio output. The Pi's onboard 3.5 mm jack is functional but noisy for anything more than kitchen-speaker duty.
- The speakers or amplifier the receiver drives. Powered monitors, a stereo receiver's aux input, or a set of active in-ceiling speakers all work.
Optional but nice to have:
- A 1 TB SATA SSD like the Crucial BX500 in a USB 3.0 enclosure, if the same box will also host a music library. Not needed for AirPlay-only duty, but a common second-purpose upgrade.
- A pair of Bluetooth headphones like the BERIBES over-ear set for out-of-band listening while configuring — the Pi's terminal output can be piped over Bluetooth so the operator hears what's happening without bothering the household.
Key takeaways
- Shairport Sync is the receiver, not Apple. The Pi has no native AirPlay support; the open-source Shairport Sync project supplies it, and current builds implement AirPlay 2 features including multi-room grouping on capable setups.
- Wired Ethernet solves most dropouts. Wi-Fi works, but the busiest 5 GHz channel in a suburban neighborhood at 8 p.m. will crush AirPlay's latency budget.
- A USB DAC is the biggest single sound-quality upgrade. The Pi's 3.5 mm output is passable; a $30 USB DAC into a real amp is a noticeable step.
- 8 GB is overkill for audio alone. Which is exactly why it is the right pick — the same board can also run Home Assistant or a small music server without breaking a sweat.
Can a Raspberry Pi 4 run AirPlay 2 natively?
No, not natively — the Pi is not an Apple device and cannot participate in AirPlay without third-party software. Yes in practice — the Shairport Sync project is a mature, actively maintained open-source AirPlay server that runs on the Pi and, on current builds, implements AirPlay 2 features on top of the AirPlay 1 core. That includes discovery via mDNS/Bonjour, lossless-quality audio delivery from iOS/macOS devices, and, on supported configurations, multi-room grouping so several Pis can play synchronized audio in different zones of a house.
The nuance worth understanding: the AirPlay 2 spec is Apple's, and third-party implementations trail official first-party support in specific edge cases (HomeKit integration, some CarPlay-adjacent flows). For the common case — an iPhone or Mac wanting to play music to a receiver in the living room — a Pi 4 8GB with current Shairport Sync is functionally equivalent to a commercial AirPlay 2 receiver in the sub-$200 tier.
How do you install and configure Shairport Sync?
The high-level flow on a fresh Raspberry Pi OS Lite installation:
- Flash Raspberry Pi OS Lite to the microSD card using the official Raspberry Pi Imager from raspberrypi.com. Enable SSH and set Wi-Fi credentials during flashing so the board is reachable on first boot.
- Update and install dependencies. On the Pi over SSH:
sudo apt update && sudo apt full-upgrade -y, then install ALSA, Avahi (for mDNS), and the build dependencies listed in the Shairport Sync README. - Install Shairport Sync. On current Raspberry Pi OS releases,
sudo apt install shairport-syncgives a recent-enough version for most users. Users who want the newest AirPlay 2 features on the newest models should build from source per the project's INSTALL.md. - Choose an audio output. Edit
/etc/shairport-sync.confto point at the desired ALSA device — the onboard jack (hw:Headphones), an HDMI output (hw:vc4hdmi0), or a USB DAC (hw:Device— checkaplay -lfor the exact name). - Enable and start the service.
sudo systemctl enable --now shairport-sync. Within a minute the Pi's configured name appears in the AirPlay picker on any iOS device or Mac on the same network.
The Shairport Sync GitHub repository documents the full config schema, including buffer size, latency tuning, and audio-format selection. The defaults are sensible; adjust only if the setup misbehaves in a specific way.
Spec table: Pi 4 8GB audio outputs and their tradeoffs
Three physical output paths exist on the stock Pi 4 8GB, plus HAT-based add-ons:
| Output | Sample rate | Bit depth | Notes |
|---|---|---|---|
| 3.5 mm analog jack | 48 kHz | 16-bit effective | Noise floor is audible on quiet passages; fine for kitchen duty |
| HDMI (either port) | Up to 192 kHz | 24-bit | Requires an HDMI-audio-capable receiver or splitter; awkward for pure-audio use |
| USB 2.0/3.0 DAC | Up to 384 kHz | 32-bit | Class-compliant DACs work out of the box; huge sound-quality upgrade |
| I2S HAT DAC | Up to 384 kHz | 32-bit | Better than USB for critical listening; requires GPIO pins and a config change |
Latency for AirPlay is typically 2 seconds by default (the client buffers ahead), which is inaudible for music but noticeable when using AirPlay for a TV's audio. The buffer is tunable in Shairport Sync's config file if lower latency is required, at the cost of dropout tolerance.
How to add a DAC for better sound quality
Two paths, in rough order of cost and difficulty:
Path 1: USB DAC. Plug a class-compliant USB DAC (any DAC that lists Linux support, which is most of them) into any USB port on the Pi 4. Run aplay -l to confirm the OS sees it. Update /etc/shairport-sync.conf to point at the new device. Restart the service. This is a five-minute upgrade and typical audio-focused USB DACs in the $30-$120 range are a night-and-day improvement over the onboard jack.
Path 2: I2S HAT. These are hardware add-on boards that connect to the Pi's GPIO header and speak directly to the CPU over the I2S bus, bypassing USB entirely. Boards from HiFiBerry, IQaudIO, and similar vendors are well-supported by Raspberry Pi OS via device-tree overlays documented on the vendor sites. Sound quality is generally the best available on a Pi, at the cost of an install step (add a dtoverlay line to /boot/config.txt) and a fixed physical position on the header.
For a receiver that lives in a closet or behind an amp, the USB DAC path is almost always the right pick. For a dedicated audiophile endpoint, the I2S path is worth the extra effort.
Troubleshooting: dropouts, discovery, and multi-room
Dropouts (audio cuts out for a second or two, then resumes) are the single most common complaint. In descending order of likelihood: Wi-Fi congestion (move to Ethernet), undervoltage on the Pi's power supply (use the official 5.1 V / 3 A supply, check dmesg for undervoltage warnings), a saturated USB bus (do not plug the DAC through a hub shared with a spinning hard drive), and finally Shairport Sync buffer tuning.
Discovery failures (the Pi does not appear in the AirPlay picker) are usually a Bonjour/mDNS issue. Confirm the Pi and the iOS device are on the same VLAN and that mDNS is not being blocked by the router. On multi-VLAN home networks, an mDNS reflector configuration is required — the Adafruit forums have several long-running threads with example configs. On a flat home network, the Pi should appear within a minute of the service starting.
Multi-room grouping (the Pi appears but cannot be grouped with a HomePod) requires AirPlay 2 group support in the installed Shairport Sync version. Older Raspberry Pi OS packages ship an AirPlay-1-only build; building from source per the project README gives access to the newer features.
What hardware to buy for the build
The base BOM, plus common upgrades:
- Board: the Raspberry Pi 4 8GB kit covers board, PSU, case, and SD card in one order.
- Storage upgrade for dual-purpose use: a Crucial BX500 1 TB SATA SSD in a USB 3.0 enclosure gives the same box a real music library or a Home Assistant database that fits without SD-card wear concerns.
- Wireless listening while configuring: a set of Bluetooth over-ear headphones like the BERIBES model keeps the household happy while the build is being tuned.
- A DAC in the $30-$120 range — vendor choice is a matter of taste and the parent amplifier's inputs; class-compliant USB models are the low-friction pick.
Bottom line: is the Raspberry Pi 4 8GB the right board for an AirPlay receiver?
Yes, and it has been the default answer for four years running. The Raspberry Pi 4 8GB has more compute than an AirPlay receiver needs, enough RAM to also host a second lightweight service, gigabit Ethernet for the wired-network build that eliminates the majority of dropout complaints, and USB 3.0 for a modern DAC. Paired with Shairport Sync on a fresh Raspberry Pi OS Lite install, the build is a two-hour afternoon project that produces a receiver that can sit in a closet for years.
The alternative — a commercial AirPlay 2 receiver at $200+ — makes sense only if the user does not want to touch a config file. For anyone comfortable with a terminal and SSH, the Pi build is cheaper, more flexible, and easier to repair when something eventually needs updating.
What about the Pi 5 or the Pi Zero 2 W?
Two questions come up on every thread. First: is a Pi 5 better for this? The honest answer is no, not meaningfully. AirPlay audio decoding is trivial for a Pi 4's quad-core Cortex-A72, so the Pi 5's extra compute is idle. The Pi 4 8GB is also cheaper on the used market, well-documented, and — importantly for a set-and-forget appliance — thermally quiet without any fan intervention. The Pi 5's higher power draw and additional heat are a downside for an always-on receiver that sits in a closet.
Second: can a Pi Zero 2 W handle AirPlay? Yes for casual use with the onboard analog output or a small USB DAC, but the single-band Wi-Fi and lower USB throughput make it more prone to dropouts than a Pi 4 on Ethernet. The Zero 2 W is a great pick for a battery-portable AirPlay speaker embedded in a small enclosure; for a permanent household receiver behind a real amplifier, the Pi 4 8GB is the better long-term choice.
Comparing to commercial AirPlay 2 receivers
The commercial market for standalone AirPlay 2 receivers is thin. The HomePod and HomePod Mini are receivers built into speakers, not standalone endpoints. The Apple TV works as a receiver but ties up an HDMI input. Third-party receivers from brands like WiiM and Bluesound run in the $150-$400 range and are polished products, but they lock the user into a specific vendor's app, firmware update cadence, and support horizon. A Pi 4 build costs $80-$120 with a decent DAC, gives root access, updates on the user's schedule, and — critically — can be repurposed to something else entirely if the household stops using AirPlay. That flexibility is the actual sales pitch for the DIY route.
Common pitfalls
- Skipping the official power supply. The Pi 4 pulls up to 3 A at load, and cheap 2.5 A adapters cause silent audio artifacts that look like Wi-Fi problems.
- Cheap SD cards. A slow SD card makes the whole system feel broken; a U3-rated card from a real brand costs a few dollars more and lasts far longer under Shairport's small-write pattern.
- Wi-Fi where Ethernet is possible. The Pi 4's dual-band Wi-Fi is fine, but a wired connection is objectively more reliable in every home network condition.
- Assuming AirPlay 2 works out of the box on old packages. If the Pi appears but cannot be grouped, the installed Shairport Sync is likely too old — build from source per the project instructions.
- Ignoring undervoltage warnings.
dmesg | grep -i undervoltageis the first diagnostic to run when audio misbehaves. A brownout under load looks exactly like a network problem to the user.
Related guides
- Windows 98 Gaming PC with CompactFlash Storage in 2026
- Best SSD for Gaming in 2026
- DIY Wireless Fingerprint Authorization Device
Citations and sources
- Shairport Sync — open-source AirPlay receiver for Linux
- Raspberry Pi — Raspberry Pi 4 Model B product page
- Adafruit — Raspberry Pi tutorials and forum
This piece is editorial synthesis based on publicly available information. No independent first-party benchmarking is reported.
Disclosure: SpecPicks earns from qualifying purchases as an Amazon Associate; prices and availability may vary.
