Raspberry Pi Setup: From microSD to Your First Login¶
To set up a Raspberry Pi, write Raspberry Pi OS to a microSD card with Raspberry Pi Imager, configure your account and network, then boot and sign in. Choose the desktop path if you have a monitor, or enable SSH in Imager before writing the card for a headless setup.
This guide gets a new board to a working first login. It covers Raspberry Pi OS on Pi 4 and Pi 5; select your own device in Imager for other supported models. Raspberry Pi Pico is a microcontroller and does not follow this installation workflow.
Raspberry Pi setup in five steps¶
| Step | Action | Check before continuing |
|---|---|---|
| 1 | Choose Desktop or Lite and prepare a card. | The image supports your board; the card can be erased. |
| 2 | Select Device, OS and Storage in Imager. | Storage name and capacity match the intended card. |
| 3 | Configure user, location, Wi-Fi and remote access. | You know the username; SSH is enabled if you need it. |
| 4 | Write, verify and boot. | You reach the desktop or can log in over SSH. |
| 5 | Check the system, update and reconnect after reboot. | Network access and SSH survive the restart. |
Already have a running Pi? Skip to the first-login checks. You do not need to erase it to change Wi-Fi or enable SSH; use the NetworkManager guide or raspi-config guide.
If the Pi already runs Bookworm and you want to move its applications and data to Trixie, plan the backup and prepare a spare boot disk first. Bookworm to Trixie migration guide
Before you start¶
Prepare a board-appropriate power supply, a microSD card and reader, and another computer with internet access. Use a card with at least 32 GB for the desktop; the official minimum recommendation for Lite is 8 GB. For connector and assembly details, use the hardware setup guide.
Writing an image erases the selected storage
Back up anything you need before writing. Do not select the computer's system disk or a drive containing your files. Leave Imager's Exclude system drives protection enabled.
Start with microSD rather than adding USB/NVMe boot configuration to the first attempt. Specialised boot methods can come later.
1. Choose Desktop or Lite¶
| Your first task | Image to choose | How you sign in |
|---|---|---|
| Use a monitor, keyboard, browser or graphical apps | Raspberry Pi OS with desktop | Local desktop |
| Run a terminal-only server or electronics project | Raspberry Pi OS Lite | SSH from another computer |
| Use a remote graphical desktop later | Raspberry Pi OS with desktop | SSH first; configure remote desktop separately |
For Pi 4 or Pi 5, select the current 64-bit Raspberry Pi OS offered for that device. Desktop and Lite are different software selections, not different wiring requirements. Lite does not include a graphical desktop.
Use Imager's device-filtered OS list for older models instead of assuming every board can use the same 64-bit image. If a kit already has a working preinstalled OS, do not overwrite it just to follow this page.
2. Install Raspberry Pi OS with Imager¶
Download Raspberry Pi Imager for the computer that will write the card. The official Imager repository also documents installation; Raspberry Pi OS users can install rpi-imager through APT. Do not assume that package exists in every Linux distribution.
Insert the card and work through the current Imager screens:
- Device: choose your exact Raspberry Pi model.
- OS: choose the Desktop or Lite image selected above.
- Storage: match the card's name and capacity. If uncertain, disconnect unrelated external drives before selecting it.
- Continue to Customisation rather than writing an unconfigured image for headless use.
Current Imager uses a guided sequence. Instructions that depend on an old gear icon can refer to a different release. If you need a specific downloaded image, use Use Custom and select that image instead of writing it with an unreviewed raw-disk command.
Configure the settings you will need at first boot¶
Use a hostname such as pi-setup and your own username. Keep these choices handy for the first connection.
| Imager screen | Set | Why it matters |
|---|---|---|
| Hostname | A unique name, such as pi-setup |
Identifies the board on your network. |
| Localisation | Your location, time zone and keyboard layout | Sets local input and Wi-Fi regulatory settings. |
| User | Your own username and a strong password | Provides the login account and administrator password. |
| Wi-Fi | Exact network name and password, if using Wi-Fi | Lets the board join the network without a monitor. |
| Remote Access | Enable SSH if needed; choose password or public-key authentication | Makes the first remote login possible. |
There is no universal pi / raspberry login on a current fresh installation. SSH-key authentication also does not remove the need to retain your account password for sudo.
For key authentication, supply a public key file ending in .pub; never upload the private key. The headless setup guide explains key creation if you do not have one. Do not overwrite an existing key used for other systems.
Keep this first setup simple: a monitor or LAN connection is enough. Raspberry Pi Connect, USB gadget access and other remote options have separate guides.
Write and verify¶
Review the summary, confirm the intended storage again, then choose Write. Allow verification to finish before removing the card. If verification fails, resolve the reader, card or write error before trying to boot.
The official first-install instructions document the current screens and storage warnings.
3. First boot: desktop or headless¶
Insert the verified card, connect the peripherals or Ethernet you need, and connect power last. First boot includes provisioning and may take longer than later boots; do not repeatedly pull the power cable while it is working.
Connect the monitor before power-up; on a board with two HDMI connectors, use HDMI0 for the first test. Check that the monitor is using the matching input.
If you skipped customisation, complete the first-boot account and network wizard. If you preconfigured the image, do not assume the same wizard must appear. Open a terminal once you can use the desktop.
Use the Wi-Fi credentials configured in Imager, or connect Ethernet to the router. Connect the client computer to the same reachable LAN.
In a terminal on the client computer, replace your-user and pi-setup with the account and hostname you chose in Imager:
If the hostname does not resolve, find your Pi's address in the router. On first connection, check the host key fingerprint before accepting it.
For connection details, see the official SSH documentation and the headless troubleshooting tool. A .local failure is not proof that the board failed to boot.
4. Verify your first login¶
Run these on the Pi, in its local terminal or established SSH session. They inspect the system without changing settings:
Check the model and OS against what you intended to install. aarch64 indicates a 64-bit running kernel. In nmcli, look for the Ethernet or Wi-Fi interface you actually use to be connected; other interfaces can legitimately be disconnected. The route table should explain how that connection reaches the internet.
Confirm that the root filesystem has room for updates. Check your time zone and allow the network time service time to synchronise. Investigate failed services rather than assuming every entry prevents boot.
What was checked on real hardware
These read-only command blocks were verified on a Raspberry Pi 4B running Raspberry Pi OS based on Debian 13 Trixie, with a 64-bit kernel, on 13 October 2026. This checks the post-boot commands, not a new Imager installation or every supported board.
Make sure SSH will work after reboot¶
For a headless system, check both current operation and automatic startup:
active means SSH is running now; enabled means its service is configured to start automatically. In the normal Raspberry Pi OS service setup, you want both. If the service is disabled or stopped, use a local terminal or your existing authenticated session to enable and start it:
A different socket-activated SSH configuration needs separate interpretation; do not blindly replace a working custom setup. On this site's Pi 4B, SSH was unavailable after a reboot and returned after enabling and starting the service. The earlier startup state was not retained, so that incident does not establish exactly why SSH was unavailable. Check automatic startup before relying on unattended access.
5. Update Raspberry Pi OS, then reconnect¶
These commands change the installed system. Read APT's proposed changes and resolve errors before rebooting:
Use APT for normal kernel and firmware updates; rpi-update installs experimental/pre-release software and is not a routine first-setup step. See the official OS update instructions.
When the update has completed successfully and SSH startup is configured if needed:
An SSH session disconnecting during reboot is expected. Wait for the board to return, then repeat the hostname or IP login from the client computer. If its IP changes, check the router again.
Setup is complete when you can log in, use the intended network, and reconnect after a restart. Install project-specific packages after that; a first boot does not require a bundle of unrelated tools, GPU-memory tuning or overclocking.
If Raspberry Pi setup does not work¶
| Symptom | Check first | Next guide |
|---|---|---|
| Nothing boots, or a repeating status-LED pattern | Intended image, verified card, correct power supply; interpret LEDs for your model | Hardware setup |
| No HDMI picture | Monitor input, correct connector/cable, HDMI0, whether you installed Lite | Display and configuration |
| No network address | Wi-Fi credentials and location, compatible band, router/client isolation; try Ethernet if available | NetworkManager checks |
| Hostname fails but the IP works | Name resolution on the client network | Headless troubleshooter |
| SSH connection times out | Correct address and reachable network | Headless troubleshooter |
| SSH connection refused | SSH enabled and running on the intended board | SSH startup check |
| Permission denied | Imager username and matching password or private key | Headless setup |
sudo asks for a password after SSH-key login |
The account password created in Imager | Trixie sudo prompts |
Do not copy legacy wpa_supplicant.conf instructions onto current boot media or add old HDMI/Fake KMS settings as a universal fix. Change one confirmed cause at a time. Do not expose SSH through router port forwarding to complete an ordinary LAN setup.
Check your understanding¶
Can you identify which account and board you logged into, explain the difference between Desktop and Lite, and make a second connection without closing the first? Can you distinguish a hostname lookup failure from a refused SSH connection?
Do not erase a working installation or change network policy merely to repeat the tutorial. New software and circuit work should start from a verified login and known recovery path.
What to do after setup¶
- Basic Operations is the next learning path, starting with safe terminal practice.
- raspi-config for the specific interface or system setting you need.
- Security hardening before exposing services beyond the local network.
- C++ hardware programming or Rust for a first programming project.