Readers can arrive by clicking the link or scanning the QR, but they land in the same governed viewer.
DynamicQR
One share, two doors
Same rules, same records
QR survives updates
One PDF share. Link and QR.
DynamicQR turns a single MaiPDF share into two entry points: a normal URL for email/chat, and a QR code for print or on-site handoff — without splitting rules or records.
Upload once, set controls once, and reuse the same reading code later to check records, update limits, or replace the file without changing the link or reprinting the QR.
Same reading code
Link + QR output
Rules stay attached
Open limit, email verification, expiry, view mode, and access records stay attached to the same share.
Replace the PDF in Control Center and the QR still opens the updated file — no reprinting needed.
Link + QR
Same controls
Same records
Best for mixed online + offline sharing
- Send the URL in email, chat, or social messaging.
- Print the QR on posters, packaging, handouts, or flyers.
- Both routes feed the same access records later.
Workflow
Set controls once, then share by link or scan.
DynamicQR does not create a separate QR system. It is another front door into the same governed share.
1
Upload PDF
Start with the document you want reachable from both URL and QR.
2
Set access rules
Combine open limit, email verification, expiry, watermarking, and view mode.
3
Generate link + QR
The same result page outputs both. No second setup step for QR.
4
Check records later
Use the reading code in Control Center for access records and updates.
Clicks and scans count toward the same open limit.
Expiry and verification apply regardless of entry method.
Replace the file later — the QR still points correctly.
QR & Records
Scans still show up in access records.
Whether the reader arrives by link or QR, the activity stays tied to the same share and reading code.
Link and QR in one place
- One share outputs both URL and QR.
- No separate QR configuration needed.
- Use it for online and print channels immediately.
History stays attached
- Inspect opens after the share is already circulating.
- Change limits, extend expiry, or update verification list.
- Replace the PDF without changing the link or QR.
Use Cases
Where DynamicQR actually wins.
Use it when the same PDF needs to live in both digital channels and physical touchpoints.
Event posters and venue signage
Print a QR on posters so attendees scan the program or briefing. Add an expiry so the link stops after the event ends.
Packaging and product labels
Put the QR on a box or label for manuals or compliance sheets. Replace the file later without reprinting.
Classroom and training handouts
Students scan on phones while others click the link in email. Records show total opens across both routes.
Flyers and property listings
Prospects scan to open a brochure. Combine email verification if you want access restricted to qualified leads.
FAQ
Questions people ask before printing the QR.
DynamicQR is still one controlled share — just with an additional scan entry point.
Do the QR and the link share the same open limit?
Yes. Both routes point to the same share and reading code. Every open — scan or click — counts toward the same limit and logs to the same access record.
If I update the PDF after printing the QR, do I need to reprint?
No. Use the reading code in Control Center to replace the file. The share link and QR still point to the same reading code, so they automatically serve the updated file.
Can I set a different limit for scans vs clicks?
Not on the same share. The open limit applies to all opens regardless of entry method. If you need different rules per route, create separate shares.
Do watermarks and verification apply to scans?
Yes. Watermarking, email verification, expiry, and view mode are applied per share session, not per entry method. A scan triggers the same protection layer as a link click.
Beyond The Browser · App DRM
Want the operating system itself to refuse the screenshot?
Link sharing protects the file inside the browser. The MaiPDF app goes one level deeper: it hands the document to a native reader that asks the operating system to mark the window as protected. A screenshot or screen recording comes back black — and the reader still reads the page normally, with no overlay in the way.
FLAG_SECURE; on iOS and macOS the window is excluded from capture.What the app adds on top of link sharing
- OS-level capture block: the screenshot and screen recording come back black — no overlay, no reading friction.
- Encrypted
.maipdfcontainer: the file only opens inside the app, never as a raw PDF on disk. - Device binding & revoke: tie a file to a device and cut off access at any time, even after delivery.
- Hostile-environment block: refuses to open on rooted, jailbroken, or virtual-machine setups where capture is trivial.
No reading friction.
Screenshot returns black.
Every page watermarked.
Where the app is stronger
- The OS refuses the capture instead of relying on something the eye can read around.
- Screen recording is blocked at the source, not just covered frame by frame.
- Reading stays comfortable — the page is fully visible, no moving overlay.
- Protection travels with the file, not just with the browser link.
What it still cannot stop
- An external camera pointed at the screen — no software stops that.
- Desktop capture blocking is weaker than mobile; phones and tablets are the strongest case.
- It needs the reader to install the app, so it is for high-sensitivity files, not casual shares.
- Like any single control, it is one layer — pair it with watermark, expiry, and records.
Start Here
Create one share and export the QR.
Upload your PDF, enable your rules, then use the same share link online and the same QR code in print. Manage everything later from Control Center using the reading code.