# How to edit a QR code after printing

> You cannot edit printed ink, but you can often change what it does: if the code encodes a URL on your domain, update the redirect and every print follows. Otherwise, a new code stickered over the old works mechanically but looks like tampering to wary users, and reprinting is usually cheaper than it feels.

Source: https://useqr.app/docs/how-to/how-to-edit-a-qr-code-after-printing · Last reviewed 2026-08-21 · UseQR is free forever, no signup.

---

## What "edit" can mean once ink is dry

The pattern on the paper is permanent: the code encodes its payload directly, and no
tool can alter printed modules. So the question decomposes into three real options:
**change what the payload leads to**, **cover the old code with a new one**, or
**reprint**. Which applies depends entirely on what was encoded.

First, find out exactly what that is: scan the printed piece with
[the scanner](/scan) and read the payload. Everything below follows from it.

## Option 1: change the destination (URL on your domain)

If the code encodes `https://yourdomain.com/anything`, you hold the pen. Point that
path wherever you now need: a server redirect, a CMS page swap, a rebuilt landing
page. Every printed instance updates at once, at no cost. The mechanics and the
decision logic are in
[changing what a QR code points to](/docs/how-to/how-to-change-what-a-qr-code-points-to).

This also works as a **rescue**: if the linked page was deleted, reinstate the path or
redirect it rather than reprinting.

If the code encodes someone else's URL, or non-URL data (WiFi credentials, a vCard),
there is no destination to edit: move to the physical options.

## Option 2: sticker over it, with open eyes

A new code printed on a sticker, placed squarely over the old one, works mechanically:
the camera sees only the top layer. The caveats deserve equal billing:

- **It looks like an attack.** A code stickered over another code is the signature move
  of [QR sticker scams](/docs/security/qr-code-stickers-placed-over-real-ones), and
  security-aware users are being taught to distrust exactly this. On payment codes or
  public signage, a stickered code measurably damages trust even when legitimate.
- **Stickers age.** Edges lift, print fades outdoors: pick a
  [durable sticker stock](/docs/print/weatherproof-qr-code-stickers) if the piece lives
  outside.
- **Cover completely.** The sticker must blanket the old code plus its
  [quiet zone](/glossary/quiet-zone); a sliver of the old finder pattern peeking out
  can confuse scanners.

Reasonable for: menus in holders, internal signage, equipment labels. Wrong for:
payment standees and anything where customer trust is the product.

## Option 3: reprint: the maths is friendlier than it feels

A reprint is a one-off cost; most alternatives are recurring. Fifty new table cards or
a roll of 500 [stickers](/qr-codes-on/stickers) is a small print job, while a dynamic-QR
subscription bills every month for the lifetime of the placement: compare over the
years the print will hang, not this quarter. Reprinting is also the only option that
fixes non-URL payloads: a changed WiFi password or a new phone number simply requires
new ink.

When you do reprint, buy the insurance for next time: encode a path on **your own
domain**, so the next change is Option 1 and free. That single habit is the difference
between this page being an emergency and being routine: the full reasoning is in
[static vs dynamic](/docs/basics/static-vs-dynamic-qr-codes). And remember the code
itself [never expires](/docs/basics/do-qr-codes-expire); only destinations rot.
Validate the replacement payload in the [validator](/validate) before the new run.

## FAQ

### Can a printed QR code be edited?
The ink cannot. What can change is the destination behind an encoded URL (if you control that domain), or the physical object, by stickering a new code over the old or reprinting.

### Is it OK to put a sticker with a new QR code over the old one?
It works and is sometimes the pragmatic fix, but it mimics a known scam pattern, so avoid it on payment codes or trust-sensitive signage. Cover the old code and its quiet zone completely with durable stock.

### The page my printed code links to was deleted: what now?
If the domain is yours, recreate or redirect that path and every printed code works again. If the domain belongs to someone else, the code is beyond rescue and a reprint is the honest fix.

### How do I avoid this problem on the next print run?
Always encode a short URL on a domain you control and decide flexibility before printing. Then destination changes are a server-side edit that costs nothing, no matter how much ink is in the field.

## Try it

- https://useqr.app/url
- https://useqr.app/scan
- https://useqr.app/validate