QR Code Generator for Links & Profiles

A QR code is a URL rendered as a grid of black and white squares that a phone camera can read from across a table. It solves one narrow problem well: getting a link from a physical surface - packaging, signage, a business card, a slide - into someone’s browser without them typing it.

This generator encodes whatever text or URL you enter into a 512-pixel PNG with colours you choose, rendered in the browser and downloadable immediately. The encoding is fixed and standards-compliant; the parts you control are the payload and the two colours.

Contrast is the whole game. Camera software finds a code by locating three high-contrast squares in the corners and then reading the grid between them. Dark foreground on a light background is what every scanner expects; inverting it - light modules on dark - fails on a meaningful share of readers even though the data is technically intact.

Pastel-on-white is the most common self-inflicted failure. A soft mint code on a white card looks pleasant in a design file and gives the camera almost nothing to threshold against, particularly under warm indoor lighting or on a phone two generations old. If you are colouring the code for brand reasons, pick the darkest version of the brand colour available.

The quiet zone - the blank margin around the grid - is part of the specification, not decoration. This generator includes a margin of two modules by default. Cropping it away in a layout tool, or butting the code against a photo or a coloured block, removes the boundary the scanner uses to find the pattern.

A printed code is permanent in a way a web link is not. Whatever URL you encode is what those cards, labels, or posters will point at for as long as they exist, and there is no editing them afterwards. Encoding a campaign landing page that will be retired in six months creates a stack of printed material pointing at a 404.

The way around this is indirection: encode a URL you control and can redirect, such as a short path on your own domain, then repoint that path whenever the destination changes. The code stays valid indefinitely and you keep the ability to change where it lands.

Adding UTM parameters to the encoded URL is worth doing for anything printed, since offline-to-online traffic is otherwise invisible in analytics. Build the tagged URL first, then encode it - a longer payload makes the grid denser, which is a reason to keep campaign names short rather than a reason to skip tagging.

The text you enter is encoded to a QR symbol and rendered to a 512-pixel-square PNG data URL, with a two-module quiet zone and your chosen foreground and background colours. The output regenerates on every keystroke and colour change, so what you see is always the current payload.

Error correction is set to level M, which reserves roughly 15% of the code’s capacity for redundancy. That is the standard general-purpose choice: it tolerates a scuff, a fold, or a printing defect while keeping the grid comparatively coarse and easy to read. Higher levels survive more damage but pack more modules into the same square, which makes each module smaller and can hurt scanning at small print sizes.

Payload length drives density directly. A short domain produces a sparse, forgiving grid; a long URL with several tracking parameters produces a dense one where every module is smaller at the same physical size. If a code looks visually busy, shortening the URL is more effective than enlarging the print.