How to Make a QR Code From a URL

Turn any public URL or short link into a QR code that scans cleanly, opens the right page, and can keep working after the printed file leaves your hands.

MV
Marisol Vega
Product · 2026-05-12 · 8 min read
$ duoqr edit menu-spring
- url: old.example.com/menu
+ url: spring.bistro12.com
✓ 14,238 codes redirected

Making a QR code from a URL is simple: paste the link, generate the code, download the file, and test it. The part worth slowing down for is everything around that paste box.

A QR code printed on a flyer, package, table card, poster, receipt, or event badge is not just a graphic. It is a link that has to survive bad lighting, phone cameras, redirects, campaign changes, and the occasional copied tracking parameter. If the URL is wrong, the QR code will faithfully send every scanner to the wrong place.

Use this guide when you need to turn a URL into a QR code you can actually publish.

Start with the final URL

First, decide what page the scanner should open.

Do not paste the first link you find in your browser bar. Check whether it is the public URL you want a customer, visitor, guest, or attendee to see. Internal preview links, admin URLs, staging domains, expired short links, and calendar links copied from the wrong account are common QR code mistakes.

Before you create a QR code for a URL, run this quick check:

  • Open the URL in a private browser window.
  • Open it on a phone, not only on your laptop.
  • Confirm it uses https://.
  • Remove unnecessary parameters that came from your own browsing session.
  • Keep intentional campaign parameters, such as UTM tags.
  • Make sure the page explains the next step without relying on nearby printed copy.

The URL should match the scanner's job. A table tent should open the menu, not the restaurant homepage. A product insert should open setup instructions, not the company blog. A conference badge should open the attendee profile, schedule, or lead form that the badge promises.

If your real goal is a website QR code for a broader page or landing page, the related guide on creating a QR code for a website covers that workflow in more detail.

Decide what kind of URL you are encoding

Most URL QR codes fall into one of three cases.

The first is a direct public URL, such as https://example.com/summer-menu. This is the cleanest input. It is easy to test, easy to understand, and usually easy to track with website analytics.

The second is a long tracked URL, such as a landing page with UTM parameters. This is fine, but keep the parameters intentional. A clean campaign URL might look like:

https://example.com/offer?utm_source=qr&utm_medium=print&utm_campaign=spring_flyer

The third is an existing short link. You can make a QR code from a short link, but be careful. A short link inside a QR code means the scanner goes through at least one redirect before landing on the final page. That may be acceptable, especially if your team already manages links in another system, but it also adds another place where the destination can break.

If the short link is temporary, owned by someone else, or hard to audit later, use the final destination URL instead. In DuoQR, the generated code already points to a managed short URL on the redirect domain, so wrapping an unknown short link inside it is usually unnecessary.

Use a dynamic QR code when the URL might change

A static QR code stores the URL directly in the QR pattern. If the URL changes after you print, the pattern cannot be edited. You need a new QR code and a new print run.

A dynamic QR code stores a short redirect URL instead. With DuoQR, a scanner opens a short r.duoqr.com link, and the resolver sends them to the current destination. That gives you room to edit the destination later while the printed QR code stays the same.

Use a dynamic QR code for a URL when:

  • The code will be printed on something expensive or slow to replace.
  • The destination is part of a campaign, event, menu, product launch, or seasonal page.
  • You want scan analytics before the visitor reaches your site.
  • You might need to pause, expire, or reroute the code.
  • Multiple teams may ask to change the destination after launch.

Use a static QR code only when the URL is permanent, low-risk, and you do not need scan data. The QR code expiration guide goes deeper on that decision.

Make the QR code from the URL

Once the URL is ready, the generation step should be straightforward.

  1. Paste the URL into the QR code builder.
  2. Choose a URL or website destination type.
  3. Name the code by where it will be used, such as lobby-poster-hiring-2026 or box-insert-setup-link.
  4. Keep it dynamic if the code will be printed or reused.
  5. Add campaign tags before launch if your website analytics need them.
  6. Choose a simple design with high contrast and a clear quiet zone.
  7. Export the file in the format your placement needs.
  8. Scan the exported file before anyone prints or publishes it.

The name matters more than people expect. Six months later, may-flyer-url is not enough context. A name that includes the surface, campaign, and purpose makes the dashboard easier to manage when a customer support message says, "the code on the back of the card goes to the wrong page."

Handle UTM parameters without making a mess

UTM parameters are useful when the QR code points to a marketing page. They let your website analytics separate traffic from a printed flyer, package insert, table card, or direct mail piece.

Keep the structure boring and consistent:

  • utm_source=qr
  • utm_medium=print
  • utm_campaign= followed by the campaign or placement name

For example:

https://example.com/demo?utm_source=qr&utm_medium=print&utm_campaign=expo_booth_card

Do not use a different naming style for every code. If one team uses qr, another uses QRCode, and another uses poster, your reports become harder to read.

DuoQR scan analytics and website analytics answer different questions. DuoQR can show that a code was scanned. Your website analytics can show what happened after the redirect. For a practical breakdown of that path, read trackable QR code guide.

Design the QR code so the URL can be reached

The scanner does not care how elegant the URL is. They care whether the phone opens it quickly.

Keep the QR design easy to scan:

  • Use a dark foreground on a light background.
  • Leave the quiet zone clear on every side.
  • Avoid placing text, icons, or artwork too close to the code.
  • Keep logos small enough that they do not damage the pattern.
  • Use a short call to action, such as "Scan for menu" or "Scan to register."

If the QR code is part of a branded layout, test the designed version, not only the default black-and-white preview. A QR code can be valid and still fail because the final artwork reduced contrast, cropped the quiet zone, or made the code too small.

For more design-specific guidance, read creating a custom QR code without breaking scans.

Test the URL QR code before launch

Do not stop at "the preview scanned once."

Test the exported QR code from the file or proof that will actually be used. If it is going to print, print one proof. If it is going into a PDF, open the final PDF. If it is going onto a digital sign, test it from the screen and distance people will actually use.

Check these items before approval:

  • The code opens the expected destination.
  • The destination works on mobile data, not just office Wi-Fi.
  • The page loads without a login wall unless the login is intentional.
  • UTM parameters remain attached after any redirects.
  • The printed size and contrast are enough for quick scanning.
  • The call to action matches the destination.
  • Someone outside the project can scan it and understand what happened.

For physical placements, use the high-resolution QR code print guide before the final order. Most print failures are preventable if you test the exported artwork instead of the generator preview.

Common URL-to-QR mistakes

The mistakes are usually small:

  • Pasting a staging, preview, or admin URL.
  • Using a short link that another team controls.
  • Removing UTM parameters that the campaign needs.
  • Keeping tracking parameters that came from an internal session.
  • Printing a static QR code for a URL that may change.
  • Sending scanners to a homepage when they expected a specific action.
  • Forgetting to test the final exported file.

The fix is also small: treat the URL as the product, not as an input field. If the link is specific, public, mobile-friendly, trackable, and editable when it needs to be, the QR code has a much better chance of doing its job.

When you are ready to make a URL into a QR code you can update later, create a DuoQR account, paste the destination, keep the code dynamic, and scan the exported file before it goes live.

MV
About the author
Marisol Vega

Marisol leads product at DuoQR. Before this, she ran ops at a chain of coffee shops where she printed too many menus. She writes about the boring problems behind shiny tools.

Keep reading

Related articles

Bi-weekly · No spam

One short email,
every other Tuesday.

New posts, the occasional product update, plus links to interesting QR-shaped things on the internet.

Trusted by 12,000+ readers · Unsubscribe any time