QR code for Twitter (X) profile, post or intent tweet

Intent URLs are constructed, not copied. For a pre-filled post, start with `https://x.com/intent/post?text=` and URL-encode your message (spaces become `%20`, ampersands become `%26`). For a DM compose, use `https://x.com/messages/compose?recipient_id=USERID`. Test both URLs in a logged-out browser before printing.

Where the X QR earns its place

Conference and tech-event badges are the highest-value placement. The audience is already on X, the handle exchange is the social ritual, and a 3 to 4 cm QR on a lanyard turns a 30-second introduction into a follow that survives the event. Profile QR for general networking, post QR for one specific talk or release.

Speaker slides and end-cards are the second strong placement. A profile QR on the last slide harvests follows from people who liked the talk but will not type the handle. Post QR on the slide that announces the launch lets attendees retweet without finding the post manually.

Press kits and journalist packs benefit from intent QRs. A pre-filled tweet QR encodes the press headline and the link, so a journalist scans, hits Post and the announcement spreads. The intent URL is the format X publishes for embed buttons; on a QR, it works identically.

Common mistakes that kill scans

Encoding twitter.com URLs after the rebrand. The redirect still works but costs cold-scan time and bytes. The longer URL also encodes into a slightly denser QR. Always use the x.com domain for new prints.

Forgetting URL encoding on intent URLs. `https://x.com/intent/post?text=Hello world & welcome` breaks because the unescaped space and ampersand terminate the query. Encode them: `Hello%20world%20%26%20welcome`. Verify the URL works in a desktop browser before encoding to QR.

Pointing the QR at a protected account on a cold-scan surface. Non-followers see the profile shell and a follow request button. For a public poster, the scan dead-ends. Unprotect the account or use a public link in bio as the QR target.