Link a number by QR code, and what works differently
The unofficial way to start with the number you already use, like WhatsApp Web. The risk you accept, the two linking methods, and the features that behave differently on a QR-linked number.
Updated 29 October 2026
In Workspace settings › "Channels", choose "Link by QR code" in the "WhatsApp Connection" card. This connects a regular WhatsApp or WhatsApp Business number the way WhatsApp Web does. It is not an official Meta API connection.
Scan the QR code
- Press "Connect with QR".
- Open WhatsApp on the phone you want to connect.
- Go to Settings › Linked devices › Link a device.
- Point the phone at the QR code. The code refreshes on its own and expires after about 30 refreshes; press "New QR" if that happens.
Or use a pairing code (beta)
- Enter the WhatsApp number with its country code and press "Get pairing code".
- On the phone, in Link a device, tap "Link with phone number instead" and type the 8-character code. The code refreshes about every 45 seconds.
Scanning the QR code is the more reliable of the two. The status moves through "Waiting for scan", "Connecting" and "Connected", then shows the number. Keep the phone online; if the phone logs the device out, the card says so and you can link again or disconnect to go back to the Cloud API.
What is different on a QR-linked number
| Feature | On a QR-linked number |
|---|---|
| Interactive buttons and lists | Sent as a numbered text menu instead. |
| Catalogue, product and cart messages | Not available; the catalogue page is turned off. |
| Templates | Saved in the CRM only and not reviewed by Meta. Sent as normal messages: header image, then text. |
| Broadcasts | Capped at 200 recipients per campaign by default, sent 3 to 8 seconds apart. |
| 24-hour window, quality rating, messaging tiers | Do not apply. |
| Business profile | Cloud API only. |
| Editing a sent message | Works here, not on the Cloud API. |
To stop, press "Disconnect" and confirm in the "Disconnect this number?" dialog. If a Cloud API number was active before the link, disconnecting the QR session restores it.