UniFi WiFi QR code
UniFi Network manages the SSID, password, security protocol, AP scope, VLAN context, and optional Hotspot behavior. A reusable QR should reflect the connection model actually configured for that WiFi.
For a straightforward personal pre-shared-key SSID that matches the generator's available security choices, create a QR from the verified values. PPSK, Enterprise, Passpoint, or captive-portal designs need additional onboarding context.
Change WiFi name or password after printing
No reprint needed.
UniFi manages WiFi at the SSID level
Current Ubiquiti guidance puts SSID name, password, AP broadcasting scope, and security settings under Settings > WiFi.
Advanced authentication changes the QR job
UniFi supports options such as PPSK, Enterprise/RADIUS, Hotspot Portal, and Passpoint that cannot be treated like one generic password QR.
UniFi Network is the source for the access model
Current Ubiquiti Network guidance documents SSID configuration, advanced authentication, Hotspot Portal, PPSK, Enterprise, and Passpoint. Use those controller settings to decide whether a simple credential QR is appropriate.
A UniFi network can be much more than one SSID and one shared password, so the QR should be a deployment decision rather than a generic router shortcut.
Know which APs, network/VLAN, and security settings sit behind the code.
Do not flatten PPSK, RADIUS, captive portal, or Passpoint into a simple password-only explanation.
For a compatible credential-based SSID, keep a tested master QR and place derivatives where the intended users need them.
Workflow
Verify the SSID first, pass a compatibility gate, then create and deploy the asset.
Select the SSID and review its network name, password, security protocol, and associated network.
Determine whether this is a simple personal PSK WiFi or an advanced PPSK, Enterprise, Passpoint, or Hotspot design.
For a supported credential-based network, enter the verified network name, password, and matching generator security choice.
Scan from the device types users actually bring and confirm the expected network and any subsequent onboarding step.
The reader can see the controller configuration and is responsible for how the QR is deployed.
Create a QR for a straightforward staff or visitor SSID without losing the UniFi network context.
Use the QR only for the part of the onboarding flow it can actually represent.
01
02
03
04
Comparison
The distinction is about authentication model, not brand.
A QR can represent the network name and shared credential when the security mode matches the generator and receiving devices.
These add identity, VLAN, profile, or web-authentication behavior that needs more than a generic shared-password QR explanation.
Questions about building a QR from UniFi-managed WiFi settings.
Current Ubiquiti guidance places them under UniFi Network > Settings > WiFi.
No. PPSK, Enterprise/RADIUS, Passpoint, and Hotspot Portal designs can require onboarding behavior beyond one shared-password QR.
No single QR workflow fits every UniFi SSID. The correct sharing method depends on whether the network uses a conventional shared credential, PPSK, Enterprise/RADIUS, Passpoint, or Hotspot Portal.
Use it when the network is a conventional credential-based WiFi that maps cleanly to the generator's available fields and has been tested on receiving devices.
Yes. Replace the static credential asset and every sign or file derived from it.
Verify the controller settings, create one reusable QR, and test the full association and policy behavior before deployment.
Create UniFi WiFi QR