High-Resolution QR Code Generator: Print Sizing, Formats and Export

A QR code that looks crisp on your monitor can come back from the printer as a soft gray smudge that no phone will read. The cause is almost always one of five things: a raster file exported too small, a quiet zone trimmed to fit the layout, a color choice with too little contrast, a code printed smaller than its scanning distance allows, or a surface the error correction level could not cope with. By the end of this guide you will know how to export the right file at the right size, what to tell the printer, and how to check the exact file before the run.

DPI versus vector

DPI, dots per inch, only applies to raster files such as PNG and JPEG. A raster file is a fixed grid of pixels; to print it at a given physical size, the printer spreads those pixels over the paper. At 300 DPI, the usual requirement for print, a code that will be 5 cm (about 2 inches) wide needs at least 600 pixels of image. A 200-pixel PNG stretched to 5 cm prints at 100 DPI, and the module edges blur into gray.

A vector file, SVG or PDF, has no pixels and no DPI. It describes each module as a shape, and the printer's own hardware draws it at whatever resolution it prints. The same SVG produces a sharp 2 cm code on a business card and a sharp 2 m code on a shop window. This is why "300 DPI" is a question about PNG, and the answer for anything that a print shop handles is usually to send vector instead.

Quick QR Maker exports PNG at 128, 256, 512 or 1024 pixels, and SVG and PDF at any size. For print, pick SVG or PDF unless the printer specifically asks for a raster file.

PNG vs SVG vs PDF

If the printer's spec sheet says "300 DPI PNG" and you cannot change their mind, export the 1024-pixel PNG and place it at no larger than 8.6 cm (3.4 inches). That keeps it at 300 DPI. Above that size, use vector.

Sizing from scan distance

The rule of thumb used across signage printing: the printed code should be at least one tenth of the distance it will be scanned from. Then add for density and for a logo.

Two things push the minimum up. A dense code, meaning a long URL, a vCard or a high error correction level, has smaller modules for the same width, and each module still has to be large enough for a phone camera to resolve. A logo raises the error correction level and eats the recovery margin, so add roughly 15%. The size calculator takes your actual content, distance, error correction level and logo and gives a minimum in millimeters and inches, along with the module count it is based on.

Shorter content is the cheapest fix. A URL under about 80 characters produces a visibly simpler code than a long tracking link, and simpler codes print smaller and scan from further away.

The quiet zone

The quiet zone is the blank margin around the code, in the background color, at least four modules wide on every side. It is part of the symbol as ISO/IEC 18004 defines it; the reader uses it to find where the code starts. This is the item most often lost in production, because a designer sees empty space and tightens the layout, or a border is drawn right up to the modules.

Four modules is a proportion, not a fixed distance. On a 25-module code printed at 5 cm, each module is 2 mm and the quiet zone is 8 mm. The exported file already includes it. Tell whoever places the code that the white margin is not negotiable, and check it on the proof with a ruler: measure one module, multiply by four, and confirm nothing else, including a frame, a fold or a die-cut edge, falls inside that band.

Color and contrast

Dark modules on a light background scan most reliably, with a contrast ratio of at least 4.5:1 between the two. Black on white gives 21:1 and is the safe default for anything that will be photocopied, faxed or read under poor light.

Brand colors work within limits. A dark navy, forest green or charcoal on white or cream passes. Mid-tones fail: orange, gold, sky blue and most pastels do not reach 4.5:1 against white. Do not invert the code, light on dark, without testing on several phones; some readers handle it, others do not. Gradients are fine when every stop clears 4.5:1, since the weakest part of the pattern decides whether it scans; the studio's curated ones do, and it grades any gradient by its palest end rather than an average. Mixing two tones by hand is the same bet without that check. On the smallest prints a flat colour is still the safer call, because a gradient spends margin you may want for ink spread and cheap stock.

Two print-specific points. First, ask for the modules in 100% black (K only), not a four-color rich black. Rich black is built from four inks and any misregistration between plates gives every module a colored fringe. Second, if the code sits on a colored background, give it a white plate that includes the full quiet zone, rather than printing directly on the color.

Error correction for print surfaces

Error correction lets a reader recover a portion of damaged modules: about 7% at level L, 15% at M, 25% at Q and 30% at H. Higher levels make the code denser, so pick the level for the surface, not the maximum.

• Paper indoors, business cards, menus, brochures: M. It survives ordinary handling and keeps the code small.
• Anything with a logo: H. A logo covers modules deliberately, and it needs the largest recovery margin.
• Outdoor signage, packaging, labels that get scuffed, anything laminated or under glass with reflections: Q or H.
• Direct printing on fabric, corrugated card, wood or any textured surface: H, and print larger than the calculator's minimum, because the texture breaks module edges.
• Screen-printed or engraved: H, and ask the printer for a sample at the intended size, since these processes have their own minimum line width.

Set the level in the generator before you export; it cannot be changed in the file afterwards. On this site the setting sits in the size and error correction section of the design studio.

Pre-press checklist

Run through this list on the final file, in this order, before it goes anywhere.

1. Content is correct. Open the destination in a browser from the exact URL in the code, and confirm it uses https://.
2. No shortener that you do not control is in the URL. A shortener that shuts down or changes its terms breaks every printed copy at once.
3. Error correction is M for plain paper, H for logos and rough surfaces.
4. Format is SVG or PDF for the print shop; PNG only at 1024 pixels and only when raster is required.
5. Printed width meets the minimum for the scanning distance from the calculator, plus the logo margin if there is one.
6. Quiet zone is intact, four modules on all sides, with nothing inside it.
7. Modules are dark on light, contrast 4.5:1 or better, K-only black if the job is CMYK.
8. No JPEG anywhere in the chain. If a designer re-saved the file, ask for the original.
9. The code has not been rotated, skewed or stretched to fit. A QR code must stay square.
10. A printed proof at actual size has been scanned with at least one iPhone and one Android phone from the intended distance.

Print the checklist and tick it. Every item on it corresponds to a job that has been reprinted.

Testing the exact exported file

Test the file that leaves your computer, not the preview inside the generator. The two are the same only if nothing has happened in between, and something usually has: a re-export, a resize, a paste into a layout, a conversion by the printer's upload portal.

Open the QR code tester and drop in the SVG, PDF or PNG you are about to send. It decodes the file and shows the exact content, flags plain HTTP links, warns when the destination is a shortened URL, and warns when the content is long enough to force a denser code that needs a larger print. If the tester cannot read the file, stop; a phone will not do better.

Then test on paper. Print the code at its final size on an ordinary office printer, or better, get one proof from the print shop. Scan it with an iPhone using the built-in camera and with an Android phone using its camera or Google Lens, from the intended distance, then from twice that distance, then at an angle, then under dim light. If it hesitates on either phone, enlarge it or simplify the content before approving the run.

For the printer's own proof, check three things with a ruler and a phone: the code's width matches the number you specified, the quiet zone measures at least four modules, and it scans at arm's length from the proof. If all three pass, approve the run.

FAQ

What resolution should a QR code be for print? 300 DPI if it is a PNG, which means at least 600 pixels for every 5 cm of printed width. If it is SVG or PDF, resolution does not apply; the file is sharp at any size.

Can I enlarge a small PNG for a poster? No. Enlarging a raster file spreads the same pixels over more paper and blurs the edges. Export a new file at 1024 pixels, or use SVG.

Is a bigger QR code always better? Bigger is safer up to the point where a phone has to be held far back to fit the whole code in frame. At normal sizes for the distance, there is no downside; a code much larger than the rule of thumb just wastes space.

Does the printed code expire? A static code from this site does not. It encodes the destination directly and works for as long as that destination exists. See QR codes that never expire for the difference from dynamic codes.

Can I print in a color other than black? Yes, if the color is dark enough to reach 4.5:1 against the background. Test the exact ink on a proof, since printed colors are often lighter than the screen version.

Export the file as SVG or PDF from /advanced-studio, get the size from the size calculator, and run the file through the QR code tester before you send it to the printer. The rest of the print rules are on QR codes for print.