Text to QR: When Plain Text Beats a Link

Almost every QR code you meet is a link. Scan it, a browser opens, a page loads.

A code can also just hold words. Scan it and the text appears on the screen — no browser, no page, no connection. For a surprising number of jobs that is the better answer, and almost nobody uses it.

What a text code is

The words are inside the pattern. There is no address, nothing to fetch, nothing in between. The phone reads the code and shows you what it says.

Which means three things follow immediately: it works with no internet, it works forever, and nobody can change what it says — including you.

Where it is the right choice

• Equipment and asset labels. Serial number, model, install date, service interval. A maintenance engineer in a basement with no signal still reads it.
• Stock and inventory. A code holding the item reference goes straight into whatever system you scan it with, without a round trip to a server.
• Short instructions. Shutdown steps, a dosage, a safety note. The information is the point, and a web page would be a slower way to deliver two sentences.
• Anything that must outlive the company that printed it. A plaque, an exhibit label, a time capsule. A link depends on a domain and a host still existing. Text depends on nothing.
• Wi-Fi details in a place with no Wi-Fi yet. A chicken-and-egg problem a link cannot solve.

Where you actually wanted a link

Text codes have a real cost: the information is frozen the moment it is printed.

• Anything with a price in it. Prices change and the label does not.
• Anything you want to measure. There is no request to count, so there is nothing to track. A text code cannot tell you it was scanned.
• Anything longer than a short paragraph. Read the next section.
• Anything that will need correcting. A typo in a text code is a reprint.

If any of those apply, you want a link, and probably a changeable one — dynamic versus static codes covers that decision properly.

Length is the real limit

The constraint is not a word count. It is that everything has to fit in the pattern, so the more you put in, the finer the grid of squares becomes.

A code holding a serial number has large, chunky squares that scan from across a room. The same code holding three paragraphs has tiny squares, and tiny squares need to be printed larger, lit better and held closer. Past a point it stops scanning reliably at any sensible size.

• Keep it to what fits on a label. A line or two scans from a distance. A paragraph wants a hand-sized print.
• Print it bigger than you think. Dense codes are unforgiving. If it is going on equipment, test the actual printed label at the actual distance before ordering a batch.
• Put the long version behind a link, and the short version in the code. "Pump 4, service every 500 hours" in the pattern; the manual on a page.

Getting the print size right is most of whether it works at all: why QR codes refuse to scan is worth reading before a print run.

Making one

Type the text into our text QR generator and download it. Use SVG for anything going to a printer, so it stays sharp at any size.

Then scan your own code, from the printed version rather than the screen, at the distance someone will really stand. Codes that scan perfectly on a monitor and fail on a label are the most common and the most expensive mistake here.

Use text when the information is short, fixed, and has to work without anything else being alive. Use a link for everything else.