How to Create a QR Code (Step-by-Step Guide)

We support 50+ content types organized by what the QR opens on scan:

Web destinations: URL (the most common), PDF (links to a hosted PDF file), App Store (deep link to App Store / Play Store).

Contact and identity: vCard (business card data — name, phone, email, company), email (prefilled subject and body), phone (one-tap call), SMS (prefilled text message).

Network: WiFi (auto-join with SSID and password encoded), location (opens Maps with a pin).

Social and messaging: Instagram, YouTube, TikTok, Facebook, Twitter, LinkedIn, WhatsApp, Telegram, Snapchat, Discord, Pinterest, Spotify, Threads.

Commerce: Amazon, Etsy, Shopify product pages, Google Pay, Apple Pay, Venmo, PayPal payment links.

Reviews and feedback: Google Review (direct-to-review URL), TripAdvisor, Yelp, Google Form, Typeform.

Specialty: vCalendar (event with start time and location), Zoom meeting, Google Meet, Microsoft Teams.

Each type has a dedicated form built for that specific data structure. The form validates the input format — for a URL it requires a valid URL, for a vCard it formats the contact data per the vCard 3.0 spec, for WiFi it builds the standard WIFI:T:WPA;S:SSID;P:password;; payload.

Pick the type that matches the scanner's expected action. If you want the scan to open Instagram, use the Instagram type (not URL — the Instagram type triggers the app deep-link properly). If you want the scan to save the contact, use vCard. The type-specific handling delivers a better scan experience than a generic URL pointing at a landing page.

Fill in the form fields for your chosen type.

For URL codes: paste the destination URL. Always include https:// (the form prepends it if missing). For long URLs with UTM parameters, consider trimming the URL for static QRs — long URLs produce denser patterns that require larger physical print sizes. The fix is either shortening the URL or switching to a dynamic QR that encodes a short redirect URL.

For vCard codes: enter your name (first and last), phone (international format with country code), email, company, and title. Keep additional fields (website, social URLs, address) to one or two — bloating the vCard increases QR pattern density without adding contact value. See the best vCard QR generators for the field-priority guidance.

For WiFi codes: enter the SSID (network name), the password (use the actual password — the QR encodes it for the scanner to send to the join prompt), and the encryption type (WPA/WPA2 for most modern networks, WPA3 (SAE) for newer enterprise networks, none for open networks). Mark the Hidden network flag if your SSID is hidden. See the WiFi QR guide for the full format spec.

For email/phone/SMS codes: prefill the recipient and any default subject, body, or message. The scanner opens the relevant app with the fields populated.

For PDF codes: upload the PDF or paste a URL to a PDF you host. We host PDFs up to 10MB on the free tier; larger files require Pro ($10/mo, up to 50MB) or Max ($20/mo, unlimited).

The form validates input in real time, so format errors surface before you generate the QR.

Match the QR to your brand without breaking the scan.

Colors. Pick the dark module color and the background color. The safe palette: black, dark navy, deep teal, forest green, burgundy, or charcoal on white or cream — all of these pass the 4.5:1 WCAG contrast threshold and read as branded. Avoid pastels, trendy mid-grays, and any combination where the contrast drops below 4.5:1. See the QR color guide for the tested palette.

Logo embed. Upload your logo (PNG with transparent background is ideal, or SVG). The generator places it in the center of the QR at under 15% of code area and automatically bumps the error correction level to H (30% recovery) so the embedded logo doesn't break the scan. Larger logos punch out too much of the pattern for the scanner to reconstruct.

Dot patterns and corner styles. The default pattern (square dots, square finder patterns) scans most reliably. Stylized dots (rounded, dot-style, leaf-shaped) and decorative corner styles are available for branded use — they scan reliably on current phones and may fail intermittently on older devices. Test on the audience's median device before committing to a stylized pattern.

Error correction level. The default is M (15% recovery) for clean indoor use. Bump to Q (25%) for general print and H (30%) for embedded logos or outdoor deployment. See the error correction guide for the trade-off between data capacity and recovery margin.

Preview at scale. The preview shows the QR at design size. Mentally scale it to print size (3 cm for a business card, 5 cm for a brochure, 10 cm for a poster) and ask whether the brand color combination still reads clearly at that scale and lighting.

Export your QR as PNG, SVG, or PDF based on the deployment.

PNG (raster). Best for digital use — websites, social media, screen display, presentations. The generator exports PNG at high resolution (up to 4096 × 4096); for fixed-size print, PNG at 300 DPI is sufficient. PNG is included on the free tier.

SVG (vector). Best for print at variable sizes — business cards through billboards. SVG scales to any size without quality loss because the QR is described mathematically rather than as fixed pixels. Print brokers prefer SVG because it gives them full control over the print size and resolution. SVG export is included on Lite ($5/mo) and higher.

PDF (vector). Best for professional print workflows where the QR is embedded in a multi-page layout (brochure, packaging artwork, formal report). The QR ships as vector inside the PDF. PDF export is included on Lite ($5/mo) and higher.

File-naming convention. Name the file descriptively so you can find it later — companyname-vcard-qr.svg, restaurant-menu-qr-2026-q4.png. Default names like qr-code.png collide and create confusion.

Watermark policy. Our static QR exports are watermark-free at every tier including free. The QR pattern is yours — there's no vendor logo stamped on the corner or alongside the pattern. See the no-watermark QR generators guide for the broader landscape.

The single most overlooked step. A QR that looks fine in the design file can fail under deployment conditions for a dozen reasons (contrast at scale, dim lighting, older phones, print substrate, lamination glare). The test catches these before the print run.

The 5-minute verification:

1. Print a single proof at production size on the production substrate. For a final batch on coated 14pt cover stock, print the proof on coated 14pt cover stock — not the office printer.
2. Scan on at least three phones: one older device (iPhone 11-era or Android 10-era), one mid-range current device, one current flagship. The mix spans the realistic audience.
3. Scan under deployment lighting. If the QR will live on a restaurant table tent, scan under restaurant-dim overhead lighting. If it's a window vinyl for a retail storefront, scan from the sidewalk at the actual storefront. Office-lighting scans can pass when restaurant-lighting scans fail.
4. Scan from the actual distance. Business cards: 20 cm. Table tents: 40 cm. Posters: 1–2 m. Window vinyl: 1–3 m. Test from real distance, not the digital-zoom test.
5. Verify the destination loads correctly. Open the URL in the browser the scanner opens; confirm the page renders correctly on mobile, loads quickly, and supports the intended action (form submission, contact save, network join).
6. Test on a clean device. A phone that has already joined the network, saved the contact, or visited the URL may scan successfully even when the QR encodes bad data. Forget the network, delete the contact, clear the browser cache before testing.

For dynamic QRs at scale, also run the cancellation verification test before printing 50+ pieces. The verification protocol is described in the linked guide.

Once the QR passes the verification tests, deploy.

For static QRs: paste the QR image into your design file (or hand the SVG to a print broker), print, deploy. Static codes have no ongoing maintenance — they work forever with no subscription requirement.

For dynamic QRs: the QR is live the moment you generate it. The dashboard shows scan counts in real time once scans start coming in. Monitor the analytics for the first 7–14 days to confirm the QR is being scanned at the expected rate; surprisingly low scan counts often indicate a placement, sizing, or CTA-text problem worth investigating.

For multi-location or multi-campaign deployments: assign clear naming conventions in the dashboard so you can attribute scans to specific placements. Menu-Main-Location-1, Menu-Main-Location-2 is more useful than QR-1, QR-2.

For deployments that will outlive the current subscription: verify the vendor's cancellation policy. We keep dynamic codes redirecting indefinitely after cancellation; some vendors (Flowcode at 30 days, QR Code Generator immediately) deactivate. Verify in writing before the print commitment. See the verify codes survive cancellation guide.

Refresh and replacement. Printed QRs degrade physically over time — lamination wear, UV fading, print abrasion. Plan a replacement cycle: table tents 12–18 months, shelf tags 6–12 months, window vinyl 12–36 months (with exterior-grade lamination), packaging on the natural inventory cycle.

Patterns we see repeatedly:

Generating the QR without picking the right content type. A URL QR pointing at instagram.com/yourbrand triggers a browser open; an Instagram QR triggers the app deep-link. Different scanner experience. Pick the type that matches the destination action.

Customizing colors below the contrast threshold. Pastels and trendy mid-grays look great in the design file and fail on older phones in dim lighting. Stay above 4.5:1 contrast.

Skipping the pre-print test. A QR that looks fine on screen can fail when printed on the wrong substrate at the wrong size in the wrong lighting. Always print one proof, scan-test, and confirm before authorizing the batch.

Using PNG for variable-size print. A PNG exported at 1024 × 1024 pixels prints crisply at 5 cm but pixelates at 30 cm. For variable-size print, use SVG. For fixed-size print, PNG at 300 DPI is sufficient.

Picking dynamic when static is enough. A QR pointing at your homepage doesn't need dynamic editing or scan analytics — static is free and reliable. Reserve dynamic for cases where the destination URL changes or analytics drive a decision.

Picking static when dynamic is the right architecture. A restaurant menu QR pointing at restaurant.com/menu-january-2026 is brittle — the URL changes with the menu update and every printed table tent goes dead. Use dynamic for any URL that might change.

Forgetting the CTA label. A QR with no adjacent text label converts at half the rate of one labeled "Scan to view menu" or "Scan to join WiFi." The label clarifies intent.

Embedding logos at the wrong size or error correction level. Logos above 15% of code area or at error correction below H break the scan. Stay within the size cap and bump to H.