Free TOTP / 2FA QR Code Generator
Build standard otpauth:// QR codes for any TOTP-compatible authenticator app. Pure RFC 6238, no server, no signup.
- 二维码生成器
- 免费名片设计器
- 可打印的 WiFi 卡片
- 批量 CSV (500 个码)
- 40 种模板
- 20 种语言
本地上传保留在您的浏览器中，仅出现在打印卡片上。二维码数据使用上面的 URL。
更多字段（可选）
地址
社交资料
提示：在 Google Maps 上右键单击任意位置并复制坐标
QR 上会自动叠加一面红色瑞士国旗 — 这是瑞士银行的要求。
粘贴 BOLT11 发票（lnbc...）或 Lightning 地址。我们会添加 lightning: URI 方案前缀，以便任何 Lightning 钱包都能扫描。
兼容 Google Authenticator、Authy、1Password、Bitwarden 以及任何标准 TOTP 应用。
编码整行 authorized_keys。扫描即可将密钥复制/粘贴到新机器上。
对于非常长的密钥，请使用 rMQR 横向或拆分为多个 QR。标准 QR 上限约为 ~2KB。
官方 WireGuard 移动应用可以直接扫描这些 QR。切勿在打印的 QR 中包含您的私钥 — 仅限数字共享。
GS1 Digital Link 是零售产品 EAN-13 条形码的现代 Web 友好替代方案。解析器域名默认为 id.gs1.org，但您可以使用自己的。
从 Spotify 应用粘贴分享链接，或仅粘贴 ID。我们会自动构建 open.spotify.com URL。
格式取决于平台 — Mastodon 使用 @user@instance，Bluesky 使用 handle.bsky.social，Nostr 粘贴 npub 密钥。
Geo URI（RFC 5870）可直接在设备上的任何地图应用中打开 — Google Maps、Apple Maps、OsmAnd 等 — 无需选择供应商。
标准 BitTorrent magnet 链接。任何支持 URI 方案处理程序的 BitTorrent 客户端都可以扫描。
粘贴完整的 RFC 5545 iCalendar 负载 — 支持多个事件、闹钟和重复规则。大多数日历应用都会直接导入 QR。
本地上传保留在您的浏览器中，仅出现在打印卡片上。MeCard 二维码数据没有照片字段。
MeCard 是 vCard 的简化替代方案，某些 Android 设备更偏好使用
更多字段（可选）
地址
Micro QR 容量：35 个数字、21 个大写字母数字或约 15 字节（小写/URL）。最适合短代码、序列号和 ID。URL 请使用标准 QR。
Rectangular Micro QR — 适合试管、腕带和票据条的细长格式。最多 361 个字符。
显示更多 30 个模板
使用上面的按钮保存样式，以便将您最喜欢的样式保存在此处。
或者选择内置图标：
Renders behind the QR at reduced opacity. Auto-forces EC=H so the QR still scans through the photo.
批量生成
上传 CSV 文件，一次最多可生成 500 个二维码。每一行都会生成独立的二维码——您可以选择模板，也可以逐行自定义 21 项属性：颜色、边框、点/眼/眼球样式、渐变、透明度、尺寸、纠错等级、格式、内置 logo 等。
21 列：type, data, filename, frametext, frame, template, fgcolor, bgcolor, size, ec, dotstyle, eyestyle, format, logo, gradient, g2, gtype, gangle, transparent, eyeball, eyecolor。仅 type 和 data 为必填项。使用 | 分隔 data 内的字段（例如 ssid|password|WPA）。
支持全部 20 种二维码类型，包括 URL、WiFi、vCard、MeCard、Email、SMS、Event、Location、UPI、SEPA、PayPal、Crypto、Micro QR 和 rMQR。下载示例 CSV，查看所有列、40 个模板、11 种边框样式以及 12 个内置 logo 的实际效果。
将整个二维码——类型、所有字段值、样式、框架、徽标、名片设计——保存为单个 .qr.json 文件。稍后加载它以一键重新创建所有内容。
输入内容以生成您的二维码
在法庭上也能成立的电子签名
Abundera Sign 超越了基本的电子签名。每份文件都获得加密证明、独立验证和防篡改证据包。
- 自动生成的法庭就绪证据包
- 个人文件封印 — 即时检测篡改
- 固定在 5 个独立系统上 — 无单点故障
How TOTP QR Codes Work
TOTP (Time-based One-Time Password) is the open standard behind every modern authenticator app — Google Authenticator, Authy, 1Password, Bitwarden, Microsoft Authenticator, Aegis, FreeOTP, Raivo, and dozens more. When you set up 2FA on a service, the service generates a shared Base32 secret and packages it into an otpauth://totp/... URI. Your authenticator app scans the QR, stores the secret locally, and starts producing 6-digit codes that change every 30 seconds.
This generator builds the URI for you. Useful for self-hosted services that don't ship a QR generator, password manager migration, lab/test environments, and the moment you need to switch authenticator apps without losing your existing seeds.
Fields explained
- Issuer — the service name (e.g. GitHub). Shown as the heading in the authenticator app.
- Account — usually your username or email. Shown as the subheading.
- Secret — the Base32-encoded shared secret. Standard length is 16, 26, or 32 characters.
- Algorithm — SHA1 (default, supported everywhere), SHA256, or SHA512.
- Digits — 6 (default) or 8.
- Period — 30 seconds (default) or 60.
Privacy
The shared secret is the most sensitive thing you'll ever paste into a QR generator. Abundera QR runs entirely in your browser — the secret never touches a server, never gets logged, never leaves your device. If you're security-conscious, generate codes on an offline laptop and you're golden.
Frequently Asked Questions
Which authenticator apps work with these QR codes?
Every standards-compliant TOTP app: Google Authenticator, Microsoft Authenticator, Authy, 1Password, Bitwarden, LastPass Authenticator, Aegis, Raivo, FreeOTP, FreeOTP+, 2FAS, Ente Auth, Yubico Authenticator, KeePassXC, and many more.
Is the secret transmitted to your servers?
No. Abundera QR is a client-side static site. The Base32 secret you paste is encoded into the URI inside your browser and rendered to the canvas locally. We have no servers, no logs, no telemetry — there is nowhere for the secret to go.
What's the difference between SHA1, SHA256, and SHA512?
SHA1 is the default and is supported by every TOTP app on the market. SHA256 and SHA512 are more secure but adoption is uneven — Google Authenticator silently treats them as SHA1, which produces wrong codes. Pick SHA1 unless you control both sides.
Can I use this for HOTP (counter-based) codes too?
TOTP only for now. Most modern services have moved to TOTP. HOTP requires tracking the counter on both sides which is significantly less convenient.
How do I get the Base32 secret from my service?
When the service displays its setup QR code, there's almost always a 'Can't scan? Enter manually' link. The text shown there is the Base32 secret. Copy it into Abundera QR to regenerate the QR for a different app.
Can I store multiple TOTP entries in one QR?
No — each otpauth:// URI is a single account. To migrate many accounts at once, use Google Authenticator's export/migration QR feature, which uses a different URI scheme (otpauth-migration://).
Does the QR work if I scan it twice from different apps?
Yes. The QR contains the seed, not a token. Scanning the same QR into two apps gives you two synchronized authenticators. Useful for backup.