The share has a defined deadline or count, not an open-ended link that lives forever.
Expiration & Self-Destruct
Real end point
Still browser-based
Records survive expiry
One PDF. One deadline.
MaiPDF lets you attach a clear end rule to the share — an expiration date, a session length, or an open limit. When the rule is met, the link stops accepting new opens and the PDF effectively self-destructs from that entry point.
Readers use the same link or QR while the share is active. When it closes, the access record trail still stays attached to the reading code, so you can review what happened during the live window.
Expiration date
Session length
Open limit
Records keep
While active, readers use one governed online view — same URL, same QR, same rules.
After the share closes, the access history still belongs to the same reading code.
Deadline
Session timer
Open counter
End Rules
Three ways to make a share close itself.
Pick any one rule, or stack them together. Whichever is met first closes the share.
1
Expiration date
Set a fixed date. The share accepts opens until that day, then stops automatically.
2
Session length
Limit how long each reader's view lasts, so a single open cannot remain idle forever.
3
Open limit
Cap the total number of opens. After the count is reached, the link stops serving the file.
4
Stack any of them
Combine deadline, session, and count. The share closes the moment the first rule is hit.
Rules are per-share — each new link can have its own deadline.
Expiry works together with verification and watermark layers.
Closed shares no longer serve the file, but records remain visible.
Workflow
Set it once, let the share close itself.
You do not resend the PDF or manually revoke it. The rule you set at creation time enforces the end point.
1
Upload PDF
Start with the document that should stop being reachable after a clear point in time.
2
Set end rule
Pick an expiration date, session length, or open limit — or combine more than one.
3
Share link or QR
Send the same governed link or print the QR. Readers use it while the rule is valid.
4
Access closes
When the deadline arrives or the count is used up, the link no longer accepts new opens.
Settings & Records
End condition lives in the share settings.
The closing rule is part of the share configuration and works alongside the access-record layer.
Pick the end point first
- Expiration date, session length, and open limit sit in the same settings panel.
- Same panel also configures verification, view mode, and watermark.
- Each share is independent — you can create a new one with different timing any time.
History stays after expiry
- Review who opened the PDF during the live window.
- Check repeat opens, timing patterns, or expired sessions.
- Use the same reading code to inspect records — even after the share has closed.
Use Cases
Where a timed share actually helps.
Use expiration when a document has a real shelf life, not when you only want to track opens.
Proposals & quotes
A proposal valid until the end of the month should stop being reachable after the deadline — not linger in inboxes forever.
Limited-time offers
Pricing sheets, promo decks, or seasonal materials close automatically when the campaign ends.
Drafts in review
Circulate a draft for a fixed review window. Once it expires, the link stops serving the stale version.
Event & training handouts
Give attendees access during the session and for a short grace period — then let the share close itself.
FAQ
Before you set a deadline.
The rule controls future access through the hosted link — not copies that already left the share.
Can I set a PDF link to expire on a specific date?
Yes. Pick the expiration date before creating the share. The link works until that date; afterwards, it stops accepting new opens. The reading code still lets you review records.
What happens to the PDF after the share expires?
The hosted link no longer serves the file through that share. The underlying file and its access record trail remain in MaiPDF, so you can inspect the history or create a new share if needed.
Is expiration the same as self-destruct?
In MaiPDF they describe the same mechanism. "Expiration" emphasises a deadline; "self-destruct" emphasises that the link closes automatically once any end rule is met — date, duration, or count.
Can I combine expiry with verification or watermark?
Yes. Expiration, session length, open limit, email verification, and watermark are all per-share settings. You can stack any combination on the same PDF share.
Once a reader downloads or screenshots, can I expire that too?
Expiration governs access through the hosted link. Copies that were already downloaded, printed, or captured on a reader's device sit outside what a link-based rule can reach.
Can I change the deadline after sharing?
Use the reading code in Control Center to adjust the rule. You can shorten or extend expiry, or swap the file — the link stays the same reading code.
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.
- Unsupported, rooted, jailbroken, virtualized, or policy-bypassing environments should be blocked instead of trusted for sensitive files.
- 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 with a clear end point.
Upload your PDF, pick a deadline, session length, or open limit, then send the link. The share closes itself when the rule is met — and the record trail remains for later review.