Most QR code generators send your data to a server. Learn how client-side QR generation works, why it matters for privacy, and how to create QR codes that stay on your device.
QR codes are everywhere — on restaurant menus, business cards, product packaging, event tickets. Creating one seems simple: paste a URL into a generator, download the image. But most people never consider what happens to the data they paste. The URL, the contact information, the Wi-Fi password — where does it go?
The majority of QR code generators are server-based. When you paste a URL and click generate, your data is sent to the company's server. The server generates the QR image and sends it back. This means the service now has a record of every URL, every phone number, every piece of text you have ever encoded. Some services also create dynamic QR codes that route through their servers permanently, meaning they can track every scan.
A client-side QR generator runs entirely in your browser. The algorithm that converts text into a QR matrix is well-defined (ISO 18004) and can be implemented in JavaScript without any server dependency. Your data never leaves your device — it goes from the input field into the generation algorithm into a canvas element, and you download the result directly.
Open your browser's developer tools (F12), go to the Network tab, and generate a QR code. If you see a request sending your data to a server, the tool is server-based. If the only network activity is the initial page load, the generation is local. Better yet, disconnect from the internet after the page loads — a truly client-side tool will keep working perfectly offline.
SocialShrink's QR generator is built on the same privacy-first architecture as all our tools: 100% client-side, no server processing, no data collection. The QR encoding happens in your browser using a pure JavaScript implementation. The generated code is a static, standard QR — no redirect through our servers, no tracking, no expiration. Your data stays yours.