Apple Shortcuts WiFi QR code
Apple's current Shortcuts app includes a Create QR Code action. A WiFi shortcut can collect or reuse network inputs, build the connection text, create the QR, and pass the image into a save or share step.
This is most useful when you will run the workflow repeatedly. If you only need one WiFi QR, a normal browser generator is simpler and less error-prone.
Change WiFi name or password after printing
No reprint needed.
Create QR Code is a current Shortcuts action
Apple's 2026 Shortcuts update notes explicitly include the Create QR Code action and new styling options.
WiFi payload construction is the fragile part
A shortcut still needs correctly formatted network data; QR creation alone does not validate the WiFi fields.
Automation can expose secrets
Do not casually hardcode a real network password into a shortcut that you plan to share with other people.
The automation is useful when the same logic must run repeatedly or feed into another Apple workflow.
Collect network inputs, create the QR, and save or share it with fewer manual steps each time.
The generated image can flow into supported share, file, or app actions inside the shortcut.
When escaping, security modes, or maintenance become awkward, use a dedicated WiFi generator instead of expanding the shortcut indefinitely.
01
02
03
04
Workflow
Use ordinary Shortcuts building blocks, but treat the WiFi text format and credential handling as the parts that require testing.
Use text, variables, or Ask for Input for the SSID, password, and the security information needed by your intended WiFi QR format.
Assemble the payload in the syntax supported by the devices you plan to scan with, including correct escaping for special characters.
Use Apple's Create QR Code action to turn the prepared text into a QR image.
Send the image to the next supported Shortcuts action, then scan it on the actual receiving devices before relying on the automation.
The goal is a maintainable shortcut, not merely a one-time way to make a QR.
Run one shortcut instead of rebuilding the QR workflow manually each time.
Create the QR and then pass the image into a save or share action.
Automation is only useful if the generated code still works across the receiving devices you care about.
Comparison
Choose based on maintenance cost, not on which workflow looks more advanced.
Best when repeated inputs, branching, or follow-on actions justify building and maintaining an automation.
Best when you want to enter the WiFi details, create a tested QR, and avoid maintaining payload-building logic.
Questions about automating WiFi QR creation with Shortcuts.
Yes. Apple's current Shortcuts release notes explicitly reference the Create QR Code action.
Do not assume that. Build the workflow around inputs and actions you can verify rather than promising hidden credential access.
Avoid doing that if the shortcut may be shared. A WiFi password inside the automation should be treated as sensitive access information.
The QR can render correctly while the payload format, security field, password, or receiving-device support is wrong.
Use the browser generator when you want a direct create-test-download flow without maintaining your own WiFi payload automation.
If you do not need a repeatable Shortcut, use the browser generator, verify the network details, and test the finished QR on another device.
Open WiFi QR generator