Frequently Asked Questions

Yes. The QR code and barcode generator runs entirely in your browser. Your URLs, text, logos, and settings are never sent to any server. The code is generated locally and stays on your device.

No. When you use makeqrco.de/<url>, the server reads the URL from the path, generates a PNG image, and returns it. No logging of the URL, no storage, no analytics on what was requested.

No cookies are set. There is no analytics, no tracking pixels, and no user database. The site functions without any persistent state.

Yes. In the QR Code tab, use the logo upload option. The logo is drawn centered on the code with a white padding border. Use error correction level H for the best results — it allows up to 30% of the code to be obscured and still scan correctly.

L (7% recovery), M (15%), Q (25%), H (30%). Higher levels mean more redundancy — the code can be partially damaged or covered and still scan. H is recommended when adding a logo. L and M produce smaller/denser codes.

Yes. The generator supports custom foreground and background colors. Ensure there is sufficient contrast between them — low contrast QR codes may fail to scan on some readers.

PNG (from canvas) and SVG. The SVG download is a vector file, ideal for print. Note: the SVG does not include logo overlays — those are canvas-composited into the PNG only.

Code 128, Code 39, EAN-13, EAN-8, UPC-A, UPC-E, QR Code, Data Matrix, PDF417, Aztec Code, ITF-14, and Interleaved 2 of 5. Powered by bwip-js which supports 100+ symbologies.

You can upload an SVG silhouette (a horse, a logo, a country outline, etc.) and the barcode will be rendered clipped to that shape. The barcode modules only appear where the SVG shape is opaque.

No. Clipping barcode modules into an arbitrary shape destroys the data encoding. This is a purely decorative feature for artwork, merchandise, or marketing materials. Do not use it where the barcode needs to actually scan.

Different barcode types have strict data requirements. EAN-13 needs exactly 12 or 13 digits. UPC-A needs 11 or 12 digits. Code 128 accepts any ASCII. If you see an error, check that your data matches the selected type's requirements.

Simply prepend https://makeqrco.de/ to any full URL. For example: https://makeqrco.de/https://example.com — this returns a 512×512 PNG QR code image directly.

Yes. <img src="https://makeqrco.de/https://example.com" alt="QR code" /> will render the QR code inline. It works in HTML emails, web pages, Notion, GitHub markdown, and anywhere img tags are supported.

Not via the URL — the catch-all always returns a plain black-on-white 512×512 QR code. For custom options, use the generator on the main page and download the result.

Yes. Responses include Cache-Control: public, max-age=86400, so CDNs and browsers cache the image for 24 hours. Subsequent requests for the same URL return the cached image instantly.

UTM parameters are URL query strings (utm_source, utm_medium, utm_campaign, utm_content, utm_term) used to track the source of traffic in Google Analytics and other analytics tools.

Click "UTM / Analytics parameters" in the QR Code tab to expand the accordion. Fill in the fields you need — they are automatically appended to your URL before encoding. Only non-empty fields are added.

Conventionally: utm_medium=qr or utm_medium=offline. This tells your analytics platform that the click came from a physical QR code scan, as opposed to a link click on a web page.