Guides

Move your QR domain to QRdx

Keep printed QR codes on your own domain working with no reprint. Import the codes onto the domain in QRdx, then point the domain's DNS at QRdx. The limits, and the link shapes each provider uses.

If your printed QR codes open links on a domain you own, such as qr.yourbrand.com/menu, you can move that domain from your current provider to QRdx. The printed codes stay as they are: they open the same links, and QRdx answers them instead. Use this page before you count on "no reprint". It covers the steps, the limits, and the link shapes each provider uses.

This only works for a domain you own. Codes that open your provider's own domain, such as its short-link domain, can't move this way: point them at QRdx from the old provider until you reprint (see Keep printed codes working). If the codes have already stopped, see Why a QR code stops working.

Pro and Business

Custom domains and kept back-halves are part of Pro (up to 5 domains per workspace) and Business (up to 25). See Plans and limits.

Scan one printed code, or open one of its links, and look at the path after the domain. QRdx answers a link on your domain when the path is a single back-half: 3 to 64 letters, digits, - or _, not starting or ending with -.

Path after your domainOn QRdx
/menu or /aB3xYzWorks as it is
/aB3xYz?r=qrWorks: QRdx ignores the query string when it looks up the back-half
/menu/Works, after one redirect to the link without the slash
A prefix, such as /r/aB3xNeeds a path alias
More than one segment, such as /spring/menuNeeds a path alias
Under 3 characters, such as /abNeeds a path alias
/p/…/p/ is where QRdx serves hosted pages on your domain. See Path aliases

A path alias answers one exact old path on your domain with a QRdx code: see Path aliases.

Two more things to check:

  • Case: back-halves are case-sensitive. /Menu and /menu are different links, so import them exactly as they're printed.
  • Reserved words: api, _next, p, q, null and undefined can't be back-halves on your domain.

Not sure what you have? Contact support with one of your links.

Get the list of codes

You need each code's link, with its back-half, and its destination.

  • Export file: export the codes from your current provider. From an export file has the steps for each provider. Where a provider has no export, list the links and destinations in a spreadsheet by hand.
  • Connected account: Bitly, Rebrandly and Short.io list your links through their API, so there's no file. See From a connected account.

Export the scan history too. It stays with your current provider, and QRdx counts scans from the day of the switch.

If a code opens a page your current provider hosts (a menu, a business card, a landing page), its destination is that page on the provider's servers, which stops when you cancel. Rebuild it as a hosted page in QRdx and use that as the destination instead.

Add the domain to QRdx

Open Settings → Domains in the workspace and add the domain. Don't change its DNS yet: it stays unverified until the switch, and the printed codes keep working at your current provider meanwhile.

Plan the switch within 3 days of adding the domain. After 3 days, an unverified domain can be added by another account. The codes you imported onto it would then move to qrdx.dev, with a new back-half wherever theirs is taken there.

Import onto the domain

Open Codes, then the ⋯ menu → Import codes → From Bitly and other apps, and pick your provider.

  1. In the preview, tick Keep the original back-halves and pick your domain under Links on.
  2. Read the list of back-halves QRdx can't keep, and why. A printed link whose back-half isn't kept won't open after the switch.
  3. Import. Each run takes up to 1,000 links; run it again for the rest. A second run skips the codes already imported.

Nothing changes at your current provider during the import.

Switch the DNS at a quiet time

  1. A day ahead, lower the TTL of the domain's current record at your DNS provider, to 5 minutes (300 seconds) if it allows. The switch then reaches visitors faster.
  2. At a quiet time, such as night in your time zone, replace the record that points at your current provider with the records the Domains page shows. A subdomain gets a CNAME record and a root domain an A record. Which provider serves your domain shows what the old record usually looks like.
  3. Click Verify on the Domains page. If the record isn't found yet, try again in a few minutes. See Custom domains for the details.

Links on the domain stop working at your current provider as soon as DNS moves, and start working on QRdx once the domain is verified. The gap is usually minutes, but DNS caches can make it longer for some visitors.

Test, then cancel the old plan

Scan five printed codes from different print runs, on a phone using mobile data rather than your office Wi-Fi. A link QRdx can't match shows a "QR code not found" page: check its case and whether the preview kept its back-half.

If something is wrong, point the DNS back at your current provider. The codes work there again for as long as the old plan is active. Cancel the old plan only when the codes open through QRdx and you have its scan history.

What we found, checked on November 17, 2026. "Seen" means we found real codes with that shape on customers' own domains. "Unconfirmed" means we only saw the provider's own short links, so the shape on your domain may differ. Providers change these, so check one of your own links (step 1).

ProviderLinksOn QRdx
Bitly/<7 characters>?r=qr, and wordsYes (seen)
BL.INK/<6 characters>; on some accounts /<word>/<word>Yes (seen). Two segments need a path alias
Flowcode, on whitelabel.flowsto.com/r/<code>, where the code can be 1 character, and /s/<id>/code_batch-1/<id>Needs path aliases (seen)
Flowcode, on custom.flowcode.comNot seen on a customer's domain. Flowcode's own links are flowcode.com/p/<id>Unconfirmed. For /p/<id>, see Path aliases
Hovercode/<8 hex characters>, and wordsYes (seen)
ME-QR/l/<slug> and /<8 characters> on its own domainsUnconfirmed. /l/ needs a path alias; the short ones likely fit
QR Code Generator PRO/<4 to 6 characters> on its own qrco.deUnconfirmed, likely yes
QR Planet/<word>; one demo used /object/<id>Yes (seen). /object/<id> needs a path alias
QR TIGER/<4 to 6 characters> on its own qr1.beUnconfirmed, likely yes
QRCodeChimp/<11 to 21 characters> on its own linko.pageUnconfirmed, likely yes
RebrandlyMixed-case words joined by _ or -Yes (seen), up to 64 characters
Scanova/<4 characters>?qr=… on its own scnv.ioUnconfirmed, likely yes: the query string is ignored
Unitag/a/<6 characters>Needs path aliases (seen)
Uniqode (Beaconstac)/<6 characters> in mixed case, and wordsYes (seen)

Some companies print codes on the provider's own domain as well as their own. Uniqode codes on qrcodes.pro, for example, don't move with your domain: they need Keep printed codes working or a reprint.

Which provider serves your domain

Look up where your domain's record points, for example with dig +short qr.yourbrand.com, and match it here. This is also the record you replace in step 5.

The record points toProvider
cname.bitly.com, or A records 67.199.248.12 and 67.199.248.13 on a root domainBitly
bl2.blink.domains, or a host made for your accountBL.INK
whitelabel.flowsto.comFlowcode
scan.custom.flowcode.com or page.custom.flowcode.comFlowcode
custom_domain.hovercode.comHovercode
A host under me-qr.comME-QR
whitelabel-02.egoditor.deQR Code Generator PRO
<id>.webapp-portal.comQR Planet
qr1.beQR TIGER
cname.qrcodechimp.comQRCodeChimp
A records 13.248.148.104 and 76.223.20.46 on a root domainRebrandly
scnv.io or scnv.appScanova
<id>.qrcode.linkUnitag
A host under tapnscan.me; on older setups, a cloudfront.net hostUniqode

Was this page helpful?

Last updated on

On this page