Turn a link, a WiFi login or a contact card into a static QR code built in the browser. The pattern holds the content directly, so it works forever with no account, no redirect and no scan tracking.
Encoding tools by OnlinePCApps since 2013
A QR code printed on a thousand flyers is a promise. These are the ways that promise breaks after the ink dries.
A free dynamic code routes through a provider. When the trial ends, the plan lapses or the scan cap is hit, the redirect dies and every printed copy leads nowhere.
A dynamic code sends each scan through a server that records the time, the place and the device. That record belongs to the provider rather than to the person who made the code.
A WiFi password or a private link typed into a hosted generator is transmitted to a server to build the image. The secret has left the device before the code exists.
A link, plain text, a WiFi login or a contact card goes into the field. The right encoding mode is chosen from the characters, so no setup is needed.
A higher error correction level lets the code survive a scuff or a logo over the center. A larger size scans from further away.
PNG suits a screen or a document. SVG stays sharp at any print size, from a business card to a poster. The file is the code, owned outright.
A generator encodes content into a grid of modules. The value is in doing it as a static code the maker fully owns.
A link, plain text, a WiFi login, a vCard contact, an email, a phone number, an SMS, a map location or a calendar event all encode from the same field.
Levels L, M, Q and H recover from roughly seven, fifteen, twenty-five and thirty percent damage. Higher levels survive a logo or a scuff at the cost of a denser grid.
PNG gives a ready image for a screen or a document. SVG is vector, so the code holds its edges from a business card up to a banner.
The content is written into the pattern, not into an account. There is no redirect to keep paid for and no service that can switch the code off.
A QR code, a quick response code, a 2D barcode and a matrix barcode all name the same thing. This tool writes a static symbol, where the content lives in the code rather than behind a link that a provider controls.
Both make a scannable code. They differ in who owns it afterward and what it costs to keep alive.
| Point of comparison | This tool Static, in the browser Content baked into the code | Dynamic services Content behind a hosted redirect |
|---|---|---|
| Keeps working over time | Forever, no plan needed | Dies if the plan lapses |
| Scan activity | Nobody tracks it | Logged by the provider |
| Sign-up or watermark | Neither | Common on free tiers |
| Edit the destination after printing | Reprint to change it | Change it without reprinting |
| Scan counts and analytics | None recorded | Counts and locations |
The last two rows go to the dynamic services, and they are the real reason to pay for one. A code whose destination must change after it is printed, or whose scans must be counted, needs that hosted layer. For a code that only has to work and keep working, static wins on every other row.
Building a QR code is arithmetic that lays out modules from the characters given. The browser can do all of it, so a WiFi password or a private link is turned into a code without ever being sent to encode it.
A static code carries no redirect, so there is no server between a phone and the content. Nobody counts a scan, records a location or holds the power to switch the code off later.
A QR code is a defined structure, not a picture. Each part has a job the standard sets out.
| Part of the code | Detail | What it does |
|---|---|---|
| Modules | black and white cells | The square dots that make up the grid. A dark module is a one and a light module is a zero, and together they hold the data. |
| Versions | 1 to 40 | The size, from 21 by 21 modules at version 1 up to 177 by 177 at version 40, growing four modules a side each step. More data needs a higher version. |
| Error correction | L, M, Q, H | Four Reed-Solomon levels recovering about seven, fifteen, twenty-five and thirty percent of a damaged code. A higher level survives more wear. |
| Encoding modes | numeric to kanji | Numeric, alphanumeric, byte and kanji modes each pack their character set efficiently. Byte mode carries UTF-8 text, and the mode is picked from the content. |
| Finder patterns | three corners | The large square eyes in three corners let a scanner find the code and read it at any angle. |
| Alignment patterns | version 2 and up | Smaller squares that help a reader correct for a code that is curved or viewed at a slant. |
| Timing patterns | alternating line | A row and column of alternating cells that tell the scanner how large one module is. |
| Quiet zone | 4 modules, required | The clear margin around the code. Without at least four modules of space a scanner can fail to locate it. |
| Masking | applied automatically | A pattern laid over the data to balance dark and light, which keeps the code easy for a reader to lock onto. |
| Data capacity | up to ~7089 digits | At the largest version and lowest error correction a code holds about 7089 numeric or 4296 alphanumeric characters. A typical URL uses a small fraction of that. |
| Payload | static or dynamic | A static code stores the content itself. A dynamic code stores a redirect address whose target lives on a server. |
The Standards This Follows
A QR code is an international standard, which is why one made by any tool scans in any conformant reader. The documents below define the symbology.
The choice is not about design. It is about who holds the content once the code is out in the world.
For most needs a static code is the safer choice, because it belongs to the person who made it rather than to a service that can switch it off.
A code that scans on a screen can still fail on paper. These three catch most of it.
A code needs roughly a one inch side to scan from arm's length, and more for a poster read across a room. Print a test at the real size before the full run.
Keep a clear margin of at least four modules on every side, and keep the code dark on a light background. A busy border or a low contrast pairing stops a scan.
A logo over the center covers modules. Level H error correction recovers about thirty percent, which is what makes a centered logo safe to add.
The browser tool makes one code at a time. A list of asset tags, seat labels or product links is work for the desktop edition, which reads a spreadsheet and writes a code for every row in one pass.
Point it at a CSV and each row becomes its own code, named from a column so the files are easy to sort.
Every code is written as vector, ready for a print sheet at any size without a loss of sharpness.
A saved job regenerates a whole batch when the source list changes, without touching each code by hand.
Free, no sign-up and no tracking. The code is built on the device and stays yours to keep forever.