Skip to content
ImgKiloImgKiloOpen tools

Twitter (X) QR Code Generator

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

Paste the URL from an X (Twitter) profile, post, intent tweet or DM compose endpoint. The studio encodes it into a standard QR that opens in the X app on phones with it installed, or the mobile web for everyone else. Export SVG for print or PNG for the screen.

Scan me

What to encode

Style

Frame

  • Files never leave your device
  • Runs in your browser
  • Free, no signup

How it works

  1. 1

    Copy the URL from X

    Profile, post, intent tweet or DM compose. The guide below covers each path.

  2. 2

    Paste it into the URL field

    The encoded payload updates live so you can verify before printing.

  3. 3

    Download SVG or PNG

    SVG for conference badges and posters, PNG for slides and screens.

What this Twitter (X) QR generator does

Profile, post or intent URLs

Any x.com permalink works. Profile for follows, post for amplification, intent for pre-filled compose.

Universal Links into the app

iOS and Android route the URL into the X app when installed, falling back to the mobile web otherwise.

Logo at error correction H

Adding a centre logo bumps error correction to 30% so the cutout still scans on consumer phones.

Where this helps

Events

Conference lanyard badge

3 to 4 cm profile QR. Networking introductions turn into follows in two seconds.

Talks

Speaker end-card slide

Profile QR on the last slide. Harvests follows from people who liked the talk.

Media

Press release header

Intent tweet QR with the announcement pre-filled. Journalists scan, post, amplify.

DTC

Product launch flyer

Post QR pointing at the launch tweet. Drives retweets without typing.

B2B

Trade show booth

Profile QR for follow-back. Big A4 print at 15 cm scans from across the aisle.

Marketing

Print magazine ad

Intent DM QR. Converts reader curiosity into a direct sales conversation.

Tips that help

  • 1

    Encode x.com, not twitter.com

    x.com is the canonical domain. twitter.com redirects, which costs cold-scan time and adds an interstitial.

  • 2

    URL-encode intent text

    Spaces become %20, ampersands become %26. Unescaped query characters truncate the URL on scan.

  • 3

    Drop tracking tails

    Strip `?s=20`, `?t=...` and `?lang=en` from copied URLs. Shorter payload, denser scan-friendly QR.

  • 4

    Unprotect the account for cold-scan posters

    Protected profiles hide posts from non-followers. The scan lands on a follow request screen.

How to point a QR at the right X URL

The Twitter-to-X rebrand left two domains, three URL formats and a handful of intent endpoints. A thin QR generator picks one and hopes. The actual work is choosing the canonical domain, the right surface (profile, post, intent), and the cleanest URL. This guide covers the four URL types you will actually need for X QRs.

The canonical X URL formats

Profiles use `x.com/yourhandle`. Posts use `x.com/yourhandle/status/POSTID`. The compose intent uses `x.com/intent/post?text=...`. The DM compose intent uses `x.com/messages/compose?recipient_id=USERID`. All four formats deep-link into the X app on iOS and Android via Universal Links, falling back to the mobile web for users without the app.

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

Use x.com, not twitter.com. The twitter.com domain still works but it 301-redirects to x.com. Each redirect adds a hop, which costs cold-scan time, and on iOS 17 the system shows a brief privacy interstitial during the redirect. The shorter x.com URL also encodes into fewer QR modules, making the print scan reliable at smaller sizes.

Drop locale tails (`?lang=en`) and tracking parameters (`?s=20`, `?t=...`) from the copied URL before encoding. The canonical x.com URL is the shortest, scan-friendliest form. Keep your own UTM parameters only if you need them for off-platform attribution.

How to copy the right URL from X

Profile URL: sign in on the web, click your handle in the sidebar, copy the address bar. The canonical form is `x.com/yourhandle`. Mobile: open the X app, tap your avatar, then the share icon next to your handle, choose Copy link. Drop any `?s=...` tail before pasting into the QR generator.

Post URL: open the post in the web feed, click the share icon below the post, choose Copy link. You get `x.com/yourhandle/status/POSTID`. On mobile, tap the share icon at the bottom of the post, choose Copy link. The URL deep-links into the app and opens the exact post on scan.

Read more

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.

Frequently asked questions

Honest answers to what people ask before using this tool.

Encode `x.com`. After the rebrand, x.com is the canonical domain and twitter.com 301-redirects to it. The redirect adds a hop, which slows the cold scan and adds a privacy interstitial on iOS 17 and later. The shorter `x.com/yourhandle` URL also encodes into fewer QR modules, which means a denser, more scan-friendly print at small sizes. The X Help Centre treats x.com as the canonical address.

Use `https://x.com/yourhandle`. Open your profile on the web, copy the address bar, drop any `?lang=en` or tracking tail. No trailing slash needed; x.com works with or without it. The QR opens the profile in the X app on phones with it installed, or the mobile web for everyone else. Avoid the legacy `twitter.com/yourhandle` form; it works but redirects, which costs cold-scan time and bytes.

Yes. Every post has its own permalink: `https://x.com/yourhandle/status/POSTID`. Tap the share icon on the post, choose Copy link. Paste that into the URL field. The QR deep-links into the X app and opens the exact post, falling back to the web viewer. This is the right pick for a single campaign or announcement printed on a flyer.

Yes. Use the intent URL: `https://x.com/intent/post?text=Hello%20from%20the%20event`. Encode the message with URL encoding (spaces become `%20`). The QR opens the compose sheet with the text pre-filled. The scanner taps Post to send. This is the official intent endpoint X publishes for share buttons; it works the same when reached via a QR.

Yes. The intent URL `https://x.com/messages/compose?recipient_id=USERID` opens a fresh DM addressed to the user ID. Find your numeric user ID via a third-party lookup; X does not show it in the UI. Note that DMs require the recipient to have open DMs enabled, or to follow the sender. Without that, the compose sheet opens but the send button fails.

On iOS and Android, the system checks for the X app via Universal Links and App Links. If installed, the URL opens in the app. If not, the browser loads the same page. You do not need a custom scheme like `twitter://`. The public `https://x.com/...` URL works for both cases and is the format X documents for share integrations.

Yes for followers, no for cold scans. A protected account shows the profile photo, handle and bio to non-followers, with a follow request button. The recent posts are hidden until the request is approved. For a printed poster aimed at a public audience, this defeats the purpose. Either unprotect the account or point the QR at a public landing page instead.

Add UTM parameters to the URL: `https://x.com/yourhandle?utm_source=conference&utm_medium=qr`. X strips most parameters from internal navigation but the referrer shows up in your site analytics if the scanner clicks through to a link in your bio. For full attribution, encode a tracked redirect URL on your own domain. The QR analytics live in your tooling, not on X.

For a lanyard badge scanned from arm's length, 3 to 4 cm on a side works. The 10 to 1 distance rule says 4 cm scans cleanly from 40 cm, which matches two people at a networking introduction. Smaller than 2.5 cm and the camera misses focus. Export SVG so the print stays sharp at any size, and keep the logo cutout under 25% of the QR area.

Yes. The studio bumps error correction to level H when you add a logo, which reserves 30% redundancy so the centre cutout still scans. Keep the logo under 25% of the QR area. Use your own brand mark, not the X glyph; X's brand guidelines restrict third-party use of the logo in promotional materials.

Further reading

Independent references if you want to go deeper on the formats and tradeoffs.