I recently built QRForge, a QR code generator focused less on tracking dashboards and more on print-ready workflows.
Most QR tools I found fell into two buckets: simple one-off generators, or dynamic QR platforms that route scans through their own tracking URLs. I wanted something more boring but useful: direct static QR codes, CSV batch generation, clear previews, and export files that are ready for labels, badges, packaging, or menus.
What I built
QRForge currently supports:
- Static URL QR generation without signup
- CSV upload for batch QR projects
- First-row previews before export
- Named PNG and SVG outputs
- Manifest and error report files
- PDF project summary
- ZIP delivery for print workflows
The main idea is that a user should know what they are about to print before they generate hundreds of QR codes.
Why static QR codes?
Dynamic QR codes are useful, but they also introduce a dependency: the QR provider has to keep redirecting scans forever.
For printed materials, that tradeoff matters. A static QR code points directly to the destination URL. Once printed, it does not depend on my app staying online.
Stack
The project is built with:
- Next.js
- React
- Cloudflare Workers
- Stripe Checkout for one-time batch exports
- Server-side ZIP generation for print packs
What I am still figuring out
The biggest question is positioning.
I am testing whether “Verified Print Pack” clearly communicates the value: preview the CSV, catch obvious problems, then export a print-ready bundle.
I’d love feedback from builders, designers, or anyone who has had to generate QR codes for real-world print materials.
Project: https://qrcodegenerator.page
Top comments (1)
Building a privacy-first QR code generator is no easy task, especially for print-ready batch workflows. I've seen how frustrating it can be to find reliable tools. Our ReplyAI can help streamline your outreach efforts with personalized replies, saving you time and hassle.