LinxyHelp Guides & support

Regenerating a Linxy Mark

In short

Regenerating rebuilds the invisible pattern inside a Mark image. You do it when the artwork changes, when the display size changes, or when a Mark reads unreliably in the field.

Regeneration never changes where the Mark points. Your destination, rules, history, and Connections all stay attached. Only the image file is replaced.

When to regenerate — and when not to

Regeneration is cheap and safe, but it does create a new image file that has to be distributed to wherever the artwork is used. That is the real cost, so it is worth knowing which situations actually call for it.

SituationRegenerate?Why
You changed the source artworkYesThe pattern is woven into the specific image. New picture, new pattern.
The Mark will now be printed at a different sizeYesThe pattern is laid down for one physical size. This is the most common reason.
Scans are unreliable in the fieldYesUsually a size problem. Regenerating at the true display size is the fix.
You changed the destination URLNoThe Mark carries an identity, not an address. Change the destination and the existing artwork follows it.
You added a geofence, expiry, or passwordNoRules are evaluated at scan time. The image is unaffected.
You want to retire the itemNoSwitch it off instead. The artwork stops working immediately.

The size rule, which decides everything

This is the single most consequential thing to understand about producing Marks, and it is the cause of the overwhelming majority of "it worked on my screen but not in print" reports.

The pattern is made of cells laid into the image at a specific density for a specific physical size. When you scale that image down afterwards — in a page layout, a browser, a print driver, an email client, anywhere — the cells are averaged into each other. Nothing warns you. The picture still looks perfect, because the pattern was invisible to begin with. It simply stops being recoverable.

CORRECT generated at 560 px printed at 560 px Cells intact Reads at normal distance, first try. WRONG generated at 1600 px scaled down to 560 px Cells averaged away Looks identical to the eye. Will not read — or reads only at about 200% zoom.
The tell-tale symptom. If a Mark reads only when you enlarge it on screen to roughly 200%, it was downscaled after generation. No amount of better lighting or steadier hands will fix that — it has to be regenerated at the true display size.
Design tools do this silently. Placing a Mark into a layout and dragging the corner to fit is a downscale. So is "fit to page" in a print dialog, and so is an email client resizing an inline image. Decide the final size first, generate for it, and place the image at 100%.

Before you start

  • Know the final display size — the actual measurement on the finished piece, not the size of your source file
  • Have the current source artwork available at good quality
  • Know everywhere the old image is currently in use, because all of it needs replacing
  • Allow time to test a physical proof before a full run

Regenerating, step by step

  1. Open the item in your Marks list.
    Find the Mark and choose Regen. You are working on the existing item, not creating a new one — this is what preserves your links and history.
  2. Set the display size first, before anything else.
    Enter the size the Mark will actually appear at. This is not a preview setting or a convenience; it determines how the pattern is laid into the image. Getting this right is the whole job.
  3. Upload replacement artwork if the picture has changed.
    If only the size is changing, keep the existing source. If the design changed, supply the new file at or above the final size — never below it.
  4. Regenerate.
    The platform rebuilds the pattern and produces a new image file.
  5. Download and distribute the new file.
    Replace the artwork everywhere it appears — layouts, print files, web pages, partner assets. The old file still carries the old pattern and will keep behaving the old way.
  6. Test at real size before committing.
    See the next section. Five minutes here prevents a print run that has to be thrown away.

Testing before you commit to a print run

Test the way a real person will encounter it, not the way you would if you were trying to make it succeed.

Physical proof, final size normal reading distance not pressed against it Test all three of these 1. Artwork filling most of the frame 2. Even, indirect light — no glare, no shadow 3. Camera roughly square to the surface Then repeat on a second phone, ideally the other platform.
A proof that reads on your own phone in good office light has told you very little. Test in the lighting the piece will actually live in, and on a device you did not choose.

What regeneration keeps and what it replaces

Kept, untouchedReplaced
The destination and every redirection ruleThe image file itself
Scan history and analyticsThe pattern inside it
Connections people have already accepted
Protection settings, geofences, expiry
The item's place in your projects and clients
Old artwork does not stop working immediately. Both files carry the same identity, so previously printed pieces keep resolving to the same destination. Regeneration is about readability, not revocation. If you need old copies to stop working, switch the item off or set an expiry instead.

If it still will not read

What you are seeingMost likely causeWhat to do
Reads on screen, not in printDownscaled in layout or at the printerConfirm the image is placed at 100% and the print pipeline is not resampling
Reads only when zoomed to about 200%Generated large, then scaled downRegenerate at the true display size
Reads on matte stock, fails on glossGlareChange the lighting, or move to a less reflective finish
Reads on one phone, not anotherCamera quality or focus distanceIncrease the display size; test on the weaker device before the run
Nothing reads at any sizeThe item may be switched offCheck the item is active and not past its expiry or scan limit
Worked for months, then stoppedArtwork was re-exported or re-placed by someoneCompare the file in use against the file you downloaded from the platform
Related reading. What is a Linxy Mark explains why the pattern behaves this way, and Redirection controls covers everything that decides where a Mark sends people once it reads.
Still need help? Contact support