How to Change Raspberry Pi WiFi Details Directly from the SD Card

Tweet

Published: September 04, 2026

---

It is a scenario familiar to every embedded system engineer, IoT developer, and hobbyist: you deploy a headless Raspberry Pi to a remote corner of your home or workspace, only to lose access when your network configuration changes. Perhaps you updated your router, changed your WiFi SSID, typed a typo into your configuration file, or took your project to a new location. Without a dedicated monitor, keyboard, and mouse, you appear to be locked out.

Fortunately, you do not have to format your microSD card and start your project from scratch. By accessing the filesystem on the SD card directly from a host computer, you can inject new WiFi credentials and restore your wireless connection. Depending on the version of Raspberry Pi OS you are running, the methods differ slightly, but they are all straightforward once you understand how the system boots and manages network profiles.

The Headless Dilemma: Restoring Lost Connections

Understanding the SD Card Partition Layout

To safely modify configuration files, it helps to understand how the Raspberry Pi OS structures its storage. When you flash an operating system onto a microSD card, it creates two primary partitions:

• The Boot Partition (FAT32): This partition contains the bootloader, kernel images, and basic configuration files like config.txt and cmdline.txt. Because it uses the FAT32 file system, it can be read and written to by almost any operating system, including Windows, macOS, and Linux.
• The Root File System (ext4): Often labeled rootfs, this partition contains the core Linux operating system, user directories, application binaries, and system configurations. Because it uses the ext4 file system, it is natively readable only on Linux. Windows and macOS users will need specialized software or a virtual environment to access this partition directly.

Method 1: The Legacy Boot Trick (Raspberry Pi OS Bullseye and Older)

If you are running an older version of Raspberry Pi OS (such as Bullseye, Buster, or older legacy releases), configuring the network is incredibly simple. This version of the OS uses wpa_supplicant to manage wireless connections and looks for a configuration file in the boot partition during start-up.

To use this method, follow these steps:

1. Power down your Raspberry Pi safely and eject the microSD card.
2. Insert the card into your host computer's card reader.
3. Open the partition labeled boot in your file explorer.
4. Create a new plain text file in the root of the boot partition and name it precisely wpa_supplicant.conf. Make sure your operating system does not append a hidden .txt extension to the end.
5. Open the file in a text editor and paste the following configuration, replacing the placeholder values with your actual network details:

ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=netdev
update_config=1
country=US

network={
    ssid='Your_New_WiFi_SSID'
    psk='Your_New_WiFi_Password'
    key_mgmt=WPA-PSK
}

Ensure you update the country code to matches your region (e.g., US, GB, DE, CA) to comply with local wireless regulations. Once you save this file and insert the card back into your Raspberry Pi, the system will detect the file during the boot sequence, copy it to the correct system folder inside rootfs, apply the settings, and delete the temporary file from the boot partition.

Method 2: Configuring Modern Raspberry Pi OS (Bookworm and Newer)

With the release of Raspberry Pi OS Bookworm, the underlying architecture changed significantly. The operating system transitioned from wpa_supplicant to NetworkManager to handle networking. Consequently, placing a wpa_supplicant.conf file in the boot partition will no longer work on clean installs of modern OS versions.

NetworkManager stores connection details as keyfiles in the /etc/NetworkManager/system-connections/ directory. Because this folder resides on the ext4 rootfs partition, Windows and macOS users cannot modify it directly without additional tools.

Step-by-Step for Linux and WSL Users:

If you have access to a Linux machine, or use Windows Subsystem for Linux (WSL), you can mount the rootfs partition and edit the files directly:

1. Insert the SD card into your Linux host.
2. Locate the mount point of the rootfs partition (e.g., /media/user/rootfs/).
3. Navigate to the system connections folder using terminal:

cd /media/user/rootfs/etc/NetworkManager/system-connections/

4. You will find connection profiles here (usually named after your old SSID with a .nmconnection extension). If none exist, you can create a new file named preconfigured.nmconnection. You will need superuser privileges to edit or create files here:

sudo nano preconfigured.nmconnection

5. Add the following structure to the file:

[connection]
id=Preconfigured
uuid=3a2b4c5d-6e7f-8a9b-0c1d-2e3f4a5b6c7d
type=wifi
interface-name=wlan0

[wifi]
mode=infrastructure
ssid=Your_New_WiFi_SSID

[wifi-security]
auth-alg=open
key-mgmt=wpa-psk
psk=Your_New_WiFi_Password

[ipv4]
method=auto

[ipv6]
addr-gen-mode=default
method=auto

6. Save the file, make sure the permissions are restricted (NetworkManager requires configuration files to be owned by root and readable only by root, run sudo chmod 600 preconfigured.nmconnection), unmount the card safely, and boot your Pi.

Method 3: The Raspberry Pi Imager Configuration Trick

If editing ext4 partitions feels overly complex or prone to permission errors, you can use the official Raspberry Pi Imager to write a customized OS profile directly. While this is normally used for fresh installations, you can use it to flash a backup of your current setup or quickly provision a fresh instance with custom settings built right into the first-boot script.

In the Imager tool, clicking the gear icon (or pressing Ctrl + Shift + X) brings up the OS Customization menu. Here, you can define your SSID, password, and country code. The utility handles writing these configurations to the correct directories on the filesystem automatically, ensuring compatibility with whatever OS version you choose to write.

Method 4: Hardware Fallback via UART Serial Console

If you cannot read the ext4 partition and do not want to re-flash your system, there is an alternative hardware approach: bypass the network entirely. By using a cheap USB-to-UART serial cable (such as a CP2102 or PL2303 adapter), you can establish a direct console connection to your Raspberry Pi.

• Connect the adapter's TX pin to the Pi's RX (GPIO 10 / Pin 10).
• Connect the adapter's RX pin to the Pi's TX (GPIO 14 / Pin 8).
• Connect the GND pins together.

Enable serial interface support on your host machine, open a terminal client like PuTTY or GNU Screen with a baud rate of 115200, and boot the Pi. You will get a login prompt. Once logged in, run sudo raspi-config or use nmtui (NetworkManager Text User Interface) to update your WiFi credentials in a user-friendly terminal interface.

Best Practices for Headless Environments

To avoid getting locked out in the future, keep these practices in mind when designing headless setups:

• Configure Backup WiFi Networks: Modern operating systems allow you to store multiple connection profiles. If you take your Pi on the road, save both your office WiFi and your phone's portable hotspot credentials.
• Use Ethernet as a Fallback: Always test changes on a wired connection first if your Raspberry Pi board includes an RJ45 port.
• Enable SSH via the Boot Partition: Whenever you make changes, ensure an empty file named ssh (no extension) is placed in the boot partition to keep secure access enabled.

---

About EDATA SL

EDATA SL shares practical electronics, embedded systems, Arduino, ESP32, Raspberry Pi, IoT, repair guides, DIY projects and technical news for engineers, students and makers.

---

Original news rewritten with AI for educational purposes.