Branded QR Code Generator Guide: Create, Test, and Print

The proof is on your desk, the client wants a logo in the middle of the square, and the printer is waiting on a file. A branded QR code generator is the right tool only when that square encodes the finished share URL and still scans from the actual table, wall, or badge.

Finish the link before you touch the artwork. Upload the PDF or set the destination, choose the link name, set any access rules, and only then design the code. With a dynamic code you can swap the PDF or change where a link points after printing, but the link name baked into the pattern can't be edited out once the ink is dry.

The destination has to be the one you meant, and the printed proof has to scan. Those two checks decide the job.

Create a Branded QR Code in Six Steps

A branded QR code is made by encoding the final share URL in a generator, customizing the design, and exporting the image.

The link comes first because a code built from a preview address or a half-finished slug can't be corrected after the paper is printed. ISO/IEC 18004 defines the encoding methods, symbol formats, dimensions, error-correction rules, reference decoding algorithm, and production-quality requirements a normal reader expects. A branded generator should give you a standard QR symbol. If it switches to another pattern, phones and print workflows that follow the specification will fail.

Brochures, sales sheets, and PDF menus go through PDF to Link or the PDF tab of the QR Code Generator, and the project's QR card designs the code for that share link. For a page on your own website, paste its address into the generator instead. A code can't point at an existing LinkShip share link. Audio and image projects get a plain, unbranded QR code on their project page instead, and scans of it count as ordinary visits. Finish any custom link name before you export. The PDF or the destination can change after printing because the printed link stays the same. Rename the link and every menu, sales sheet, and event program has to be reprinted.

Finish the link, then the artwork

1. Upload the PDF and lock the link settings. Use PDF to Link or the generator's PDF tab, and complete the name plus any access choices you need. The code can only open what that link already does.
2. Set a password or expiry now if the page needs one. Do this before the artwork exists, so the printed code opens the page you intend rather than a wide-open draft.
3. Open the final share URL. Check it from the project page in a private window, so you see what a stranger will see.
4. Design the code on the project's QR card. It encodes that share URL for you, so nothing is retyped. That is what ties the print to the file.
5. Set the brand color, and add a logo only if it stays small. Check the live preview. If the finder squares lose clear corners, remove the logo.
6. Scan the preview with your own phone before you export. A preview your camera reads catches a bad URL immediately. It still isn't a printed proof.

Practical rule: Export only after the phone reads the final URL, not a staging link you meant to swap later.

If the code will sit on packaging or a counter card, send the tested file to a cutter such as Custom Sticker Shop QR decals instead of photographing a screen. A photo of the preview softens the module edges scanners need.

Before you approve a print quantity, open the generator page and confirm which save and download actions the current plan includes. Don't assume every account can download the same file.

Pick Error Correction and Colors That Hold Up

DENSO WAVE specifies four error-correction levels: Level L restores approximately 7% of codewords, Level M about 15%, Level Q about 25%, and Level H about 30%. DENSO WAVE identifies Level M as the most frequently selected level. The LinkShip generator picks the level for you: Level M for a plain code and Level H once you add a logo, so the covered center can still be recovered.

Higher correction lets a code still decode when part of it is smudged, scuffed, or covered. The cost is density. More recovery data makes the symbol larger and harder to print small, which is one more reason to add a logo only when it earns its place. A long destination, plus tracking parameters, adds to that load, so keep the encoded link short.

Color, contrast, and the center mark

Dark modules on a light background scan most reliably. Inverted light-on-dark codes fail on many older readers. Pale brand tints and gradients wash out the difference the camera needs. A transparent export still needs a light field behind it once it hits paper, which is the point of a transparent-background QR code.

Keep a logo small, about a quarter of the code at most, and park it in the center. Don't cover the finder squares in the corners. Accepting the upload isn't proof it will scan at the final size and viewing distance.

Say a restaurant menu stays on a clean table. A small logo is fine. An outdoor event banner that gets handled, rained on, or partly covered is better off as a plain dark-on-light code, printed larger. Keep brand styling only when the scan still passes in the final size and color.

Size the Printed Code for Its Viewing Distance

A module is the smallest square in the code. Printed size is that module multiplied by the number of modules on a side. Say you're laying out a Version 2 symbol, 25 modules per side. At 0.5 mm per module it prints 12.5 mm square. That's a postage-stamp target, fine for a phone held close, useless on a wall.

A peer-reviewed print-quality study reports that mobile scanning at close range generally benefits from modules of about 0.4–0.5 mm, while longer-distance scanning calls for approximately 0.5–1 mm modules. The same study puts about 0.36 mm as a practical lower bound for small packages or labels, and says larger media should use modules above 1 mm when people scan from farther away. Below that lower bound, ink merges and edges go soft.

A 2048-pixel export doesn't guarantee a readable print. The file can be sharp while the press blurs modules that are too small on the sheet. Ask the printer for a physical proof at actual size, then scan it from a table, wall, or stage distance.

A restaurant table tent is an arm's-length scan, so the close-range module size is the one to prove. A conference poster read from several meters away needs much larger modules, or the code is decoration. The same sizing problem shows up on a badge. If you're also ordering custom lanyards, the code on the badge still has to be large enough for a phone held at chest height, not shrunk to fit a logo lockup.

For a sales sheet, pair this measurement with how you create a QR code for a PDF, then size the print from the scanning distance and the press, not from a default pixel count.

Test the Code and Confirm the Link Before Printing

The generator preview isn't the release test. The code has to be scanned as a printed proof on the material it will be used on.

Preflight on the sheet

Marketing guidance on QR codes points to a quiet zone of at least four modules, strong contrast, a logo covering no more than roughly 20–25% of the code, and a test on both iPhone and Android. Gloss, a curve, low light, and small print on a busy background are where branded files die.

• Quiet zone: Leave a blank margin of at least four modules. A border, a photo, or a dark table edge that touches the code will break the read.
• Contrast and glare: Dark modules, light ground, matte stock. Glossy laminates throw the camera off in a bright room.
• Logo and shape: If the mark crowds the pattern, or the label wraps a bottle, drop the styling.
• Who is scanning: If an older phone, someone with low vision, or a person across the room can't get the same result, ship a plain high-contrast code.

Scan the physical proof on one iPhone and one Android phone, from several distances and angles, in bright light and dim light.

Confirm the page, then release

The scan should open a fast mobile page. Check that the title matches the file, and that any password, expiry, or view limit behaves as you set it. Our sharing workflow is upload, customize the link with name, password, expiry, and view-limit settings, share, then track visits and downloads. Saving QR designs and downloading QR codes are paid features for Tiny, Solo, Pro, and Pro Max. Don't promise those downloads on a free account.

Add a visible line such as "Scan to open the sales sheet," plus a short fallback URL beside the code. Write down which link and which file version the square points to. QR code analytics are easier to trust later if that note exists before the run.

Don't print or publish until the final share URL, the printed proof, and the mobile scan have all passed.

Scan Failures and How to Fix Them

Wrong page, unexpected password

An unexpected page means the square encoded the wrong address, or an old one. The printed code has to carry the final share URL. If the PDF changes later, replace it on the project page, a paid feature, and the same share URL stays live. Change the link name, though, and every printed code has to be reprinted. Promising a swap without knowing which one you need is how a stack of menus goes in the bin.

A password prompt means protection is already on the sharing link. Password and expiry apply to that link, not as a lock inside the file itself. Set them, and test them, before the proof is approved. Finding the prompt on delivery day means the card in someone's hand doesn't match the page you described.

Work the fixes in this order.

1. Size first. Most distance failures are modules that are too small.
2. Contrast next. Matte stock and dark-on-light beat another pass at the logo.
3. Logo after that. Shrink it or drop it before you blame anything else.
4. Destination last. Re-check the live URL before you export again.

Protect Trust When Your Logo Is on the Code

A logo on a QR code can reassure someone enough to scan. It cannot confirm that the destination is safe. Print the destination domain and a clear description of what the code opens, so readers can check before scanning.

What to print beside the code

• A human-readable label: Say what will open, such as “Scan for the 2026 spec sheet.” Give people a reason to scan.
• The destination domain: Print it beside the code so readers can compare it with the address they expect. A memorable LinkShip address can be easier to recognize than an unfamiliar string.
• A change log: Record who created the code, its destination, and when that destination was last changed.

Keep a record of the final share URL associated with each printed code. If your analytics distinguish QR scans from ordinary link clicks, review the two separately to understand which channel brought visits.

A changeable destination can keep a printed code useful when the linked file is updated. That flexibility also means the destination needs oversight. Limit who can edit the link, review changes, and confirm that the share URL will remain stable for as long as the print run is in circulation.

Password protection controls access to a sharing link. It does not encrypt the file or recall copies someone has already downloaded. Make sure the people receiving the code can access the link under the settings you chose.

The same check applies to branded packaging and drinkware. Nothing's guide to custom logo cups offers a look at branded cups. Print the destination domain and the action beside the code, then verify the final share URL before approving the proof.

LinkShip turns a PDF into a browser link with a print-ready QR code of its own. Upload the file, check its share URL, then design the code on the project's QR card. Start with PDF to Link, or open the QR Code Generator to upload a PDF or point a code at a page you host.