Micro QR and rMQR: Different Formats

Shape is part of the format

A standard QR code has a defined square grid. Stretching it into a rectangle does not create an rMQR symbol. Cropping its corners or removing its border does not create Micro QR. Those changes damage the original format rather than convert it.

Micro QR and rMQR have their own structures, capacities and decoding requirements. They solve different space constraints through specified designs. A receiving application must understand the format it sees.

Tidy QR's generator produces standard QR codes. The compact formats are discussed in the reference library to explain their role, not to imply that a hidden setting enables their creation here.

Micro QR trades capacity for a smaller structure

DENSO WAVE describes Micro QR variants with smaller square grids. Their published dimensions range from 11 × 11 to 17 × 17 modules across the variants. The reduced structure suits small amounts of data rather than providing the same capacity as a large standard symbol in less space.

Its margin requirement differs from standard QR as well. DENSO documents a quiet zone of 2 modules for Micro QR, compared with 4 for standard QR. That distinction applies only when the symbol is actually the corresponding format.

A small-looking standard QR image still needs the standard border. The physical size on the page does not change its symbology. Identify the format from the encoder and specification rather than judging it by appearance alone.

rMQR uses a rectangular design

DENSO's rMQR information describes a rectangular format intended for narrow spaces. The published size range includes 7 × 43 through 17 × 139 modules. These are format-specific dimensions, not permission to choose arbitrary height and width values.

The rectangular footprint can be useful where a square is difficult to place. That potential advantage matters only if the scanner, encoder and downstream system support rMQR. A code that fits physically but is unreadable by the intended application does not solve the labeling problem.

Do not assume that a device described as supporting QR scanning necessarily supports every related variant. General camera help pages often describe standard consumer scanning workflows without enumerating all industrial symbologies.

A worked label-selection example

Imagine an equipment label with a narrow reserved area and a short internal identifier. The project team first checks which symbologies the installed scanners support. If rMQR is explicitly supported, an appropriate encoder and specification review may make the rectangular format a candidate.

If the audience instead uses unknown consumer phones, standard QR may be the more practical starting point. The team can shorten unnecessary content, reserve a different area or link to a stable record page. The decision comes from the receiving workflow, not only the visual space available.

In either case, print a proof with the actual data and test it in the actual application. A demonstration symbol from a vendor's page does not validate the team's own payload, printer and label material.

Capacity needs format-specific tables

The standard QR version table cannot be applied to Micro QR or rMQR by scaling its dimensions. Their modes, structure and capacity rules differ. Use the source that corresponds to the selected format.

Likewise, a maximum digit count does not mean the same number of arbitrary text characters will fit. Numeric, alphanumeric and byte representations have different requirements. Keep the mode attached to any capacity claim.

For standard QR work in Tidy QR, the complete version and correction table is available in the reference section. Compact-format facts are kept in their own pages so the distinctions remain visible rather than being blended into one misleading maximum.

Do not solve density by deforming artwork

Resizing a standard QR code proportionally preserves its square geometry. Stretching it non-proportionally changes module shapes and the relationships a reader expects. A layout tool's free-transform handle should not be used to force a code into an unsuitable slot.

Keep the exported quiet zone intact. If the available area is too small for the final payload and scan conditions, change the layout or content strategy. Removing required structure is not a valid compression technique.

A vector export preserves geometric detail through proportional scaling, but it cannot make an undersized physical module easier for a camera to resolve. Print planning still needs density, distance and material checks.

Confirm the entire system supports the choice

For specialized labeling, document the encoder, scanner configuration and downstream interpretation. A reader may decode the data while the application rejects the resulting identifier or expects another format. Successful image recognition is only part of the integration.

Test representative payload lengths and characters. An example with a short numeric identifier does not establish that a longer mixed-language record will fit or behave identically. Use the actual data constraints of the project.

Keep the format name with the approved artwork and production instructions. This prevents a later supplier from substituting a visually similar symbol that the installed readers do not support.

Choose simplicity when the audience is broad

For public menus, contact cards and website links, standard QR is the implemented Tidy QR workflow. Its type pages explain the payload and general device behavior, while the local decoder checks the rendered image.

Compact variants are valuable technical options in the right system, but their existence is not a reason to complicate an ordinary public code. Start with the format the audience can actually use and reserve sufficient space for it.

The key decision is interoperability. A smaller or narrower symbol is useful only when it still connects the intended reader, payload and action under the project's real conditions.

Plan a format change as an integration change

If an existing labeling system moves from standard QR to a compact variant, review more than the artwork. Scanner settings, software parsing, procurement specifications and support instructions may all refer to the old format. Confirm that each relevant part of the workflow accepts the new one.

Keep old and new production files clearly separated during the transition. A visually similar symbol can still require different decoder support. Test the actual application result before distributing labels, and retain an understandable fallback identifier when the operational process requires one.