Changing the Wi-Fi name (SSID) or password is straightforward, but every wireless device using the old details will disconnect as soon as the router applies the change. Planning the order avoids the common situation where you save the new password and immediately lose the admin page.

Before you change anything

Know how to reach the router again. If possible, make the change from a computer connected by Ethernet. Record the current SSID, security mode, and any separate 2.4/5/6 GHz names so you can reverse the change if a legacy device stops connecting.

Open the wireless settings

Sign in to the router or manufacturer app and look for Wi-Fi, Wireless, WLAN, or Network settings. The exact menu is model-specific. Avoid instructions that claim every router uses the same path.

Choose a useful network name

The SSID does not need to contain your address, surname, or apartment number. A neutral recognizable name is easier to identify without revealing unnecessary personal detail.

Set a strong Wi-Fi password

Use a long, unique passphrase and modern security supported by your devices. WPA2-Personal with AES remains widely compatible; WPA3-Personal improves protections when all required devices support it. Many current routers offer a WPA2/WPA3 transition mode for mixed households.

Reconnect deliberately

After saving, reconnect the device you are using first. Then update phones/computers, streaming devices, printers, cameras, and IoT devices. A guest network can use a different password so visitor access does not require changing every household device when it is rotated.

Admin password is separate

Changing the Wi-Fi password does not necessarily change the router administrator password. Review the admin credential separately and keep it out of guest QR codes.

Plan the reconnection

Changing the SSID or passphrase disconnects wireless clients. Keep the new values visible, use Ethernet if available, and update one band/network at a time. Smart-home/IoT devices can require manual reprovisioning if the network name/security changes.

Security mode matters

Prefer WPA2-AES or WPA3 where supported. Mixed transition mode can help older clients during migration. Avoid WEP and TKIP-only legacy modes.

Keep admin credentials separate

Do not reuse the Wi-Fi passphrase as the router administrator password unless the product forces that design. Separate credentials reduce the impact of sharing Wi-Fi with guests.

Before you change anything

Confirm the exact model and current network role, export/record the existing configuration, and make one change at a time. Prefer a wired connection for changes that can disconnect Wi-Fi. After saving, test both local connectivity and internet access before moving to the next step.

Rollback plan

Know how to reverse the change. Keep the previous value, configuration backup and ISP credentials available. A factory reset is not a rollback strategy unless you know every setting needed to rebuild the connection.

Change-control checklist for a home network

Small router changes can disconnect an entire household, so treat them like a miniature maintenance window. Photograph or export the current settings, write down the goal, and identify which devices can be affected. If you are changing Wi-Fi credentials, keep one wired or already-authorized management path available when possible.

Make one logical change

Avoid changing DNS, DHCP range, channel, security mode and router IP in one save operation. If the result is worse, you will not know which variable caused it. Apply one logical change, reconnect if necessary, verify the expected result, then continue.

Test the whole path

Do not stop at “the page saved.” Verify local gateway access, DHCP renewal, DNS, internet connectivity and at least one representative wired/wireless client. For security or forwarding changes, verify from the correct side of the firewall rather than only from inside the LAN.

Rollback without panic

Restore the previous value or configuration backup if the change fails. Factory reset is the last-resort rollback because it erases unrelated settings too. If ISP provisioning, VoIP or IPTV is involved, obtain provider-specific recovery details before resetting.

Write down the final state

Record the new LAN subnet, SSIDs, admin URL, reservations and other important changes. Future troubleshooting becomes much easier when the network no longer depends on memory.

Wi-Fi-specific evidence to collect

Record band, channel/channel width, RSSI/signal level if available, negotiated link rate, node/access point association and whether the same symptom occurs over Ethernet. A wired control test is especially valuable: if Ethernet is stable while Wi-Fi fails, focus on radio/interference/roaming rather than WAN or DNS.

Client compatibility matters

Old drivers, power-saving behavior, unsupported WPA modes and device-specific roaming decisions can make one client fail while every other device works. Update the client and test another device before changing the whole network around a single endpoint.

Verification after the procedure

Confirm that the requested change actually took effect and did not create a second problem. Renew/reconnect at least one client, verify the current gateway and DNS, test local router access, and test internet reachability. For Wi-Fi/security changes, check both a modern client and any important legacy/IoT device.

Keep the configuration maintainable

Use descriptive SSIDs/reservation names, avoid overlapping address ranges, and store administrator/ISP details securely. If the router supports configuration export, save a fresh known-good backup after the network is stable.

When instructions differ from your screen

Stop and identify the exact hardware revision, firmware and provider build. Menu names move between releases; forcing steps from another model can change the wrong feature. Use the current model manual as the tie-breaker.