Vector vs raster
SVG keeps module geometry as vectors, so you can scale in layout software without inventing blurry pixels—useful for posters, packaging dies, and any job where size may change late.
PNG is a raster snapshot at a fixed pixel grid. It is convenient for many printers and proofs, but the pixel count must match physical size × DPI or modules softens when scaled up.
| Format | Best when | Watch for |
|---|---|---|
| SVG | You need scalable module edges in a design tool or large-format workflow | Downstream software that rasterizes poorly or flattens transparencies |
| PNG | You know the final physical size and can export at target DPI | Upscaling a small PNG; QRburst blocks extremely large edge sizes for safety |
| You want a page with the QR at an exact physical size for handoff | QRburst PDF currently embeds a high-res rendered QR—not a pure vector module PDF |
DPI and physical size
DPI tells a raster how many pixels land in each inch of paper. For QR, the goal is enough pixels per module that printing and camera capture do not smear neighboring squares together.
QRburst defaults Print Studio DPI to 300 for most hand-held pieces and uses lower DPI on large storefront/poster presets where modules are already physically large. 96 DPI is labeled as screen-oriented, not commercial print.
pixels ≈ inches × DPI
pixels ≈ (mm / 25.4) × DPI
PDF in QRburst today
QRburst builds print PDFs locally with pdf-lib. The page (A4 or Letter) places the QR at the configured physical size in PDF points so printers and collaborators see true dimensions.
Important product detail for 2026: the QR artwork inside that PDF is a high-resolution rendered image of your styled code, not a vector-only module construction. Gradients and logos are preserved; edges remain sharp when the embedded raster is dense enough for the box size. If your production pipeline requires editable vector modules exclusively, export SVG and place it in your layout tool.
Materials and finish
Substrate and finish change effective contrast and glare more often than creators expect. Dark kraft stock, metallic ink, heavy varnish, and window clings can all reduce decoder confidence even when the digital file is clean.
- Prefer matte finishes over high-gloss when scanners will work under spotlights
- Avoid placing codes where folds, staples, or die-cuts invade the quiet zone
- On transparent materials, give the code an opaque light backing so modules stay dark-on-light
- Curved packaging shrinks modules toward the edges—bias larger and re-test on the real object
Proof and physical testing
Before a production run, print a single proof at final size on representative stock. Scan with more than one phone, at the intended distance, under similar lighting.
Browser tools in QRburst (configuration analysis and simulated decode stress tests) reduce risk earlier in the design cycle, but they are not a substitute for physical proof. Treat them as layered evidence, not a merged certainty score.
- Confirm the decoded payload matches what you intended
- Open HTTPS destinations and verify the live page
- Re-check after any vendor resize, color conversion, or “optimize for web” compression