QR Code Builder + UTM

How this tool computes its result

The tool composes a campaign URL from a destination URL plus UTM fields (source, medium, campaign required; term, content optional) via buildUtmUrl, then encodes that exact URL string into a QR code client-side using the qrcode package — generating both a PNG data URL (via toDataURL) and an SVG string (via toString) at a chosen pixel size (256/384/512) and margin (0/2/4 modules). The QR code is a static encoding of the final long URL; nothing about the QR image is dynamic or redirect-based.

Worked example

Destination "https://example.com/offer", source "event", medium "qr", campaign "trade-show-2026": buildUtmUrl appends the query string to produce "https://example.com/offer?utm_source=event&utm_medium=qr&utm_campaign=trade-show-2026", which is what actually gets encoded into the QR image and shown in the "Campaign URL" panel with a parsed breakdown of each utm_ parameter.

When not to use this tool

There is no link-shortening or redirect layer — the QR code encodes the full destination URL with query string baked in, so if you need to change the destination later (A/B test a landing page, fix a typo) you must regenerate and redistribute a new QR code rather than edit a redirect target.

Common mistakes

• - Leaving UTM source, medium, or campaign blank — generation is blocked with "UTM source, medium, and campaign are required." before any QR code is produced.
• - Entering a destination URL that buildUtmUrl cannot parse as valid — blocked with "Enter a valid URL to generate the QR code."
• - Choosing a small pixel size (256px) with a 0px margin for a print use case, which hurts scan reliability at small physical sizes since there is no quiet-zone padding.

Related tools