QR Code Generator

Generate QR codes for websites, Wi-Fi networks, text, email, phone numbers, SMS messages, contacts, events, and locations.

Encoded value


        

Appearance

How to use this QR code generator

  1. Choose the QR code type, such as website URL, Wi-Fi, contact card, event, or location.
  2. Fill in the fields for the selected type and review the encoded value.
  3. Adjust size, padding, foreground color, and background color.
  4. Download the QR code as a PNG for images or SVG for scalable print and design work.

QR Code Generator features

  • Generate QR codes for website URLs.
  • Generate QR codes for Wi-Fi credentials.
  • Generate QR codes for contact cards.
  • Generate QR codes for calendar events and locations.
  • Preview the encoded value before downloading.
  • Adjust QR size and padding.
  • Customize foreground and background colors.
  • Download QR codes as PNG images.
  • Download QR codes as scalable SVG files for print and design work.

What you can encode in a QR code

Use this QR code generator to make scannable codes for websites, Wi-Fi networks, plain text, email, phone numbers, SMS messages, contacts, calendar events, and map locations. QR codes are useful for print materials, signs, packaging, menus, handouts, events, and quick mobile actions.

How QR codes are generated

The tool formats your fields into the appropriate QR payload, generates the code in the browser, and renders downloadable PNG and SVG outputs. Larger payloads need more QR modules, so shorter URLs and simpler text usually produce cleaner, easier-to-scan codes.

QR code generator FAQ

Are QR codes generated on the server?
No. The QR code preview and downloads are generated in your browser.
Should I download PNG or SVG?
Use PNG for quick image sharing and SVG when you need a scalable file for print, design, or layout software.
Why should I leave padding around a QR code?
Padding creates a quiet zone around the code. Scanners use that clear space to detect the QR code reliably.

Test the QR code in the place people will scan it

Start with the shortest dependable payload. A short HTTPS URL usually creates a less dense symbol than a long tracked URL, which can improve scan tolerance at a given print size. Do not remove information required by Wi-Fi, contact, event, email, or payment formats. When using a redirect, make sure the redirect will remain under your control.

Choose error correction for the real environment. More correction can recover from some damage, but it also increases symbol density. A clean indoor handout and an outdoor label have different needs. Error correction does not make an unreadably small, low-contrast, stretched, or heavily covered code reliable.

Preserve the quiet zone around the code. Do not crowd it with text, borders, folds, trim lines, or another code. Keep modules square and use strong contrast. A dark foreground on a light background is the safest starting point; unusual color combinations and transparent backgrounds need testing on the final material.

Print at the final physical size and scan from the distance and angle a user will face. Test several current iOS and Android devices, not only the phone that created it. Check glossy surfaces, dim light, curved packaging, display glare, camera focus, and any lamination. A code that works from a desktop preview may fail after printing.

Make the destination understandable without scanning. Add a short label and, for important actions, a readable URL or another way to proceed. This helps people who cannot use a camera, have disabled scanning, or are reading a copied document. Do not make a QR code the only route to safety, payment, consent, or essential instructions.

Treat encoded data as visible. Anyone nearby can scan a printed code, and a URL can be logged or shared. Do not embed passwords, private tokens, personal records, or credentials. For Wi-Fi access, consider a guest network and rotate credentials when the printed code is no longer controlled.

Inspect the decoded result before distribution. A convincing label can hide a mistyped or malicious URL, so use HTTPS, check the domain character by character, and avoid untrusted shorteners. Keep the source payload and a sample print with the campaign record. For measured campaigns, build the destination first with the UTM builder, then generate and test the exact final code.

If a code will remain in public for years, plan for destination maintenance. Prefer a stable URL you can redirect over a vendor link that may expire. Monitor the page, certificate, and redirect, and replace damaged signage promptly. The generated image is only one part of a reliable scanning path.

Pre-publish checklist

  • Decode the final symbol and compare every character with the approved URL, Wi-Fi setting, contact, event, email, phone, or location payload.
  • Use a stable HTTPS destination under organizational control and inspect the domain carefully before printing or publishing.
  • Remove credentials, private tokens, personal records, and any value that should not be visible to every person who can photograph the code.
  • Preserve a clear quiet zone, square modules, strong contrast, and enough physical size for the expected scanning distance.
  • Print at final dimensions and test folds, trim, lamination, gloss, curvature, low light, screen glare, and ordinary camera focus.
  • Scan with several current iOS and Android devices and check the entire redirect and consent path, not only initial recognition.
  • Provide a human-readable label and an accessible alternative route when the action is important or required.
  • Save the source payload, generated asset, print proof, owner, destination-monitoring plan, and replacement date.
  • Retest the public destination and certificate over the life of signage; a readable symbol can still lead to a broken or expired page.
  • Place several printed codes far enough apart that a camera can select the intended one without ambiguity.
  • Check that nearby text, decorative squares, crop marks, and background patterns do not enter the required clear area.
  • For events or contacts, verify time zone, dates, telephone country code, address, and character encoding on a second device.
  • Retain a replacement plan for compromised Wi-Fi credentials, changed phone numbers, expired events, and destinations that must move.
  • Export at sufficient resolution for the production method and never stretch the raster code unevenly after generation.
  • Ask a person unfamiliar with the project to scan the proof and describe the destination before approving mass production.

Built and maintained by utilkit. Updated . Found an issue? Send corrections to contact@utilkit.com