June 2000: shared rules for readers
DENSO WAVE dates the international standardisation of QR to June 2000. The ISO/IEC 18004:2000 catalogue page confirms that first edition; its life cycle records publication on 22 June. QR had existed since 1994: the standard marks a step in its spread, rather than a new invention of the symbol.
A shared specification gives encoder and reader designers a reference. The practical aim is to recover a symbol’s data without depending solely on the tool that created it. Our retrospective on the birth of QR explains the industrial need behind the format.
What a format standard describes
The 2024 edition’s catalogue page covers encoding, symbol geometry, error correction and decoding, among other topics. Those rules let software work with a shared structure. This current scope is not a transcription of the 2000 text.
To picture that structure, start with the guide to how QR codes work. If your grid becomes very dense, the content and capacity guide explains the link with the data. The word “version” can describe the grid size; it should not be confused with the year of a standard’s edition.
The symbol, its content and the action: three questions
To understand a scanning result, separate three stages:
- Does the reader recover the data?
- It needs to recognise the symbol and extract its content. An image defect can prevent this first stage.
- What does the QR code contain?
- A URL, text and a contact card carry different information. The square is an encoding medium; the content defines what is being shared.
- What does the app offer?
- It may display text, prepare a contact or offer a link. Recognising the data does not guarantee support for every action.
Built-in iPhone scanning in 2017 illustrates that last stage: a notification offers to continue. See that journey in the iOS 11 retrospective. Standardising the symbol does not authenticate the proposed website; the safety guide covers that question separately.
Changing generators: inspect the encoded address first
Take a fictional instruction page at https://example.org/notice. If that address is encoded directly, keeping the QR file preserves that content. Recreating a QR code with the same address may produce a different image; what matters is the data recovered when reading it.
If the file instead contains a redirect service’s address, that dependency remains after changing software. A shared format transfers neither the contract nor control of the domain. Start with the image reader to inspect the content, then consult the guides on choosing between static and dynamic QR and QR code lifespan. Readable data and a destination that is still available remain two separate checks.
A shared format still needs readable materials
Standardisation does not remove layout constraints. DENSO WAVE specifies a clear zone of four modules around a standard QR code. A border, text or trim that intrudes into that margin may make recognition harder.
Before a print run, check the file, its layout and the result at the intended size. Successful reading in one piece of software does not certify every device or printing condition. The PNG, SVG or PDF and printing at the right size guides help you prepare the material; the unreadable QR diagnostic helps locate a failure. You can then open the generator with your chosen destination.
Why is the 2000 catalogue entry marked “withdrawn”?
A standard can be revised. The first edition is no longer the published reference edition: ISO marks its entry as withdrawn and points to the 2024 edition. On 30 October 2026, the fifth edition is still listed as a working draft under development.
Those statuses apply to the standards documents. They do not, by themselves, say that an existing printed label has become unreadable or that its page still works. For an existing file, inspect the data, reading on the intended devices and the destination. For a professional project’s conformance requirement, identify the requested edition and checks rather than inferring certification from a successful scan.