ChoosingaphonenumberQRcodegenerator

Static against dynamic — the only distinction that matters

A static code carries its payload in the pattern. Nothing sits between the scanner and the destination, the code works forever, and it cannot be edited after printing.

A dynamic code carries a short link belonging to the generator. The destination can be changed later and scans can be counted, which is genuinely useful — and it means the code depends on that company's redirect continuing to run, and on you continuing to pay for it.

Neither is better in the abstract. A menu that changes weekly wants a dynamic code. A Wi-Fi card, a business card or a payment sticker wants a static one, because permanence is the entire point.

Six questions worth asking of any of them

• Is the code static or dynamic? If the site will not say plainly, assume dynamic — it is the answer with a business model attached.
• Does it expire, or cap scans? A limit means it is a redirect, whatever the pricing page calls it.
• Does the free tier watermark the image or force a logo into the middle?
• Can I export SVG? Without it, anything printed larger than a postcard will show pixel edges.
• Where is my payload processed — my browser, or their server?
• If this company shuts down next year, does my printed code still work?

That last one catches more people than the rest combined, and it is only ever a problem in one direction. A static code outlives the site that made it. A dynamic code does not.

Where this phone number QR code generator sits

Static, browser-based and free. A tel: link — nothing more than the number, with no redirect in the middle, no account, no scan cap and no watermark. SVG and PNG both export at full resolution.

The finished code is decoded entirely on the phone, so it scans with no connection.

What it deliberately does not do is let you change the destination after printing. That requires storing the destination somewhere, which requires an account — the dynamic side of this product, kept separate so the free half can honestly promise permanence.

When to use something else

• A campaign where the destination genuinely changes — a seasonal menu, a rotating offer, a link you expect to move.
• Scan analytics: how many, where and when. A static code cannot report that, because nothing is watching it.
• Bulk generation of thousands of unique codes with per-code tracking, which is a data pipeline rather than a form.
• Printed packaging with a decade of shelf life, where you may want to retarget the code years later.

For everything else — a card, a poster, a window, a till, a badge, a Wi-Fi note by the door — a static code is the version that still works in five years.