If one of your devices is already connected to a Wi-Fi network, the password may be saved on that device. Current versions of Windows, macOS, Android, iOS, and iPadOS all provide legitimate ways to view or share saved Wi-Fi credentials, although the exact menu names vary by release.
Windows 11
Open Settings → Network & internet → Wi-Fi and open the properties for the relevant network. Current Windows 11 builds can display the Wi-Fi security key after you authenticate. On systems where that option is not present, Control Panel → Network and Sharing Center → the Wi-Fi connection → Wireless Properties → Security → Show characters is the traditional route.
For networks saved on the computer but not currently connected, Windows command-line tools can also display profiles and keys when you have appropriate local permission.
macOS
On current macOS versions, the Passwords app or Wi-Fi settings can provide saved network credentials after user authentication. Keychain Access remains useful on older systems. Search for the network name, open the matching password item, and authenticate with your Mac account or Touch ID when prompted.
Android
Android 10 and newer generally let you share a saved Wi-Fi network from Settings. Open the connected or saved network, choose Share, and authenticate with the device PIN or biometrics. Android normally displays a QR code; many device versions also show the password in text.
iPhone and iPad
On iOS 16/iPadOS 16 and newer, open Settings → Wi-Fi, tap the information button beside a network, tap the password field, and authenticate with Face ID, Touch ID, or the device passcode. Apple devices can also share Wi-Fi access directly with another nearby Apple device without revealing the password to the person typing it.
Find it in the router
If you administer the network, the router or mesh app is usually the source of truth. Find the router gateway, sign in with the router administrator account, and look for Wireless, Wi-Fi, WLAN, or Guest Network settings. Some modern systems are app-only, and ISP gateways may use a provider app instead of a full local web interface.
Wi-Fi password vs. admin password
The Wi-Fi password lets a device join the wireless network. The admin password allows someone to change router settings. They should not be treated as interchangeable, and sharing a guest network does not require sharing the router administration credential.
Share access without typing the password
For a network you control, the Wi-Fi QR Code Generator can create a scannable code in the browser. Consider a separate guest network when visitors do not need access to computers, storage, printers, or smart-home equipment on the primary LAN.
Only recover or share credentials for a network you own or are authorized to use.
Password sources in order of trust
For your own saved Wi-Fi network, prefer the operating system’s authenticated credential viewer, then the router/app where authorized, then the device setup documentation. Avoid third-party “password reveal” software that asks for excessive permissions.
Enterprise/managed networks
802.1X enterprise Wi-Fi may use per-user credentials/certificates rather than a shared passphrase, so there may be no single network password to reveal. Guest captive portals can also authenticate separately from Wi-Fi encryption.
After recovering a shared password
If it has been exposed widely, rotate it, update trusted devices and consider a separate guest network instead of repeatedly sharing the primary LAN credential.
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.
How to verify what you learned on a real network
Use observation before configuration. Record the active client address, prefix/subnet, gateway and DNS; identify the router/mesh/gateway that supplies those values; and compare LAN state with WAN state. This gives you a baseline without changing anything. When you do make a change, alter one logical variable and repeat the same test.
Common edge cases
Guest networks can block local management. VPNs can install routes that overlap private LAN ranges. Access-point/bridge mode can make a device receive a new management address. Double-router networks can create two different private gateways. Cellular failover can make a phone appear to work even when Wi-Fi has no internet. These are reasons to inspect the active path rather than rely on a memorized default.
Security and privacy boundary
Use administrative instructions only on systems you own or are authorized to manage. A private IP is not a secret password, but router credentials and configuration are sensitive. Keep management interfaces on trusted networks, use strong unique administrator passwords, update supported firmware and avoid exposing local admin pages directly to the internet.
When instructions disagree
For a router address, reset sequence, firmware file, or credential workflow, the exact current model/provider documentation should take priority over a generic brand tutorial. For protocol behavior such as private addressing or subnet rules, use the networking standard rather than a router-specific shortcut. Community reports can help identify unusual symptoms, but confirm them before changing a working configuration.
Credential types you may encounter
A shared Wi-Fi passphrase protects network association; a router administrator credential protects configuration; a vendor cloud account protects remote/app services; an ISP account can authorize broadband service; enterprise Wi-Fi can use per-user 802.1X credentials/certificates. Recover the credential the prompt is actually requesting instead of reusing one password across roles.
After recovery
If the shared Wi-Fi password has been disclosed broadly, rotate it and consider guest Wi-Fi for visitors/IoT. If the router admin password was weak or reused, change it to a unique value and review remote-management settings and administrator accounts.
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.
How to validate the explanation on your own network
For How to Find a Saved Wi-Fi Password on Windows, Mac, Android, iPhone, and Your Router, look for an observable before/after signal: route table, lease, DNS answer, gateway reachability, radio association, WAN status, application behavior, or latency under load. A setting is understood when you can predict which observation it should change and which observations it should leave alone.
Keep recovery access available
When a change can affect Wi-Fi, LAN addressing, routing, or admin access, keep an Ethernet path or documented recovery method available before pressing Save.
Frequently asked questions
Should I make this change while connected remotely?
Prefer a local connection for changes that can alter routing, Wi-Fi, LAN addressing, firewall policy, bridge mode, or administrator access. A remote session can disappear immediately after a correct configuration change, leaving no safe rollback path.
What should I save before following this guide?
Record the current value, take screenshots where useful, and export the router configuration if the vendor supports it. Also note any ISP-specific WAN, VLAN, PPPoE, static-IP, voice, or IPTV requirements before changing network-wide settings.
How do I know the change actually worked?
Test the exact function the change was meant to affect, then verify that unrelated basics still work: DHCP, gateway reachability, DNS, internet access, and local admin access. For Wi-Fi changes, test both modern and older/IoT clients if they matter to your network.
When should I undo the change?
Roll back when the original goal is not achieved, a new failure appears, or the result cannot be explained. One reversible change at a time is much easier to troubleshoot than several simultaneous “optimizations.”