iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
You can run a Raspberry Pi headlessly: prepare Raspberry Pi OS on another computer, configure networking and remote access in Raspberry Pi Imager, then administer the Pi over Ethernet or Wi-Fi. The safe approach is to match the power supply to the exact board, use a current OS, secure SSH or Raspberry Pi Connect, minimize exposed services, and maintain updates.
Raspberry Pi defines this arrangement plainly: “A headless Raspberry Pi operates without a monitor, keyboard, or mouse.” Raspberry Pi’s getting-started documentation describes the supported setup path.
What a headless Raspberry Pi needs
A headless Pi still needs the same essentials as a desktop installation, but you provide them before first boot or through the network:
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →- A compatible boot device, normally a microSD card, prepared with Raspberry Pi OS.
- A power supply capable of the power mode required by your particular Raspberry Pi model.
- A network path, either Ethernet or configured Wi-Fi.
- A remote-control method, usually SSH or Raspberry Pi Connect.
- A second computer, tablet, or phone from which to run the setup and later administration.
Raspberry Pi’s official setup guidance lists boot media and a power supply among the basic requirements and recommends Raspberry Pi OS Lite when you do not need a graphical desktop. Lite reduces the software you must maintain, but it also means graphical remote-desktop methods that depend on a desktop environment are not available. See the official headless setup guide.
#1 Best Overall
- CanaKit Power Supply for the Raspberry Pi 5
- Power Delivery (PD) Support, including 5V / 5A (27W) specially designed for Pi 5 and up to 45W for other devices
- UL Listed
- Includes noise filter for added stability
- Thick and insulated cable (4ft length)
Choose power and networking before you image the card
Use a model-matched power supply
Do not choose a supply solely by a generic wattage label or assume that every Pi uses the same connector and power mode. Read the requirements for the exact board and use a high-quality supply that provides that mode. A marginal supply can produce apparently random symptoms—failed boots, disconnects, storage errors, or peripherals that vanish—without giving you a useful screen message. Raspberry Pi’s installation and configuration documentation explains why the supply must match the board.
Also check the physical connector, the cable, and any adapter between the supply and the board. If you are powering a Pi in a remote location, secure the cable so movement cannot loosen it, and avoid sharing an undersized supply with unrelated USB loads.
Ethernet or Wi-Fi?
| Choice | What you need | Advantages | Limitations to check |
|---|---|---|---|
| Ethernet | A network cable and a board with an Ethernet port, or a compatible USB/Ethernet adapter | Usually the simplest first connection; no wireless credentials or radio compatibility issues | The Pi must be near a cable or suitable adapter; not every model has an Ethernet connector |
| Wi-Fi | A board or adapter with compatible wireless hardware, the network name and password, and a configured WLAN country | No cable is required and the Pi can be placed where wireless coverage exists | Some boards and adapters do not support 5 GHz; dual-band wireless remains disabled until a WLAN country is set |
Verify the board and adapter against your router rather than assuming that a “dual-band” network works with every Pi. Raspberry Pi’s configuration documentation records both the 5 GHz compatibility caveat and the WLAN-country requirement.
Recommended Free Tools
Prepare a headless installation with Raspberry Pi Imager
Do the preparation on a working computer before connecting power to the Pi. The labels in Imager can change between releases, but the sequence is the same.
Rank #2
- USB-C Connector for the latest Raspberry Pi 4 Model B
- DC 5. 1V 3 Amp Power Supply
- 15. 3 watts, 1. 5M cable (18AWG)
- Item Weight: 3.84 ounces
- Install Raspberry Pi Imager on the other computer and insert a compatible microSD card or other supported boot medium. Anything on that medium will be erased.
- Select the target Raspberry Pi model, then choose Raspberry Pi OS. Select Raspberry Pi OS Lite if the device will be administered from a terminal and does not need a desktop.
- Select the storage device you intend to use. Confirm its identity carefully so you do not overwrite another drive.
- Open the OS customisation settings before writing. Set a unique hostname that will help you identify the Pi, create the user account, and choose a strong password. Avoid reusing a password from another service.
- Configure the network. For Wi-Fi, enter the exact SSID and password and set the correct WLAN country. If you will use Ethernet, leave Wi-Fi unconfigured and plan to connect the cable before powering up.
- Enable remote access. Imager supports SSH configured with a username and password or with a public key. Choose the public-key option when you already have a key on the administration computer. Raspberry Pi Connect can also be used where it suits your access requirements and the installed OS supports it.
- Write the image and wait for verification. Safely eject the medium when Imager finishes, then insert it into the powered-off Pi.
Preconfiguring the hostname, account, network and remote access avoids the old assumption that you must attach a monitor for first-run questions. Keep the credentials you entered in a password manager; without them, a network-only installation can be difficult to administer.
First boot and first connection
- Connect Ethernet if you chose a wired network.
- Insert the prepared boot medium.
- Attach the model-matched power supply and allow the Pi to boot.
- Give the first boot time to complete. Raspberry Pi notes that it can take up to five minutes, depending on the board and SD card.
- From the administration computer, connect using the hostname you configured, the Pi’s address shown by your router, SSH, or Raspberry Pi Connect.
For SSH, a typical connection is ssh username@hostname. If local name resolution does not find the hostname, use the Pi’s current address from the router’s client list. Do not assume that an address will remain permanent unless you have deliberately configured a DHCP reservation or another address-management method.
Do not use the retired Bookworm Wi-Fi trick
Many older tutorials tell you to copy a wpa_supplicant.conf file into the boot partition. Raspberry Pi’s current configuration guidance says that method is unavailable from Raspberry Pi OS Bookworm onward. Use the current Imager customisation process instead. If Wi-Fi does not come up, connect Ethernet temporarily when possible and correct the wireless settings from the running system.
Choose SSH or Raspberry Pi Connect deliberately
| Method | Best fit | Authentication and setup | Important boundary |
|---|---|---|---|
| SSH | Terminal administration, automation, file operations and services that expose a shell | Enable it during Imager setup or on the Pi, then authenticate with a password initially or, preferably, an SSH key | It is a network service that must be restricted with account controls and firewall rules; do not expose it directly to the public internet as a default |
| Raspberry Pi Connect | Remote access through the Connect service when you prefer its account-based workflow | Configure it according to the current Raspberry Pi OS and Connect prompts, then sign in from your remote device | Availability and features depend on the installed OS and service configuration; it is not a substitute for securing the local user account |
Raspberry Pi lists SSH and Raspberry Pi Connect as first-boot remote-access choices. VNC can be used after first boot on an OS with a desktop, but it is incompatible with Raspberry Pi OS Lite, so selecting Lite commits you to terminal-oriented administration unless you later install a graphical environment. The supported connection options are described in the getting-started documentation.
Rank #3
- Standard: The black GaN 27W USB-C PD Power Supply (with 1.3M Length) for Pi 5 Output: 5.1V/5A Input: AC100-240V; It allows the the Pi 5 to power a wider range of peripherals.
- High Quality Power Solution: This GaN power supply can supply for Raspberry Pi 5 current up to 5.1V/5A to Pi 5 motherboard. In addition, there is no problem that low voltage appears even in full-load power operation.
- 6-layer Protection Function: Includes various functions such as over-power protection, over-current protection, short-circuit protection, over-voltage protection, low-voltage protection, and electrostatic protection.
- Good Compatibility: The GaN 27W PD USB-C Power Supply is also capable of delivering 5A@5.1V ,3A @ 9V, 2.25A @ 12V, and 1.8A @ 15V to PD-compatible products, making it a good cost-effective power supply for many general-purpose.Compatible with Raspberry Pi 5 16GB/8GB/4GB/2GB
- For Pi 5：The total power drawn from the four USB ports on Pi 5 is limited by default to a nominal 600mA; this limit is automatically increased to a nominal 1.6A when the USB-C PD Power Supply is detected.
Secure SSH after you get in
Prefer a key over a reusable password
Raspberry Pi’s operational-security guidance recommends key-based SSH authentication. If you did not add a public key in Imager, create one on the administration computer with its operating system’s OpenSSH tools, then add the public key to the Pi account while password login still works. Keep the private key private, protect it with a passphrase, and store a recovery copy in a secure location. Test a second login with the key before disabling password authentication.
Do not remove the only working authentication method first. A safe sequence is:
- Log in with the configured account.
- Add and test the public key from a separate terminal session.
- Confirm that the key works after a new connection.
- Only then consider disabling password-based SSH, if your workload and recovery plan support it.
Protect accounts and service access
- Use a unique administrative username and a long, unique password even when keys are enabled.
- Grant administrative privileges only to accounts that need them.
- Do not share one private key among every person or machine that might administer the Pi.
- Remove or disable accounts and services that are no longer needed.
- Keep a record of which account owns each application so that you can revoke access without taking unrelated services offline.
Reduce the network attack surface
A headless Pi is easy to leave running indefinitely, so its network exposure matters as much as its local login. Start with only the services the device’s job requires. A small sensor gateway might need SSH and one application port; it does not need a file-sharing service, web interface, or remote desktop merely because those packages are available.
Use a firewall to control allowed connections, as Raspberry Pi recommends in its operational-security guidance. Before enabling restrictive rules, identify how you will administer the Pi and which application ports must remain reachable. Permit management traffic from the networks or devices that need it, and avoid broad “allow from anywhere” rules. Test from another machine on the same network before closing your current session.
Rank #4
- Compatible only with the Raspberry Pi 2, Pi 3 and Pi 3 B+. NOT Compatible with Raspberry Pi 4 or Pi 5
- UL Listed
- 5-feet cable with integrated noise filter
- Micro USB plug
- Output: 5V DC / 2.5A Regulated Input: 100 - 240VAC
Do not make port-forwarding SSH from the public internet your normal remote-access plan. If you need access while away from home, use a properly secured private network or an access service designed for that purpose, and still retain strong local account controls.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Keep Raspberry Pi OS and applications maintained
Separate routine updates from a major OS upgrade
Routine package updates within your installed Raspberry Pi OS release are different from moving to a new major release. Raspberry Pi’s security guidance says only the newest major Raspberry Pi OS release receives all the latest security fixes. Plan a major upgrade as a change project: check application compatibility, make a restorable backup of configuration and data, schedule downtime, and verify every service afterward.
For normal maintenance, use the package manager to refresh package metadata and install available updates, then reboot when the kernel or another system component requires it. Review what will change before confirming, particularly on a Pi controlling hardware or running a database. Unattended upgrades can be useful for some roles, but they are not universally safe for every workload; choose an automation policy only after you understand how the application handles restarts and dependency changes.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteUse a maintenance checklist
- At each administrative visit: check that the expected services are running, that storage has free space, and that the system clock is correct.
- During routine updates: read the package changes, apply updates during a planned window, and check logs and application behavior afterward.
- After configuration changes: open a fresh SSH or Connect session before closing the one you used to make the change.
- Periodically: review user accounts, SSH keys, firewall rules, listening services, and router port-forwarding rules. Remove anything no longer required.
- Before major changes: back up application data and configuration and document how to restore them.
These checks are more useful than relying on an assumed uptime number. The official material does not establish a universal reliability figure for every board, storage device, power supply and workload.
Best Value
- 3.5A USB-C power supply specially designed and tested for the Raspberry Pi 4
- Includes noise filter for added stability
- 18 AWG Cable
- UL Listed
- 5ft Cable Length
Plan storage, power-loss and physical recovery
Keep the Pi where airflow, moisture protection and cable strain are appropriate for the exact model and workload, and consult the model-specific documentation for thermal and cooling requirements. Do not infer a safe temperature or SD-card lifespan from another board. If the workload writes heavily, evaluate storage and backup options for that workload rather than assuming every microSD card has the same endurance.
A remote device also needs a recovery plan. Record the board model, OS release, hostname, network method, account owner, backup location and the steps for re-imaging the boot medium. Keep a spare, compatible boot medium if the service is important. Test that you can restore application data and reconnect remotely; a backup that has never been restored is only an assumption.
Troubleshoot without attaching a monitor
| Symptom | Likely checks | Action |
|---|---|---|
| No device appears on the network | Power connector, supply compatibility, Ethernet link, Wi-Fi SSID/password, WLAN country, router client list | Power off, verify the model-matched supply and cable, try Ethernet, and confirm the Imager settings. Allow the documented first-boot period before deciding that it failed. |
| Wi-Fi works on 2.4 GHz but not 5 GHz | Board or adapter support and WLAN-country configuration | Check the exact hardware capabilities and set the correct country. Use 2.4 GHz or Ethernet if the hardware does not support 5 GHz. |
| Hostname does not resolve | Local DNS or mDNS behavior and whether the Pi received a new address | Find the current address in the router’s client list and connect by address. Consider a DHCP reservation for a stable local address. |
| SSH refuses the connection | SSH was not enabled, the username is wrong, a firewall blocks the port, or the service is not running | Use Ethernet or local recovery if available, verify the account and SSH configuration, and inspect firewall rules before changing ports or opening new ones. |
| Connection drops under load | Power supply and cable quality, network signal, storage errors, or a service consuming resources | Check power and cabling first, then review system and application logs and available storage. Do not assume a software reinstall fixes an inadequate supply. |
| You locked yourself out | Incorrect key permissions, a removed key, a changed firewall rule, or a disabled password login without a working key | Use a second tested administrator account or an approved local recovery method. If none exists, remove the boot medium, re-image it, and restore only verified data and configuration. |
A safe headless operating pattern
- Identify the exact board and its power requirement.
- Choose Ethernet when first-access uncertainty makes a cable practical; otherwise verify Wi-Fi band and country compatibility.
- Write Raspberry Pi OS with Imager and configure the hostname, user, credentials, network and remote access before boot.
- Use Raspberry Pi OS Lite for a terminal-only role, understanding that it is not compatible with VNC.
- Wait for first boot to finish, then connect through SSH or Raspberry Pi Connect.
- Replace password-only SSH with a tested key-based method where practical.
- Enable a firewall and permit only the management and application traffic the role needs.
- Apply routine updates, plan major OS upgrades separately, and verify services after changes.
- Maintain backups, recovery media and written access information so a failed card or configuration change is recoverable without a monitor.
Following that sequence keeps the Pi manageable without local peripherals while addressing the failures that matter most in a remote installation: unsuitable power, unavailable networking, weak authentication, excessive exposed services and untested recovery.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
