How to make a QR code for a link
SmartQRCode editorial · Updated October 2026
How to make a QR code for a link covers any URL, including short links and campaign strings. Prefer a hosted SmartQRCode website type when the URL will move or you need totals. Encode the raw string as static only when the print must survive with no provider. Canva's widget is that one-off path.
How to make a QR code for a link without stuffing the modules
A link is bytes that start with a scheme the phone will dispatch, usually https. The making mistake is pasting a paragraph-long tracking URL into a static generator, then printing it at card size. Query string density raises version. Modules shrink. The card fails. Put parameters on a hosted link retarget destination instead.
How to make a QR code for a link that is a Google short name still densifies if you add unused parameters. Strip them. Scan and read the destination aloud before the run. If the short host is a phishing lookalike, the square will not warn anyone. The landing page must look like you. Hosted retarget can point a compromised poster at a warning; static cannot. How to make a QR code for a link you do not control is still a proof scan, plus a plan for when that third party changes the path. Prefer a hosted hop if you will need to retarget. Static ink freezes their path. How to make a QR code for a link you will retarget is therefore hosted from the first Download, even if today's URL looks final. Proof on paper. Read the destination aloud. Then print. How to make a QR code for a link ends there, not in the URL bar of a laptop already logged into the campaign. Close that laptop. Scan a second phone.
This is adjacent to a website QR but not identical. Website implies a site you control. Link includes app-store URLs, payment pages, and third-party short hosts. A website generator still encodes those as the URL type. Dynamic and tracking are the same hosted class under different searches.
Do not use the wifi type. A link is not a password. Do not screenshot the unpaid preview.
A link that requires an app the scanner does not have will look broken. Test on a phone without that app. If the fallback is a website, host that website as the destination. Static ink cannot grow a fallback later.
Short link versus long URL, then Download
- Decide hosted or static. Hosted if the URL will move or you need counts. Static if the paper must work after every account is gone.
- If hosted, create a website type whose first destination is the live link. Confirm it opens in a browser before you print.
- If static, shorten the URL first. Strip unused query parameters. A coarse grid beats a complete UTM set at 2 cm.
- Download SVG or a 300 dpi PNG at the final millimetres.
- Place the file with a four-module gutter. Do not crop finders.
- Print a proof. Scan from the real distance.
- For channel tests, use different hosted destinations, not two colours of the same static URL.
Data capacity is why the long URL looks like pepper. Static vs dynamic is why hosted ink stays coarse.
Is a short link safer as a hosted hop
A QR symbol is not an identity check. It does not prove the poster is who it claims. The destination does. Short-link hosts are a common phishing pattern in the wild. Saying so is allowed. Inventing a statistic is not. A hosted SmartQRCode hop does not make a malicious destination safe. It does let you point a compromised poster at a warning page; a static link freeze under a sticker cannot.
If trust is the job, the landing page's HTTPS certificate and content matter more than which generator drew the squares.
How do query strings change the printed grid
On a static file they are payload. Version grows. On a hosted type the printed pattern is the short address; you can add or remove UTMs later. That is the density reason to host campaign links even when you think you will never retarget. You might still want to add a parameter next week without reprinting.
Can you change the link after printing
Only if the modules stored a hosted address. Changing a Google Doc that you encoded as a static https://docs.google.com/... string does not update prints already on walls. Changing the Doc's contents might, if you encoded the same unchanging Doc URL. Changing to a different Doc does not. Hosted retarget covers that. Static does not.
App-store links, payment pages, and a scheme the phone will not dispatch
A link is not always https://. App-store URLs, custom schemes, and intent URLs behave differently per OS. Test iOS Camera and Android Camera on the actual destination. If iOS opens the App Store and Android opens a browser chooser, that is expected. Encode two hosted destinations only if you need two prints; SmartQRCode does not invent an eighteenth type for "smart OS split" on this page. Smart routing as a concept exists on hosted types; do not claim a flag state here. Proof both phones.
Payment links expire. A static print of a checkout URL that dies in 48 hours is a brick. Hosted retarget is how you point the same ink at a fresh checkout. If the payment provider forbids reuse, you needed a stable landing page in front of checkout, which is a landing-page type, not a raw link.
Mailto and tel links are still links. They densify like any byte string. Keep them short. They are not Wi-Fi. They are not trackable unless you wrap them in a hosted hop, and wrapping a tel: in a web redirect is a product choice you should test because some phones will not pass the scheme through.
Short-link vanity domains look clean and still densify if you encode them as static with extra query junk. Strip the junk or host.
Scan the proof. Read the destination aloud. If it is not the page you meant, stop the run. How QR codes work is decode; this page is which bytes you chose.
When a Canva static link should be the encoder
A single URL on a party poster, a classroom reminder, or a one-night board that will never be counted belongs in Canva's built-in QR. How to make a QR code for a link, in that case, is paste, print, scan. How to make a QR code for a link when the URL is a campaign you will retarget is the website type, Download SVG or PNG, and a proof scan at the real distance.
If the link is a PDF on Drive with "anyone with the link," confirm that setting before ink. A school that later restricts the PDF will look like a broken code. Hosted retarget can point at a public copy. Static ink cannot. If the link is a Zoom URL that expires, host a stable page that you update with the new Zoom. Do not print the Zoom string. Scan from a phone that is not already in the meeting.
Questions this raises
Short-link hosts are a common phishing pattern in the wild. A hosted SmartQRCode URL is still a hop. The destination page is what the scanner must trust, not the square.
On a static file they live in the modules, so version grows and squares shrink at the same millimetres. On a hosted type they sit on the destination.
Yes when the modules store a SmartQRCode website-type address. No when the modules store the final https string.
A one-off URL that will never move and will never be counted. That is the honest static-link job.
The camera decode does not. Opening an http destination does. A Wi-Fi payload is a different type and is not a link.
Keep going
The tools and playbooks this post refers to, one click away.
Make the code this post is about
$1.99 for 7 days, then a paid plan. Pick a type, brand it, and edit the destination whenever you like, even after it is printed.