Free HOTP QR Code Generator
Build standard otpauth://hotp/ QR codes for counter-based authenticator apps and hardware tokens. Pure RFC 4226, no server, no signup.
- QR Generator
- Gratis Visitekaartjes Ontwerper
- Printbare WiFi Kaarten
- Batch CSV (500 codes)
- 40 Templates
- 20 Talen
Dit barcode-formaat wordt monochroom weergegeven met alleen voorgrond- en achtergrondkleuren. Sjablonen, punt-/oogvormen, verlopen, kaders en centrale logo's gelden alleen voor QR-codes en zijn hier verborgen.
Laat 30 templates meer zien
Sla een stijl op met de knop hierboven om je favorieten hier te bewaren.
Of kies een ingebouwd icoon:
108 extra pictogrammen tonen
Wordt achter de QR weergegeven met verlaagde dekking. Forceert automatisch EC=H zodat de QR via de foto scanbaar blijft.
Batch Generatie
Upload een CSV om tot 500 QR-codes in één batch te genereren. Elke rij wordt een eigen QR — kies een sjabloon of overschrijf 21 eigenschappen per rij: kleuren, frames, stippen-/ogen-/oogbolstijlen, gradiënten, transparantie, formaat, foutcorrectie, bestandsformaat, ingebouwd logo en meer.
21 kolommen: type, data, filename, frametext, frame, template, fgcolor, bgcolor, size, ec, dotstyle, eyestyle, format, logo, gradient, g2, gtype, gangle, transparent, eyeball, eyecolor. Alleen type en data zijn verplicht. Gebruik | om velden binnen data te scheiden (bijv. ssid|password|WPA).
Alle 20 QR-types worden ondersteund, waaronder URL, WiFi, vCard, MeCard, Email, SMS, Event, Location, UPI, SEPA, PayPal, Crypto, Micro QR en rMQR. Download de voorbeeld-CSV om alle kolommen, alle 40 sjablonen, 11 framestijlen en de 12 ingebouwde logo's in actie te zien.
1. Voorbeeld-CSV downloaden · 2. Bewerken in Google Sheets, Excel, Numbers of een teksteditor · 3. Hier uploaden
Sla de hele QR â type, alle veldwaarden, stijl, frame, logo, visitekaartjesontwerp â op als één .qr.json bestand. Laad het later om alles in één klik opnieuw te maken.
Voer inhoud in om je QR-code te genereren
E-handtekeningen die standhouden in de rechtbank
Abundera Sign gaat verder dan gewone e-handtekeningen. Elk document krijgt cryptografisch bewijs, onafhankelijke verificatie en een manipulatiebestendig bewijspakket.
- Automatisch gegenereerde rechtbankklare bewijspakketten
- Persoonlijk documentzegel — detecteert manipulatie onmiddellijk
- Verankerd aan 5 onafhankelijke systemen — geen enkel storend punt
How HOTP Differs from TOTP
HOTP and TOTP both produce 6- to 8-digit one-time codes from a shared Base32 secret, and both use the same otpauth:// URI scheme. The single difference: TOTP advances the code on time (typically every 30 seconds), while HOTP advances on a counter that the client increments each time it generates a code. The server tracks the same counter and accepts codes within a small look-ahead window.
HOTP is the right choice when you can't trust the device clock, when the device has no clock (hardware tokens), or when codes need to remain valid until they are used (login flows where typing time matters). The trade-off is that the counter can drift if the user generates codes without submitting them — most servers handle this with a re-sync window of 10 to 50 codes.
Where HOTP shines
- YubiKey OTP slot — the original use case. Press the button, the YubiKey emits the next HOTP code as keystrokes.
- Hardware tokens — Feitian c100, RSA SecurID 700-series, programmable tokens from Token2 and Protectimus. All ship with HOTP firmware.
- Air-gapped systems — submarines, remote sensors, factory-floor terminals where time sync is unreliable but a counter is durable.
- Server-side OTP backup — single-use recovery codes are HOTP under the hood, with the counter incremented per use.
Fields explained
- Issuer — service name (e.g. GitHub). Shown as the heading in the authenticator app.
- Account — usually your username or email. Shown as the subheading.
- Secret — Base32-encoded shared secret. 16, 26, or 32 characters typically.
- Algorithm — SHA1 (default), SHA256, or SHA512.
- Digits — 6 (default) or 8.
- Initial counter — usually 0. Set to a higher value if re-provisioning a token that has already been used.
Privacy
The shared secret is sensitive. Abundera QR runs entirely in your browser — the secret never touches a server, never gets logged, never leaves your device. Generate on an offline laptop for maximum paranoia.
Beschikbaar in 26 talen
Volledig vertaalde UI, native scriptweergave en rechts-naar-links-ondersteuning voor Arabisch en Urdu.
Frequently Asked Questions
Which apps and tokens can read these HOTP QR codes?
Any standards-compliant HOTP implementation: Aegis, Raivo, FreeOTP, FreeOTP+, KeePassXC, Yubico Authenticator, Token2 personalization tools, Protectimus desktop tools, and most modern enterprise IAM platforms (Okta, Auth0, Keycloak). Note: Google Authenticator quietly ignores the counter parameter and treats everything as TOTP — pick a different app for HOTP setups.
How is HOTP different from a YubiKey FIDO2 / WebAuthn key?
Different protocol entirely. HOTP is a shared-secret one-time-code scheme (RFC 4226). FIDO2/WebAuthn is asymmetric public-key authentication. Both are 'second factors' but FIDO2 is phishing-resistant where HOTP is not. HOTP is a fit when the relying party only supports OTP, or when you specifically need a code that can be typed.
What happens if the counter drifts out of sync?
Most servers accept codes within a look-ahead window (typically 10 codes) and resync the counter when a valid forward code arrives. If drift exceeds the window the user has to re-enroll. Some IAM platforms expose a 'resync' admin action that takes two consecutive codes to recompute the offset.
Why does Google Authenticator give wrong codes for HOTP QRs?
Google Authenticator treats every otpauth:// QR as TOTP regardless of the path. The codes it produces are valid TOTP codes against your secret — not HOTP codes — so the server rejects them. Use Aegis, Raivo, Yubico Authenticator, or a hardware token instead.
Can I program a YubiKey OTP slot from this QR?
Not directly. YubiKey OTP slots are programmed with the YubiKey Manager (GUI) or ykman (CLI). You can copy the Base32 secret from the form into ykman: ykman oath accounts add --type HOTP --algorithm SHA1 --digits 6 ISSUER:ACCOUNT <secret>.
What's the maximum counter value?
RFC 4226 allows counters up to 2^63 - 1. Practically, most implementations cap it lower (32-bit on legacy hardware). Hundreds of thousands of presses is fine on any modern token.
Should I use HOTP or TOTP for new deployments?
TOTP for almost everything. HOTP is the right pick only for: hardware tokens that lack a clock, deeply air-gapped environments, or single-use recovery codes. For phone-based 2FA, time-based codes are the standard and the user experience is significantly better.