Skip to content
YAS.SH
QR CODE GENERATOR

Free QR code generator — PNG & SVG

Generate a QR code for any URL in one click — no watermark. Choose 128–1024px, PNG or SVG. Pair with a yas.sh short link for a dynamic QR that tracks every scan.

Download 1024px PNG

Rendered server-side by GET /api/v1/qr — error-correction level M, cacheable for 1 hour. Open the preview to verify scanability before printing.

QR code for https://yas.sh
# via API curl "https://yas.sh/api/v1/qr?url=https%3A%2F%2Fexample.com&size=512&format=png" -o qr.png

WHAT TO USE IT FOR

Print & packaging

High-contrast QR at 1024px for flyers, boxes, and menus. SVG for crisp vector print.

Dynamic links

Generate a QR for a yas.sh short link — change the destination any time without reprinting.

Campaigns & events

Every scan lands in your click analytics with device, referrer, and bot filtering.

Dynamic QR in three steps

  1. 1. Shorten your destination URL in the dashboard — e.g. yas.sh/launch.
  2. 2. Generate a QR for that short link here (or via GET /api/v1/qr?url=…).
  3. 3. Update the destination in the dashboard any time — the printed QR keeps working.

Every scan of a dynamic QR is recorded in your analytics: total scans, device breakdown, referrers, and a daily series — bot traffic filtered automatically.

About QR code generation on YAS.SH

This page generates QR codes from a URL or text and renders them in your browser. A QR code is a matrix of modules with Reed–Solomon error correction, which is why a code that is partly obscured, printed on a curved surface or lightly damaged still scans. The trade-off is that stronger error correction produces a denser matrix, which needs to be printed larger.

Codes are generated locally, so the destination you encode is not transmitted or logged. That matters when the URL contains a campaign identifier, a customer reference or an unlisted page.

Getting a code that actually scans

  • Keep the quiet zone

    Four modules of clear space on every side. Codes cropped tight to the artwork edge fail to scan and there is no visible clue why.

  • Size for the distance

    As a rule of thumb the code should be about one tenth of the intended scanning distance — roughly 20 cm for a code read from two metres.

  • Shorten the destination

    Less data means fewer modules and a coarser, more forgiving matrix. Point the code at a short link you control so the destination can change without reprinting.

  • Choose correction deliberately

    Level M for screens and clean print; Q or H where the code may be scuffed, curved or partly covered by a logo.

Making scans measurable

A QR code on physical material is otherwise invisible to analytics. Encoding a URL with UTM parameters, or a short link that carries them, turns a poster or a package into an attributable channel. The UTM Builder on this site assembles the tagged URL, and the URL Tracking Cleaner strips those parameters again when you need the clean address.

Frequently asked questions

Do the codes expire or stop working?

No. A QR code is a static encoding of whatever you put in it — there is no service in the middle. If you encode a short link, the code keeps working as long as that link resolves, which is what makes short links the right target for printed material.

Is my URL sent to a server?

No. The matrix is computed in your browser, so the destination is not transmitted or stored.

Can I add a logo in the centre?

Yes, at error correction level H and covering no more than about 30% of the area. Test with several phones — the correction budget spent on the logo is no longer available for real-world damage.

Why does my printed code fail to scan?

Usually a missing quiet zone, print size too small for the scanning distance, low contrast, or too much data forcing a dense matrix. Shorten the payload and enlarge the code before changing anything else.

Ask YAS AI
🍪 Cookies & privacy. Essential cookies keep you signed in and remember language and theme. Google AdSense and reCAPTCHA are Google technologies: AdSense runs only after Accept All; reCAPTCHA loads on sign-in and contact forms. See how Google uses data: https://policies.google.com/technologies/partner-sites cookie policy · privacy policy.
Settings