When you share Wi-Fi at home, in a shop, or in a meeting room, reading out a long SSID and password or asking someone to type them manually creates plenty of opportunities for mistakes. Wi-Fi credentials can be encoded in a QR code so that supported phones can scan it and continue to the connection flow.
Browser Kitty's Wi-Fi Share creates a Wi-Fi connection QR code locally in the browser from the SSID, password, and security type. You can show it full-screen, save it as PNG, print an A4 handout, copy the SSID or password separately, use the OS share sheet where available, or experimentally write Wi-Fi data to an NFC tag on supported Android browsers.
Start by verifying the SSID, password, and security type
You need the network SSID, Wi-Fi password, and security type. Enter the SSID exactly as shown, including capitalization, spaces, and symbols. If your router exposes similar 2.4 GHz, 5 GHz, or Guest names, choose the network that visitors should actually join.
Wi-Fi Share supports WPA / WPA2 / WPA3 Personal, WEP, and open networks. If the selected type does not match the router, the QR code may fail even when the SSID and password are correct. Enterprise / EAP networks are outside the supported scope.
| Item | What to verify |
|---|---|
| SSID | Use the exact network name including case and symbols |
| Password | Use the value currently configured on the router |
| Security | Match the real WPA-family, WEP, or open-network setting |
| Hidden SSID | Enable only when the network is actually hidden |
A Wi-Fi QR code packages connection details
A Wi-Fi QR code contains connection information such as the SSID, security type, and password. On a supported device, the OS or camera app interprets that payload and offers the Wi-Fi connection flow. Browser Kitty does not directly change the receiving device's network settings.
Behavior after scanning depends on the device, operating system, and QR reader. One phone may offer to join the network, while another reader may only display the encoded text.
A QR code does not encrypt the Wi-Fi password
Turning a Wi-Fi password into a QR code does not encrypt it. The information is simply encoded into the black-and-white pattern, so someone who can decode the QR code may be able to use those credentials.
That makes a main home-network QR code a poor choice for public posting on social media or an unrestricted web page. For visitors or customers, a separate guest network can be a better source for the QR code when the router supports one.
Choose between on-screen display, PNG, and print
For a one-time handoff, the simplest approach is to show the QR code large on a phone or computer and let the other device scan it. Wi-Fi Share includes narrow-screen layouts and can use Screen Wake Lock as a convenience on supported platforms.
For shops, meeting rooms, accommodation, or other repeated sharing, save the QR code as PNG or use the A4 print layout. Printing the password as plain text is off by default, so you can enable it only when the use case needs a manual fallback.
Use separate SSID and password sharing when QR scanning is awkward
A camera-less computer, or a device that does not interpret Wi-Fi QR payloads as a connection action, may still require manual entry. Wi-Fi Share can copy the SSID and password separately and can show them in a large on-screen view for easier transcription.
Where the Web Share API is available, you can also invoke the operating system's share sheet. After that, you choose whether to send the information through messaging, email, nearby sharing, or another destination. A copied password enters the OS clipboard, so clipboard handling is also part of the device-side workflow.
Frequently used Wi-Fi details are stored only when you explicitly save them
Wi-Fi Share does not automatically persist everything you type. Credentials are written to the same browser's localStorage only when you explicitly choose to save that Wi-Fi entry. The saved list shows the display name, SSID, and security type without constantly exposing the password in the list.
This is separate from an operating system keychain or protected credential store. Clearing browser site data can remove it, and a web page cannot automatically read the Wi-Fi password already saved by the operating system.
Troubleshoot the credentials, security type, and receiving device separately
If the QR code scans but the network does not connect, verify SSID capitalization, spaces, and symbols; look for password confusions such as 0 versus O or 1 versus l; and make sure the security type matches the router. For a hidden SSID, also make sure that setting is correct.
A WPA3-only network can still fail on an older receiving device even when the QR code is correct. The QR code does not add Wi-Fi capabilities to the device, so final compatibility still depends on the receiving OS and hardware.
Regenerate saved and printed QR codes after credentials change
The QR code contains the SSID, password, and security data that were current when it was created. If any of those values change, previously saved PNG files and printed signs still contain the old credentials.
For a shop or meeting room, updating the network therefore means creating the new QR code and removing any old handouts or signs that still expose the previous credentials.
Wi-Fi details are processed in the browser
Wi-Fi Share processes the SSID, password, and QR generation in the browser, and the generated HTML uses a CSP containing connect-src 'none'. It also avoids analytics, telemetry, external fonts, and an application backend. The web version still needs the initial HTML request.
When you explicitly choose OS sharing, clipboard copy, localStorage saving, PNG save, printing, or experimental NFC writing, the selected data is handed to that destination. Local processing does not mean that these user-initiated output actions do not exist.
NFC tag writing is an optional path for supported Android environments
On Android browsers that support Web NFC, Wi-Fi Share can experimentally write Wi-Fi data to an NDEF-compatible tag. This provides a tap-based option in addition to showing a QR code.
Web NFC requires conditions such as a Secure Context, support is limited to particular browsers and devices, existing NDEF content is overwritten, and someone who can read the tag may be able to use the Wi-Fi information. QR remains the broader-compatibility default, with NFC as an optional extra.
Step by step
- Open Wi-Fi Share and enter the exact SSID of the network you want to share.
- Enter the Wi-Fi password and choose the real security type: WPA / WPA2 / WPA3, WEP, or open.
- Enable the hidden-network option only if the SSID is actually configured as hidden.
- Show the QR code and scan it with a supported camera or QR reader on another device.
- If the device offers a Wi-Fi connection prompt, confirm the SSID and connect. If not, use separate SSID/password copy or the large-text view for manual entry.
- For repeated use, save the QR as PNG or create the A4 print layout. Print the password as plain text only when the fallback is actually needed.
- Only if you need to recall the same network later, explicitly save it in the browser.
- If the SSID or password changes, regenerate saved PNGs and printed QR codes with the new credentials.
Wi-Fi Share
Share Wi-Fi connection details by QR code, copy, large display, print layout, and experimental NFC tag writing on supported devices.
Tips and limitations
- For customers or visitors, a separate guest network is often easier to manage than sharing the main network when the router supports it.
- If the QR code scans but the connection fails, verify the SSID, password, and security type first, then check the receiving device's Wi-Fi capabilities.
- A saved image or printed QR code is also a copy of the credentials. Remove outdated PNGs and signs when they are no longer supposed to grant access.
- Web Share, Screen Wake Lock, and Web NFC are optional helpers whose availability depends on browser, OS, and Secure Context requirements.
Frequently asked questions
Do I need to install an app to create a Wi-Fi QR code?
No. Browser Kitty's Wi-Fi Share runs in the browser.
Is the Wi-Fi password sent to a Browser Kitty server?
Wi-Fi Share processes the SSID, password, and QR generation in the browser, and the generated HTML uses connect-src 'none'. If you explicitly invoke OS sharing, you then choose the destination yourself.
Does the QR code hide the password from people who scan it?
No. The QR code contains the connection details. Someone who can decode it may be able to use the Wi-Fi credentials; QR encoding is not password encryption.
Can it work with both iPhone and Android?
It can work where the camera and OS support Wi-Fi QR payloads, but the exact behavior and supported network types vary by device and OS. Manual SSID/password entry remains the fallback.
Can I print the Wi-Fi QR code?
Yes. Wi-Fi Share includes an A4 print layout and lets you decide whether to print the password as plain text as well.
What happens after I change the Wi-Fi password?
Old QR codes still contain the previous password, so regenerate the QR code and replace any saved PNG files or printed signs that still use the old credentials.
Can the page automatically read the password of my current Wi-Fi network?
No. A web page cannot automatically retrieve the Wi-Fi password stored by the operating system, so you enter the SSID and password yourself.
Does it support Enterprise Wi-Fi?
No. The tool targets Personal Wi-Fi using an SSID and password, not Enterprise / EAP configuration.
Can I write the Wi-Fi details to an NFC tag?
On supported Android browsers, experimental Web NFC support can write Wi-Fi data to an NDEF tag. Support is limited, so QR is the more broadly compatible default.