Skip to content
ConsultEvo

How to Create a QR Code: Choose the Right Method and Test It

To create a QR code, choose the destination URL, decide whether the code should be static or dynamic, generate it with a suitable tool, and test the finished asset before sharing or printing it. The reliable sequence is: choose the destination, choose the code behavior, generate the asset, validate access, scan the final design, and record who approved it.

A QR Code is a two-dimensional code that can encode data such as a web address. A phone camera can read it and open the destination. A standard QR Code Model 2 can encode up to 7,089 numeric characters, with lower maximums for other encoding modes. Capacity also depends on version and error correction, so a short HTTPS URL is usually more practical for a printed campaign than using the code’s maximum capacity. DENSO WAVE explains QR Code capacity and how the code is read.

Choose static or dynamic before you generate

A static QR code contains a fixed destination or payload. If the encoded destination needs to change, you generally need to create and distribute a new code. You can still update the content at a URL that you control, such as changing a menu page while keeping the same address.

A dynamic QR code typically uses a provider-managed redirect. Depending on the provider and plan, you may be able to change the destination after printing and view scan insights. This creates a dependency on the provider, your account, the selected plan, and the provider’s continuing service. Confirm what happens to the redirect after cancellation or a plan change before putting a dynamic code on a long-lived asset. Provider-reported scans are observations, not necessarily unique people.

Static

Fixed encoded destination

Best for a stable destination when you do not need provider analytics or post-print destination edits. You control the destination URL and can update the page it serves.

Dynamic

Provider-managed redirect

Useful when a printed asset must point to changing destinations or campaign measurement matters. Check ownership, plan limits, analytics access, export options, and redirect continuity first.

Before choosing a dynamic service, record the provider, code ID if available, current destination, campaign, owner, and last verification time. Confirm whether those details can be exported or documented. Do not assume that one provider’s editing, analytics, expiry, or cancellation terms apply to another.

Create a QR code with Canva or Adobe Express

Use Canva when the code will be placed directly into a larger design. Use Adobe Express when a browser-based generator and a downloadable standalone asset are sufficient. In either case, decide static or dynamic first, then test the result after it is placed in the final layout.

Canva

  1. Sign in to Canva and open the QR-code tool that matches your need: static or dynamic.
  2. Enter the destination URL and generate the code.
  3. Place it in the design, preserve clear space around it, and export the finished layout.

Canva documents free static QR-code creation, and its static app requires signing in or logging in. Dynamic editing, insights, expiry dates, collaboration, and some logo controls depend on the tool and plan. Canva recommends a minimum size of 2 x 2 cm, but that is not a universal guarantee of scan success. Use strong contrast, avoid transparency, and test any logo or brand styling in the finished design. See Canva’s QR-code guidance and its static QR-code app details.

Adobe Express

  1. Open the Adobe Express QR-code generator.
  2. Enter the URL, generate the code, and adjust its style or color only if the pattern remains clear.
  3. Download an available format such as PNG, JPEG, or PDF, then test the asset in its finished design.

Adobe Express advertises a free, browser-based generator and says its generated QR codes do not expire. The reviewed product page does not establish that every workflow is account-free, so confirm whether the current process prompts for an Adobe account. A logo or brand color is optional. Treat it as a design change that requires a real scan test, not as proof that the code will remain reliable.

Create a QR code from a webpage in Chrome

Chrome is useful when you want to share the page currently open in the browser. Before generating the code, check that the page URL is the intended public destination and does not contain a session token, private document parameter, or temporary access link.

  • Desktop: Open the page, select More, then Cast, save and share, then Create QR code. Download or share the result.
  • iPhone or iPad: Open the page, use Share, and choose Create a QR code. If the option is not visible, check the additional sharing options.
  • Android: Open the page, select More, choose Share, then QR Code.

See Google’s Chrome instructions. Menu names and locations can vary by device and change with Chrome updates. Chrome is suitable for a quick representation of the current page. If the destination needs campaign tracking, an editable redirect, or a controlled permanent URL, prepare that destination first and use a generator that supports the required behavior.

Choose an online QR generator

Choose a generator by the job it must do, not by an unqualified vendor ranking. Compare fixed versus editable destinations, analytics, design controls, vector or print-ready downloads, supported payloads, API needs, plan restrictions, and service continuity. Vendor feature pages describe advertised capabilities, so verify the selected plan and test the downloaded asset.

Generator Best fit Advertised capability Check before use
QRCode Monkey Static branded assets Color, logo, design, and vector-output options Codes are described as static and not editable. Test styling and logo overlays.
Uniqode Campaigns needing editable destinations or insights Dynamic destinations, analytics, branding, and downloadable files Verify plan eligibility, editing limits, analytics access, retention, and continuity.
QR Code Generator Projects assessing dynamic codes or tracking Editable destinations, scan tracking, multiple code types, and an advertised API Check current plan terms, account conditions, file format, and provider dependency.

For print production, confirm the actual download format, resolution or vector availability, and any usage restrictions on the chosen account. If you do not need tracking or post-print edits, a static code avoids dependence on a provider-managed redirect.

Decision point

A dynamic code solves an operational problem, not merely a design problem. Choose it only when editable destinations or campaign insights justify assigning an owner to the account, redirect, plan, and reporting record.

Validate the destination and test the finished code

A code can scan correctly and still fail its purpose if it opens the wrong page, a private file, or a page that does not work on a phone. Check the destination separately from the code image. If it points to a document, confirm the sharing permissions for the people expected to scan it.

Use HTTPS where appropriate, confirm that the destination resolves, load it on a mobile connection, and check that the intended audience does not encounter an unintended login. Leave a clear quiet zone of at least four QR modules around the code, as DENSO WAVE’s QR Code guidance recommends. There is no universal printed size that guarantees a successful scan. Distance, module size, print quality, contrast, surface, lighting, and camera all matter.

01Confirm the URLOpen the exact destination, check the path and parameters, and confirm that the asset owner approves it.
02Check audience accessLoad the page on a mobile connection and confirm that the intended audience can open it without an unintended login or private-file restriction.
03Inspect the final designCheck contrast, the four-module quiet zone, module clarity, and any logo or decorative treatment in the exported layout.
04Scan the finished assetTest the exported or printed version under ordinary conditions at the intended viewing distance. If it fails, correct the asset rather than relying on the generator preview.
05Record approvalSave the destination, asset filename or version, owner, test result, and verification time. For dynamic codes, also record the provider and current redirect.

Test the actual exported design or printed material, not only a preview on the generator screen. If the code will be used publicly, consider testing at the intended distance and under ordinary conditions such as glare, angled viewing, and varied lighting.

Automate QR-code creation only after the process is defined

Automation is useful when each form submission or new file needs its own code. The examples below show verified trigger-to-action patterns, not complete publishing systems. They do not by themselves establish URL validation, approval, storage, distribution, retries, or duplicate prevention.

Trigger Verified action Required validation Failure owner
Jotform New Submission QRTIGER Create Static QR Code Validate the mapped URL, required fields, source event ID, and duplicate policy before the QR action. The workflow owner corrects invalid submissions and investigates failed actions.
Google Drive New File in Folder ME-QR Create Link QR Code Confirm that the file link is accessible to the intended audience and remains valid. The file owner fixes sharing or link problems; the automation owner handles action errors.

For a production workflow, define the record grain before configuring actions. One QR asset record should represent one physical or digital asset version. A provider-reported scan observation is a different grain, and a campaign report is an aggregation with a stated period and scope. Do not use a campaign total as though it were an individual scan event.

The following is an illustrative operating record, not a schema guaranteed by the Zapier templates:

{
  "source_system": "jotform",
  "source_record_id": "illustrative-submission-1842",
  "source_event_id": "illustrative-event-1842-run-1",
  "destination_url_normalized": "https://example.com/attendee",
  "campaign_id": "event-2026",
  "placement_id": "registration-desk",
  "qr_mode": "static",
  "provider": "QRTIGER",
  "provider_code_id": "capture-if-returned",
  "asset_version": "1",
  "status": "awaiting_review",
  "owner": "event-marketing",
  "created_at": "2026-11-21T10:00:00Z",
  "last_verified_at": null
}

The key must match the declared row grain. If the rule is one asset per source event and version, a proposed uniqueness key could be source_system + source_event_id + asset_version. If the rule is one code per destination, campaign, and placement, use a different key such as destination_url_normalized + campaign_id + placement_id. Include a run or version identifier when multiple legitimate regenerations are allowed.

Zapier Tables can store records and trigger workflows from records, but the reviewed documentation does not establish database-enforced unique constraints or transactional upserts. A lookup followed by create can race when two runs process the same event. When duplicate creation would cause harm, use a datastore or database with a unique index and transactional upsert, or label the workflow best effort. Do not present a Zapier template as providing that guarantee.

Keep deterministic rules ahead of AI. URL syntax, allowed domains, required fields, file permissions, expiry, and duplicate handling should be validated by rules. AI is not needed to generate the QR code. If it drafts landing-page copy, validate the output and require human approval before publishing it or changing a live destination. Assign an owner for invalid URLs, inaccessible files, duplicate events, provider failures, and approval exceptions.

ConsultEvoZapier automation servicesRelevant when a QR workflow needs validation, ownership, exception handling, and stronger duplicate controls than a basic trigger-to-action template provides.

A practical pre-publication checklist

Publish only when these checks pass
  • The code is static or dynamic for a deliberate reason, and a dynamic code has an accountable owner.
  • The destination is correct, uses HTTPS where appropriate, works on a mobile connection, and is accessible to the intended audience.
  • The final asset has adequate contrast, a four-module quiet zone, and a successful scan from the exported or printed version.
  • The asset version, destination, owner, test result, and last verification time are recorded.
  • A dynamic code has documented provider, plan, code ID if available, current redirect, and continuity terms.
  • Automation has a source event key, a row-grain-specific uniqueness rule, and an owner for validation and failures.

Choose the code behavior, prepare the destination, generate the asset, and make the final scan test part of approval. For a dynamic code or automated workflow, also name the person responsible for keeping the redirect, destination, and operating record current.