Dark Mode Inverted is the template this gallery is most careful about, because it is also the most requested and the most likely to be misused. Light modules (#EDEDED) on a near-black background (#111111) look native inside dark-mode apps, dashboards, README files rendered in dark themes, streaming overlays, and OLED signage. The contrast between the two colors is around 15:1 — high in absolute terms. And yet this template carries an explicit scanability warning, because contrast is not the whole story: scanner pipelines are built around the assumption of dark-on-light, and inverted codes fail on a meaningful minority of real-world scanners.
Be specific about the risk. Modern phone cameras (iOS and Android stock camera apps, recent Chrome) handle inverted QR codes reliably. Older scanner apps, many enterprise scanning SDKs, and essentially all laser-line industrial imagers do not — they binarize for dark modules and never find the symbol. If your audience is "people with phones made in the last five years scanning from your dark-mode UI," this template is fine and looks far better than a white box stamped into a dark interface. If your audience is unknown, mixed, or includes dedicated scanning hardware, do not use it. There is no aesthetic worth a failed scan you cannot debug remotely.
The template mitigates what it can: Level Q error correction for 25% recovery, rounded dots that stay crisp on OLED subpixel layouts, and a frameless design that assumes the surrounding UI provides the quiet zone. That last point is a real integration requirement — in a dark UI, the quiet zone must be the background color extending at least four modules past the symbol. A common failure is placing the code on a card or panel whose edge sits two modules from the symbol; on dark backgrounds this is visually invisible to the designer and fatal to the scanner. Enforce the quiet zone in code, not in hope.
Scanability notes: test on the oldest phone your audience plausibly uses, not your own. Test in the actual lighting — OLED glare in bright rooms can wash out light modules. Never print this template on paper unless you have tested that exact printer and lighting; print is where inverted codes die, because paper cannot emit light and ambient reflection is never as clean as a screen. For any print use, prefer a dark-on-light template.
Best for: dark-mode web apps and dashboards; developer documentation with dark themes; streaming and video overlays; OLED conference signage; in-app QR displays (2FA enrollment, device pairing) where the scanning device is a modern phone.
Avoid for: print of any kind without device-specific testing; unknown or mixed scanner audiences; industrial scanners; email (renders in unpredictable themes); and any code where failure has operational cost — ticketing, payments, access control.
Best for: - Dark-mode web apps and SaaS dashboards - Developer docs with dark themes - Streaming and video overlays - OLED conference and lobby signage - In-app QR displays (2FA enrollment, device pairing)
Avoid for: - Print without device-specific testing (inverted codes die on paper) - Unknown or mixed scanner audiences - Industrial laser scanners - Email (renders in unpredictable light/dark themes) - Ticketing, payments, or access control