Dynamic vs. static QR codes: what actually happens when someone scans

A static QR code encodes its payload directly in the pattern: a phone number, Wi-Fi credentials, a UPI payment string. The scanner's camera decodes it and the phone acts on it — no server involved. It works offline and it works forever. It also can never change, and you'll never know it was scanned.

A dynamic QR code encodes a short link instead — something like qrflow.app/s/eGBEF5H. When someone scans it, the link hits our scan service, which does four things in a few milliseconds: resolves which experience the code points to, checks your access rules (passcode, expiry, schedule, scan limit), records an anonymous scan event, and routes the scanner onward.

That indirection is the entire value. The printed pattern never changes, but everything behind it can: swap tonight's menu, fix a typo in your landing page URL, pause a campaign, or upgrade a simple link into a full hosted page — all after the stickers are on the tables.

It's also what makes analytics possible. Because every scan passes through the service, you get totals, unique visitors, trends, and device breakdowns without adding any tracking to your own site.

Our rule of thumb: choose static only when you specifically need offline behavior — Wi-Fi access in a basement, a serial number on a device. For everything else, dynamic is strictly more capable, and on QRFlow your dynamic codes keep resolving on every plan, forever. Printed codes are commitments, and we treat them that way.