Using CMYK QR Codes
Did you know your QR Planet Codes support CMYK?
If your QR Codes are headed to print - offset press, product packaging, branded collateral - there's a detail that's easy to overlook until it's too late: the color mode.
Why the color mode matters
Screens build colors by emitting light (RGB: red, green, blue). Print works the opposite way - ink absorbs light, and the press combines cyan, magenta, yellow, and black (CMYK) to produce the desired color. These are fundamentally different color spaces, and they don't perfectly map to each other. A vivid brand color in RGB can shift noticeably when converted to CMYK at the printer's end, especially with certain printing-profiles (ICC profiles).
For text and images this is a known quantity, routinely managed by designers. For QR Codes, however, color shift isn't just an aesthetic problem - sufficient contrast between fore- and background is a functional requirement. A conversion that slightly muddies a dark module color against a light background can affect scanability in real-world conditions.
What 'RGB by default' can actually cost
If you download a QR Code in RGB and hand it off to a print shop or drop it into a CMYK design file, one of two things will happen: the software converts it automatically (with results that depend on the active ICC profile), or the press operator flags it. Either way, you've lost control of the output. With branded QR Codes - custom colors,
embedded logo, styled frame - that loss of control is more consequential than with a plain black-on-white Code.
The professional way: CMYK QR Codes
QR Planet lets you define your QR Code colors natively in CMYK from the start and
export directly as a PDF with the CMYK color profile intact. That file drops cleanly into Adobe Illustrator or Photoshop without color mode conflicts, enabling you to verify the exact CMYK values on any element before it goes to press. Your brand colors stay your brand colors.
If you're working on anything destined for physical print, it's worth doing it right from the start rather than fixing it downstream.
Designer QR Code ToolImplementing your domain into your QR Planet account
Your QR Codes, your domain - a reminder about Domain Masking
Every dynamic QR Code contains a redirect URL - the Short URL encoded within the pattern that routes a scan to its destination. By default, this URL lives on our infrastructure. Most users never think about that; but for anyone taking QR Codes seriously as a brand touch point, it's worth a closer look.
What the URL in your QR Code actually says about you
When someone scans a QR Code and their phone briefly shows a redirect URL, the displayed domain is part of the experience. A URL on your own domain -
qr.yourcompany.com - reads very differently from a generic third-party short link (like subdomains of qrplanet.com). For enterprise deployments, printed marketing material, or anywhere a QR Code is presented as part of a professional identity, the difference in perceived legitimacy is real. It's the same reason companies use branded email domains instead of Gmail.
Pair that with a
custom-designed QR Code in your corporate CI - your brand colors, your logo embedded in the code, your
custom frame - and the result is a coherent branded artifact rather than a technical utility.
Portability: an underappreciated argument
There's a more pragmatic reason to care about domain masking that rarely comes up until it matters: if the redirect domain is owned by a third-party QR provider and you ever switch platforms, every Code already printed or distributed becomes a liability. The redirect URLs encoded in those Codes still point to the old infrastructure.
With Domain Masking, the redirect domain is yours. You control the DNS. If you ever need to migrate to a different QR management solution, you can repoint your subdomain and your existing Codes continue to work - no reprint, no broken Codes.
Minimal Setup
Technically, it comes down to creating a subdomain (e.g.
qr.yourdomain.com, but it can be anything you like) and setting a CNAME record pointing to your QR Planet instance. SSL is handled automatically. Read the
full setup guide for Domain Masking if you want the details.
Domain Masking is included in
White Label accounts and is also available as an add-on for Premium plans. If you're on Premium and want to enable it, please don't hesitate to
contact us.
Language Settings
QR Planet speaks your language - and your users' language, too
Platform language is one of those things that only becomes a problem when it's wrong. If you're running a QR management platform for a team, an agency, or end users in a specific market, having the interface show up in the wrong language - or no supported language at all - can create unnecessary friction at every step.
What's available out of the box
The platform ships with German, English, Spanish, Portuguese, Swedish, French, Italian and Catalan. For most deployments in the Western markets, that covers the ground without need for any complex configuration.
Where it gets interesting: custom languages
White Label accounts can go further: Any language not already in the platform can be added - including languages with right-to-left script such as Arabic or Hebrew, which the platform supports by default with an RTL toggle. The translation workflow is straightforward: export a language pack, run it through machine translation, import it back, and optionally fine-tune individual strings manually. Changes reflect in the interface immediately, no republishing loop required.
Beyond adding new languages, White Label accounts can also overwrite individual strings in any existing language - meaning you can adapt the platform's terminology to match your products' vocabulary, replace generic labels with your brand's wording, or localize tone and style without touching a single line of code. For agencies running white-labelled QR platforms under their own brand, this closes the last gap between "QR Planet with our logo" and a product that genuinely feels like their own.
Practical Use Cases
This matters most in three scenarios: deploying to non-Western markets where none of the built-in languages apply; running a white-label instance for end users who shouldn't be exposed to generic SaaS terminology; and operating in a regulated or specialized industry where standard UI needs to match internal language or external compliance requirements.
Manual translation with fields for all text elements