Verify our privacy claims live, from your browser▾
These values are computed in your browser right now. No server round-trip. Click any row for a one-line explanation.
Outbound requests after page load…Expected: 0Everything runs in your browser, so no data ever leaves after the initial page load.
Third-party domains contacted…Expected: 0No analytics, no CDN fonts, no avatar services, no trackers — single origin only.
Cookies set…Expected: 0No session, no analytics, no preferences in cookies. Nothing to sync, nothing to leak.
localStorage keys…Only your saved QRs and preferencesSaved templates, history, and language preference. Inspected in Application → Local Storage.
Service worker status…Offline-readyStatic assets cached for offline use. You can disable your network and the generator still works.
Network status…Offline proof: turn off WiFi, click Generate. Still works.The simplest proof. If this were secretly a client for a server, offline would break it.
This symbology renders monochrome with foreground and background colours only. Templates, dot/eye shapes, gradients, frames, and centre logos are QR-only features and are hidden here.
Zobrazit dalších 30 šablon
Uložte styl tlačítkem výše, abyste si sem uchovali své oblíbené.
#000000
#FFFFFF
#8B5CF6
Nebo vyberte vestavěnou ikonu:
Zobrazit dalších 108 ikon
No icons match your search.
Vykreslí se za QR se sníženou neprůhledností. Automaticky vynucuje EC=H, aby QR stále prosvítal skrz fotografii.
Hromadné generování
Nahrajte CSV a vygenerujte až 500 QR kódů v jedné dávce. Každý řádek se stane samostatným QR — vyberte šablonu nebo přepište 21 vlastností pro jednotlivé řádky: barvy, rámečky, styly bodů/oček/očních bulv, přechody, průhlednost, velikost, korekce chyb, formát, vestavěné logo a další.
21 sloupců: type, data, filename, frametext, frame, template, fgcolor, bgcolor, size, ec, dotstyle, eyestyle, format, logo, gradient, g2, gtype, gangle, transparent, eyeball, eyecolor. Povinné jsou pouze type a data. Pro oddělení polí v data použijte | (např. ssid|password|WPA).
Podporováno je všech 20 typů QR, včetně URL, WiFi, vCard, MeCard, e-mail, SMS, událost, poloha, UPI, SEPA, PayPal, kryptoměny, Micro QR a rMQR. Stáhněte si vzorové CSV a uvidíte všechny sloupce, všech 40 šablon, 11 stylů rámečků a 12 vestavěných log v akci.
1. Stáhněte vzorové CSV · 2. Upravte jej svými daty · 3. Nahrajte jej zde
Uložte celý QR — typ, všechny hodnoty polí, styl, rámeček, logo, design vizitky — jako jeden soubor .qr.json. Později jej načtěte a vše se obnoví jediným kliknutím.
Zadejte obsah pro vygenerování QR kódu
Encoded payload
Nedávné
You're editing an existing Pro code. Click "Update Pro code" below to save your changes back to Pro.
Need to change the destination after it's printed?
Volitelné: uložit jako Pro krátký kód, abyste mohli později změnit cíl bez opětovného tisku. Ochrana heslem, plánovaná aktivace, analýza tepelných map a ROI, veřejné statistické stránky a statický záložní QR. 90denní ochranná lhůta, žádný lock-in.
Naskenujte QR kód fotoaparátem, nahrajte obrázek nebo vložte ze schránky
BCBP (Bar-Coded Boarding Pass) is the IATA-mandated machine-readable format for boarding passes, defined by Resolution 792 and specified in the BCBP Implementation Guide v7. Over 200 airlines implement it — every major global, regional, and low-cost carrier. The format encodes up to 4 flight legs in a single fixed-width string that gate scanners, kiosks, and lounge readers decode the same way everywhere.
Which symbology to use
Aztec (ISO/IEC 24778) — the preferred symbology for mobile boarding passes. Reads well on low-contrast phone screens, corrects for glare, and requires no quiet zone. Apple Wallet and Google Wallet use Aztec for their boarding-pass passes.
QR code — used by modern gate readers and some low-cost carriers. Widely supported by phone cameras, which matters for self-service kiosks.
PDF417 (ISO/IEC 15438) — the classic symbology for printed paper boarding passes on Type-A boarding-pass stock. Stacked linear format, requires a conveyor-style laser scanner.
BCBP string structure
The mandatory header is M1 — format code "M" plus the number of legs (1–4). Then, for each leg, a fixed sequence of fields: passenger name (20 chars), electronic ticket indicator, operating-carrier PNR (7 chars), from airport (3 chars, IATA), to airport (3 chars, IATA), carrier designator (3 chars), flight number (5 chars), date of flight (3 chars, Julian day-of-year), compartment code (1 char), seat number (4 chars), check-in sequence (5 chars), passenger status (1 char), conditional section size (2 hex chars). Optional conditional section follows with per-leg extras, security data, and FFP information.
What the structured builder emits
Our structured builder produces the mandatory header + a single-leg mandatory section with no conditional data. This is sufficient for gate scanners and for most airline-interop demos. For production use, an airline's PSS (Amadeus Altea, Sabre SabreSonic, Navitaire NewSkies, HP Shares) issues the full BCBP string with the correct security hash and multi-leg data — paste that in the Advanced section to preserve every field.
Date encoding
The date field is a 3-character Julian day-of-year (day 1 = January 1, day 144 = May 24, day 365/366 = December 31). We compute it automatically from the date picker. Note that the year is not encoded in the mandatory BCBP section — scanners infer it from context (check-in window, current date). For post-midnight boarding (day-of-year rollover), use the Advanced paste to override if needed.
Také od Abundera
Elektronické podpisy, které obstojí u soudu
Abundera Sign jde nad rámec základních elektronických podpisů. Každý dokument získá kryptografický důkaz, nezávislé ověření a balíček důkazů odolný proti manipulaci.
Automaticky generované balíčky důkazů připravené pro soud
Osobní pečeť dokumentu — okamžitě detekuje manipulaci
Ukotveno v 5 nezávislých systémech — žádný jediný bod selhání
The string is structurally valid BCBP, readable by any IATA-compliant gate scanner. But it carries no cryptographic signature — airline gate systems validate against their own Departure Control System (DCS) at the gate. A BCBP string you generate without being on the passenger list will decode correctly but will NOT board you on the flight.
Can I test my BCBP parser against the output?
Yes — that's one of the most common legitimate uses. Developers building airline apps, kiosks, lounge readers, and loyalty integrations need known-good BCBP strings to test parsers. Our structured output exactly matches the Resolution 792 fixed-width spec for the mandatory section.
What's the Julian day format?
Day of the year, 1–366, zero-padded to 3 digits. January 1 is 001; December 31 is 365 (or 366 in leap years). We compute it from your date picker automatically. The year isn't in the mandatory section — scanners derive it from context.
Does the PNR matter?
It's the 6–7 character airline booking reference (also called the record locator). Real PNRs are alphanumeric and issued by the airline's reservation system. For testing, any 6-character uppercase string like ABC123 works. For production, use the actual PNR from the booking.
Which symbology scans fastest at the gate?
Aztec on a phone screen — it's what the spec was designed for. Modern airports (LAX, DFW, LHR, SIN, NRT) use imagers that read all three symbologies in under 100ms. Printed paper passes still commonly use PDF417 because laser-line scanners at older gates prefer stacked-linear formats.
Can I encode multiple flight legs?
Not with the structured builder — it emits a single-leg M1 header. For 2–4 legs, paste the full BCBP string from your PSS in the Advanced section. The format is M{N} where N is the leg count, followed by N mandatory-section blocks.
What about SSR codes (wheelchair, special meal)?
SSR codes live in the conditional section, not the mandatory one. The structured builder omits them. Paste the full BCBP from the PSS to preserve conditional fields.
What if my carrier uses a custom format?
Some low-cost carriers (esp. regional Asian and Latin American airlines) use non-BCBP custom QR formats for boarding. Those aren't standardised — if your target is one of those, paste the raw custom string in the Advanced section and generate a QR wrapping it verbatim.
How does this relate to Apple Wallet / Google Wallet passes?
Apple Wallet (.pkpass) and Google Wallet passes are containers that embed a BCBP-encoded Aztec or PDF417 barcode. The outer container format is Apple/Google's; the inner barcode is BCBP. Our generator produces the BCBP string you'd embed inside such a pass.