Processed locally
Your input stays in this browser.
An 'HD' QR code export means little on its own: a QR code generator's SVG output scales to any print size with no loss of sharpness, while a raster PNG needs enough pixels for its target size at a specific print resolution, typically 300 dots per inch for close-range packaging or as little as 72 to 150 dots per inch for a distant banner.
Why 'HD' is not a print specification
A request for an 'HD' QR code usually means the exported file looked blurry or pixelated once enlarged, and the actual fix is choosing the right export format and pixel count for the intended print size, not a vague higher-quality setting. The term 'HD' itself comes from video, where it describes a fixed pixel count relative to a screen; a QR export has no equivalent fixed target, because its correct pixel count depends entirely on the physical size it will be printed or displayed at, a variable video resolution never has to account for. This site's SVG label generator produces a vector file built from mathematical module coordinates rather than a fixed pixel grid, which is the more reliable answer whenever the final print size is unknown or likely to change, since a vector export has no native resolution to outgrow in the first place.
How raster resolution actually works for a QR code
A raster PNG export is a fixed grid of pixels, and its sharpness at a given print size depends entirely on how many of those pixels land within each printed inch, commonly expressed as dots per inch or DPI. A QR code intended for a small, close-range label, such as a 25 millimetre product sticker read from a few centimetres away, benefits from a higher DPI, commonly 300, because the small module size leaves little margin for pixel softness at the edges of each square. A QR code intended for a large banner viewed from several metres away can use a much lower DPI, often 72 to 150, because the individual modules are physically large enough that the same absolute pixel softness is imperceptible at that viewing distance. This site's guide to sizing a code for its scanning distance covers the module-size side of that same calculation; DPI and module size are two different numbers that both have to be checked, not one substituting for the other.
| Use case | Recommended export | Typical resolution |
|---|---|---|
| Close-range product label | SVG, or PNG at high DPI | around 300 DPI |
| Distant banner or signage | SVG, or PNG at lower DPI | 72 to 150 DPI |
| Unknown or multiple print sizes | SVG | not applicable |
Worked example: exporting the same code for two different jobs
A generator exports one QR code as a 600 by 600 pixel PNG. Printed at 2 inches square, that file provides 300 dots per inch, sharp enough for a close-range product label. The same 600 by 600 pixel file printed at 20 inches square provides only 30 dots per inch, and every module edge turns visibly blocky and soft, a resolution failure that has nothing to do with the QR encoding itself and everything to do with reusing a file sized for a small label at ten times the linear dimension. An SVG export of the identical code sidesteps this specific failure entirely, since its vector paths are recalculated at whatever size the final layout requests rather than being stretched from a fixed pixel count.
When SVG is the better default, and when it is not
SVG is the safer default whenever the final print size is not yet fixed, when the same code needs to appear at several different sizes across different materials, or when a design tool needs to recolour or otherwise edit the code's paths directly. A raster PNG remains the more practical choice when a system specifically requires a bitmap format, such as many e-commerce platforms and print-on-demand services that do not accept vector uploads, or when the code is being composited directly into a raster photo or template inside an image editor that works in pixels rather than paths. Export both from the generator when the final destination format is uncertain, and keep the SVG as the durable source file regardless of which format ships.
Why a screen preview looking sharp does not guarantee a good print
A screen displays at a fixed, relatively low pixel density compared with most print processes, commonly around 96 to 110 pixels per inch, so a raster file that looks perfectly crisp on a laptop screen can still be well under the pixel count a 300 DPI print job needs at the same physical size. This site's guide to checking a QR code before printing covers testing the actual exported file at its real intended dimensions rather than trusting an on-screen preview, and that check matters more, not less, for a raster export specifically chosen for a demanding, small, close-range print where resolution shortfalls show up first.
Mistakes that produce a soft or blocky printed code
Scaling up a small raster export inside a layout application, rather than re-exporting at the target size from the generator, is the single most common cause of a blurry printed QR code, since enlarging existing pixels cannot recover detail that was never captured. A second mistake is exporting at a generic default resolution without checking it against the specific print size and viewing distance the job actually needs, treating every job as identical when a packaging label and a trade-show banner have very different requirements. A third is applying image compression, such as a low-quality JPEG export, to a QR code file at all; a QR symbol needs sharp, high-contrast edges between modules, and lossy compression artifacts at those edges are exactly the kind of degradation that can push a marginal symbol below a decodable contrast threshold. A fourth, easy to overlook, is exporting at the correct pixel count but then letting a page-layout application's own automatic image compression, applied when the final document is saved or exported to PDF, recompress the embedded raster a second time without anyone reviewing the result.
Vector formats beyond SVG: PDF and EPS for a print shop
A professional print shop or packaging supplier sometimes asks for a QR code as a PDF or EPS file specifically, rather than SVG, because those formats fit directly into an established prepress workflow built around page-layout and industrial printing software. Converting an exported SVG into a PDF or EPS through a vector-editing application preserves the same scalable, resolution-independent paths, so the conversion itself does not reintroduce the pixel-density problem a raster export has; the choice between SVG, PDF, and EPS at that point is mainly about which format the receiving printer's own software accepts, not about print quality.
Confirm the export before it goes to production
ISO/IEC 18004 specifies the module structure a decoder expects, but it says nothing about pixel density, print resolution, or file format, all of which are production decisions layered on top of a correctly encoded symbol. Export at the actual target size, whether as SVG for scalability or PNG at a resolution matched to the print process, then run the exported file through this site's decode tool and, for anything physically printed, a real printed proof rather than a screen check alone, before treating the file as finished. ISO/IEC 18004:2024 QR Code specification is the named source for the current external rule or product behaviour.