Skip to main content
QRSenBuilt for business
Core Concepts

QR Code Resolution: What Actually Matters

Resolution for a QR code actually means two different things people mix up: the pixel dimensions of an exported image file, like a 2048 by 2048 pixel PNG, and the physical print resolution, measured in DPI, needed for a printer to render each module as a crisp edge rather than a blurred blob. A vector SVG export sidesteps the whole question since it has no fixed pixel count at all.

When a QR code is exported as a raster image like PNG or JPG, resolution refers to how many pixels wide and tall the file is. QRSen exports PNG at 2048 by 2048 pixels, described as HD, which gives enough pixel density to scale the image down for a website or up to a reasonably large print size without visible blurring or blockiness, since you're just displaying that fixed grid of pixels at whatever size you place it.

A separate concept applies once you're sending a QR code to a printer: DPI, dots per inch, describes how finely a printer lays down ink or toner at a given physical size. What matters for scannability isn't the DPI number on its own but whether each individual module in the QR grid ends up with a crisp, distinct edge at the final printed size, a module that prints as a fuzzy blur because the resolution was too low for how small the code was shrunk can cause modules to bleed into each other and break the scan.

The word 'resolution' gets used loosely to mean 'how sharp is this,' which covers both the pixel-count question and the print-quality question, but they're solved differently. A PNG with plenty of pixels can still print blurry if it's stretched far larger than its pixel count supports, and a code with a huge pixel count doesn't help at all if a printer's DPI settings or the print size itself are the actual bottleneck.

An SVG file describes the QR code as mathematical shapes rather than a fixed grid of pixels, so it has no resolution limit at all, it scales up or down to any size, a business card or a billboard, with perfectly crisp edges every time. For anything that might be resized, printed large, or sent to a professional printer, SVG removes resolution as a variable to worry about entirely, which is why it's generally the safer export choice for print production.

Frequently asked questions

For print, especially anything larger than a business card or anything going to a professional printer, SVG is the safer choice because it scales without any quality loss. PNG at a high pixel count like 2048 by 2048 works fine for most digital use and standard-size prints, JPG is best reserved for cases where a specific tool requires that format.
It depends more on how much data is encoded and how fine the resulting modules are than on a single fixed number, a code encoding a short URL can go smaller than one encoding a long vCard, since the latter has more, smaller modules packed into the same grid. When in doubt, test-scan a printed sample at the actual intended size before committing to a full print run.
No, pixel count only affects how sharp the image looks, not whether the underlying data or error correction level is sufficient. A high-resolution image of a poorly configured code, say one with too little error correction and a logo covering too much of the grid, will still fail to scan regardless of how many pixels it has.