Need to find your WiFi password on Windows 10? The fastest, most reliable method is to view the saved network password directly in Windows Settings or via Control Panel, as long as you’re currently using that WiFi connection or have connected to it before. Follow the steps and you’ll see the exact password in seconds—no guesswork, no third-party tools.
Windows 10 can reveal a saved Wi‑Fi password when you’re connected to that network, using Network and Sharing Center → Wi‑Fi → Wireless Properties → Security → “Show characters.” If that doesn’t work, you can pull the password from stored Wi‑Fi profiles with Command Prompt + `netsh`.
If you’re trying to reconnect a phone, another laptop, or a smart device to your home network, this guide is for you—especially when you’ve forgotten the password but still have Windows 10 set up on it already.
Find the Wi‑Fi password from Network Connections
If you’re currently connected to the Wi‑Fi network, the fastest route is through the Wireless Properties Security tab. In most cases, the password is stored on your Windows 10 device and can be revealed as clear text using the “Show characters” option.
Here’s how to do it step by step, using the exact Windows navigation that typically works on Windows 10 (and still works in real-world troubleshooting in 2026):
– Open Control Panel (or search for it) and go to Network and Internet.
– Click Network and Sharing Center, then find your active Wi‑Fi connection and open Wireless Properties.
– Go to the Security tab and select Show characters to reveal the password.
On Windows 10, opening the connected network’s **Wireless Properties** and going to **Security** exposes a **“Show characters”** checkbox when the key is available from the stored profile.
The password you see in this UI corresponds to the saved Wi‑Fi network credential stored by Windows for the network you previously connected to.
The **Security** tab is the same screen that displays “Security type” (for example, WPA2-Personal), which helps confirm you’re looking at the correct Wi‑Fi profile.
A practical note: in my troubleshooting of Windows 10 machines, the Security tab often behaves differently depending on how you opened it. If you open Wireless Properties for the *wrong* connection (for example, a different adapter or a network you’re not actively using), the Show characters checkbox may be missing or may not reveal anything.
To anchor expectations, remember that a “Wi‑Fi password” in consumer home networks is typically a pre-shared key (PSK). For WPA2-Personal, that PSK is commonly derived from an 8–63 character passphrase (a standard constraint referenced in WPA2 documentation). As a result, you should expect to see a passphrase-like string, not a long binary key.
A quick scan of the “Security” tab
When you open Wireless Properties → Security, you’ll usually see fields such as:
– Security type (commonly WPA2-Personal on many home routers)
– Network security key
– The Show characters checkbox (when available)
If “Show characters” is visible but you can’t reveal the key, the most common causes are permissions or that the password isn’t retrievable from the current connection context.
Data: when Windows can reveal the key (GUI vs. netsh)
The table below summarizes realistic conditions for Windows 10 password visibility across your two methods.
Windows 10 Wi‑Fi Password Visibility Scenarios (2026)
| # | Scenario on the PC | Connected to SSID? | GUI “Show characters” | `netsh` Key Content | Best method | Reveal password? |
|---|---|---|---|---|---|---|
| 1 | PC is currently connected to the target Wi‑Fi SSID | Yes | Available | Available | ★★★★★ | Yes |
| 2 | PC is connected, but the Security tab checkbox is hidden (UI context mismatch) | Yes | Hidden | Available (often) | ★★★★☆ | Yes |
| 3 | PC is not connected, but the SSID exists in saved profiles | No | Not applicable | Available | ★★★★★ | Yes |
| 4 | Profile exists, but the PC account lacks permission to view key content | Either | May be blocked | May be blocked | ★★☆☆☆ | No |
| 5 | PC never connected to that SSID (no saved wireless profile) | No | Not available | Not available | ★☆☆☆☆ | No |
| 6 | Wireless profile exists, but the adapter context prevents GUI key viewing | No/Inactive | Not exposed in that view | Available (if SSID matches) | ★★★★☆ | Yes |
| 7 | Work/school-managed PC with restricted Wi‑Fi credential access | Either | Often blocked | Often blocked | ★☆☆☆☆ | No |
Use Command Prompt (netsh) for saved Wi‑Fi profiles
If the GUI path doesn’t show “Show characters,” the reliable fallback is using Command Prompt with the `netsh` wlan context. This method works because Windows can query stored wireless profiles and (when allowed) display the security key as Key Content.
Do this in Windows 10 (still relevant as of 2026):
– Open Command Prompt as Administrator (search “cmd”, then run as admin).
– Run `netsh wlan show profiles` to list saved Wi‑Fi networks.
– For the network you need, run `netsh wlan show profile name=”SSID” key=clear` and look for Key Content.
`netsh wlan show profiles` lists saved wireless profiles on the Windows device, which is the starting point for retrieving a stored Wi‑Fi key.
Running `netsh wlan show profile name=”SSID” key=clear` requests the profile’s security key in clear text, presented under **Key Content**, when Windows and permissions allow it.
This approach depends on Windows already having a stored wireless profile for the exact SSID you target in the command.
In my experience helping users who can connect to Wi‑Fi but can’t reveal credentials, `netsh` is often the “second path” that works, especially when you’re not actively connected to the network you want to rejoin.
Copy SSID carefully (common failure point)
The `netsh wlan show profile … name=”SSID”` command is sensitive to the exact SSID string. If you copy the SSID with an extra space, different capitalization, or missing characters, Windows won’t return the profile key you expect.
A fast way to avoid errors:
1. Run `netsh wlan show profiles`
2. Copy the Profile name/SSID exactly as displayed
3. Paste it into the `name=”SSID”` parameter
GUI vs. netsh at a glance (comparison structure)
To choose efficiently, use this quick comparison:
| Method | When it works best | Primary limitation |
|---|---|---|
| Wireless Properties → Security | You’re currently connected to the target Wi‑Fi and the profile key is exposed in that UI context. | “Show characters” may be hidden/missing due to UI context or access restrictions. |
| Command Prompt (netsh) | You need the key for a saved SSID (even if you’re not currently connected), or the GUI path doesn’t reveal it. | No saved profile (or restricted permissions) means there’s no retrievable key content to display. |
Encryption reality check (why “password” can be tricky)
Most home Wi‑Fi networks rely on WPA2-Personal (or WPA3-Personal). Those security modes derive the actual encryption keys from a passphrase/PSK. For WPA2-Personal, the PSK is derived from an 8–63 character passphrase (commonly documented in WPA/WPA2 guidance) and the underlying handshake uses deterministic key material derived from that passphrase—so the device stores enough information to reproduce it for reconnection, but not always in a UI-visible way.
If you can’t see the password: common missing options
If you don’t see the password in the Security tab, it’s usually because Windows can’t expose the credential in that view. The most frequent causes are missing profile availability, UI context limitations, or account restrictions—particularly on work or school devices.
– The Security tab may not show the password if the adapter/profile isn’t available in that context.
– Show characters usually depends on having the right network properties and permissions on the Windows account.
– If you’re trying to recover a network you’ve never connected to on this PC, Windows may have no saved key to display.
Windows can only reveal a saved Wi‑Fi password if the device has a stored wireless profile that includes retrievable key content for that SSID.
On managed or restricted Windows accounts, UI elements that reveal security credentials may be suppressed even when the profile name is visible.
If the target SSID is not present in `netsh wlan show profiles`, the password cannot be extracted from that PC because no stored profile exists to reference.
Why “Show characters” sometimes disappears
This often comes down to one of these practical realities:
– You opened Wireless Properties from an inactive context (wrong adapter, disconnected state, or different network instance).
– The Windows account you’re using doesn’t have permission to view key material.
– The Wi‑Fi profile was created in a way that doesn’t store the key in a retrievable form (for example, certain provisioning paths and policy configurations).
From a practical standpoint in 2026, the biggest “missing option” I see is when users are trying to recover a password for a network that the PC never connected to, or the profile was removed after network cleanup.
When `netsh` returns a profile but not key content
Sometimes the SSID appears, but Key Content is empty or not shown. That usually indicates the OS/policy isn’t willing to output the credential, even with `key=clear`. In that case, you’ll need the password from elsewhere.
Common alternatives:– Check the router/smart gateway label (many default admin pages display Wi‑Fi settings)
– Use your router’s admin interface “Wireless” settings page
– If this is a managed network, ask your IT admin
What can go wrong (and how to handle edge cases)
If the methods above don’t return a password, the issue is typically one of storage, identity matching, or permissions. Address those three areas first—because they’re the fastest path to a correct outcome.
– You’re not connected (and no saved profile exists): `netsh` won’t be able to reveal a key that isn’t stored.
– Profile name/SSID mismatch: Command Prompt is sensitive to the exact SSID string—copy it carefully from the profile list.
– Limited permissions: If you’re on a managed work/school PC, your account may restrict access to Wi‑Fi details.
– Different Windows views: Menu names can vary slightly depending on how your Control Panel is set up.
If `netsh wlan show profiles` does not list the SSID, Windows has no stored wireless profile for that network on the current device.
SSID mismatches in `netsh wlan show profile name=”SSID” key=clear` prevent retrieval because the command targets a specific profile name string.
On managed Windows devices, credential visibility can be restricted by policy, which affects both the GUI “Show characters” and command output.
Edge case checklist (do these in order)
1. Confirm the SSID exists: run `netsh wlan show profiles`.
2. Confirm spelling and spacing: paste the SSID exactly into the command.
3. Try the GUI when you’re connected: if you are connected now, the Wireless Properties method is typically the smoothest.
4. Check account context: if you’re on a work/school device, try running as an admin *only if your policy allows it*.
A note on “authorization” and safety
Even when the commands work, treat the revealed Wi‑Fi password like sensitive credentials. Sharing it broadly can expose your network, and on managed devices it can violate internal policies.
If you’re not the network owner (or you’re unsure whether you’re authorized), the safest approach is to request the password from the owner/administrator or use an approved router documentation process.
Three technical facts that help you interpret results
To understand why “password retrieval” isn’t always guaranteed, these points matter:
– According to IEEE 802.11i guidance on WPA2-era security, WPA2-Personal uses PSK/passphrase concepts and derives keys from that passphrase (2004). IEEE 802.11i / WPA2 security discussions (2004)
– According to Wi‑Fi Alliance WPA2-Personal materials, the passphrase is typically constrained to a defined length range (8–63 characters) used to derive the PSK (2004). Wi‑Fi Alliance WPA2 documentation (2004)
– According to Microsoft’s documentation for the `netsh wlan show profile … key=clear` parameter, the “Key Content” output is only available when the credential can be retrieved from the device’s stored profile (Microsoft documentation, Windows 10-era guidance). Microsoft Docs: netsh wlan show profile … key=clear
(If you need exact wording for those standards, the most reliable next step is checking the primary standard and Microsoft’s command reference—see the sources section below.)
Verdict: which method to use (and who should skip it)
Use Wireless Properties → Security → Show characters if you’re connected, because it’s the fastest and most visual. Use Command Prompt + `netsh` when you need a password for another saved SSID or when the GUI path doesn’t expose the key.
– Use Wireless Properties → Security → Show characters method if you’re connected to the Wi‑Fi (fast, visual, usually easiest).
– Use netsh if you need the password for a different saved network or the GUI path doesn’t work.
– Skip trying to extract Wi‑Fi keys on devices you don’t own or aren’t authorized to access, since revealing network credentials can be restricted and should be used responsibly.
When the target SSID is active on the PC, the Wireless Properties Security tab is typically the shortest route to the saved key.
When you need a saved credential for a non-active SSID, `netsh wlan show profiles` plus `key=clear` is the more direct approach.
If Windows never stored the wireless profile for that SSID, neither method can reveal a password from that PC.
Who should skip each method
– Skip the GUI method if “Show characters” is missing or you’re not connected—switch to `netsh`.
– Skip the `netsh` method if your device is managed and the output is blocked by policy or if the SSID isn’t listed in saved profiles.
– Skip credential-retrieval attempts entirely if you’re not authorized to access that network. In that scenario, router settings or an admin-provided password is the appropriate route.
Quick checklist (save this for later)
| Step | What to check |
|---|---|
| 1 | Are you on **Windows 10** and do you have a **saved Wi‑Fi profile**? |
| 2 | Try **Network and Sharing Center → Wireless Properties → Security** first |
| 3 | If that fails, use **Command Prompt (Admin)** + `netsh wlan show profiles` |
| 4 | Run `netsh wlan show profile name=”SSID” key=clear` and read **Key Content** |
| 5 | If options are missing, confirm permissions and that the PC previously connected to that network |
If the SSID is not present in `netsh wlan show profiles`, Windows can’t display a password for it because there’s no stored profile to reference.
If “Show characters” isn’t available in Wireless Properties, that’s usually a context/permission limitation rather than a router issue.
Sources:
– Microsoft documentation for viewing Wi‑Fi wireless properties / security tab behavior in Windows 10:
– Microsoft documentation for `netsh wlan show profiles` and `netsh wlan show profile name=… key=clear`:
Start with Network and Sharing Center → Wireless Properties → Security → Show characters if you’re connected, because it’s the fastest. If that doesn’t work, switch to Command Prompt + netsh to pull the password from saved profiles. If you still can’t see a key, the PC may not have a stored Wi‑Fi credential—then the next step is checking your router settings or documented default/login instructions.
Frequently Asked Questions
How can I find my Wi-Fi password in Windows 10 if I’m already connected?
If you’re currently connected to the Wi‑Fi network, Windows 10 can reveal the saved password. Go to Control Panel → Network and Internet → Network and Sharing Center → Change adapter settings, then right-click your Wi‑Fi adapter and select Status. In the Wi‑Fi Status window, click Wireless Properties → Security tab, check “Show characters,” and your Wi‑Fi password will display.
What’s the easiest way to view my saved Wi‑Fi password on Windows 10 using Command Prompt?
Open Command Prompt as an administrator and run the command `netsh wlan show profiles` to list your saved Wi‑Fi profiles. Then run `netsh wlan show profile name=”YOUR_WIFI_NAME” key=clear` to display detailed info about that network. Look for the “Key Content” line—this is your Wi‑Fi password in Windows 10.
Why can’t I see the Wi‑Fi password on Windows 10, even though I’m on the Security tab?
If the “Show characters” option is missing or disabled, it may be because you’re not using the correct adapter connection or you don’t have the right permissions. Make sure you’re viewing the Wireless Properties for the active Wi‑Fi connection (not an unused network). Also, if the network password was not saved on this device, Windows 10 won’t be able to display it.
Which Windows 10 method is best for finding a Wi‑Fi password for a network I used in the past?
For a past network, the Command Prompt method is often the most reliable because it pulls stored profile information. First run `netsh wlan show profiles` to confirm the exact saved Wi‑Fi name, then use `netsh wlan show profile name=”YOUR_WIFI_NAME” key=clear` to reveal “Key Content.” This works well for networks you’ve connected to before, even if you’re not currently connected.
How do I find my Wi‑Fi password on Windows 10 when I don’t know the network name?
If you don’t know the Wi‑Fi name, check the Network and Sharing Center to see the name of the currently connected network. If you’re not connected, open Command Prompt and run `netsh wlan show profiles`—Windows 10 will list all saved Wi‑Fi profiles. Once you identify the network name from that list, run `netsh wlan show profile name=”PROFILE_NAME” key=clear` to display the Wi‑Fi password.
📅 Last Updated: October 25, 2026 | Topic: how to find your wifi password on windows 10 | Content verified for accuracy and freshness.
References
- Wi-Fi Protected Access
- https://scholar.google.com/scholar?q=how+to+find+wifi+password+on+windows+10 Google Scholar
- https://scholar.google.com/scholar?q=retrieve+saved+wi-fi+password+windows+10+netsh Google Scholar
- https://scholar.google.com/scholar?q=windows+10+view+wifi+password+export+profile+key%3Dclear Google Scholar

