QR Code DPI: What Resolution Do You Need for Print?
For printed QR codes, 300 DPI is the standard safe target, the same baseline used across most professional print production, and it applies to the printer's output resolution rather than being something you set on the QR code file itself if you're starting from a vector (SVG) source. Starting from SVG sidesteps the DPI question almost entirely, since vector artwork has no fixed resolution to run out of.
DPI (dots per inch) describes how many printer dots fit into each inch of physical output — higher DPI means finer detail the printer can reproduce. For raster QR images (PNG or JPG), DPI matters because those files have a fixed pixel count, and stretching a low-resolution raster to a larger print size spreads the same pixels over more physical area, which is exactly the upscale-blur problem that causes many print scan failures. A 2048×2048px PNG printed at business-card size has enormous effective DPI headroom; the same file printed at billboard size does not.
Vector files (SVG) don't have this problem at all, because they describe the QR pattern as mathematical paths rather than a fixed pixel grid — a vector QR code prints at 300 DPI, 1200 DPI, or any resolution the print process supports, with identical sharp edges every time, since the file is being redrawn fresh at whatever size and resolution the output requires rather than being stretched. This is the core reason SVG is the recommended default for anything print-bound: it removes DPI as a variable to think about entirely.
If a raster file is unavoidable (a printer's software only accepts PNG or JPG, for example), the practical fix is exporting at a pixel dimension that comfortably covers the intended print size at 300 DPI — for a 2-inch code, that's roughly 600×600px minimum, and QRSen's default 2048×2048px HD export covers print sizes up to roughly 6-7 inches square at 300 DPI with room to spare, well beyond most everyday printed placements like labels, cards, and flyers.
The one scenario where even 300 DPI raster planning doesn't fully solve the problem is very large-format printing — billboards, building wraps, banners — where the physical size is measured in feet, not inches, and no reasonably-sized raster export covers that without visible upscaling. That's specifically where starting from a vector master file stops being a nice-to-have and becomes the only reliable option.
None of this changes based on which color the code uses, either — DPI and print resolution are entirely separate from the contrast and color considerations covered elsewhere; a code can clear every resolution requirement perfectly and still fail to scan if the color contrast itself is too weak, and vice versa. Treat resolution and contrast as two independent checklist items to confirm before a print run, not a single combined concern.