Two Ways to Secure Every PDF

It depends on which route you use. Online Sharing (the browser link) cannot block screenshots: shortcuts such as Win+Shift+S or PrtScn are handled by the operating system before the web page is aware of them, so no website can intercept them. The MaiPDF app can block them, because it asks the operating system itself to exclude its window from capture, which makes screenshots and screen recordings come back black. If screenshots are your main concern, use App DRM.

Online Sharing turns a PDF into a link or QR code hosted by MaiPDF. Recipients open it in a normal browser with no app or account, and you can set open limits, session length, expiry, dynamic watermarks, download and print blocking, and email verification. App DRM packs the PDF into an encrypted .maipdf file that opens only in the MaiPDF app; it adds screenshot blocking, device binding, revocation after delivery and activity logs. Online Sharing is faster and easier for recipients; App DRM offers stronger protection.

With App DRM the file is not stored on MaiPDF servers. The PDF is packed into an encrypted .maipdf file that stays on your own device, and you deliver it yourself through any channel you like - email, WeChat, AirDrop, a USB stick. The access rules, expiry, revocation and copyright controls travel with the file. This is a deliberate design choice so that you keep control of your own document.

No. Guest sharing has been supported from the start and still is. As a guest you receive two codes after uploading: a reading code, which recipients use to open the document, and a modification code, which you keep in order to replace the file or change its settings later - keep the modification code safe, it is the only way back in. If you sign in, everything is managed from the Control Center instead: all reading codes, access records, limits, expiry, file replacement and revocation, without needing to track codes yourself.

If you are signed in, open Control Center and select the reading code. Session length can be edited directly there; the open limit, expiry, allowlist, view mode and watermark are fixed at upload and change only by replacing the share. If you shared as a guest, use the modification code you received when you uploaded - it lets you replace the file or update its settings without an account. In both cases the original share link stays the same, so recipients do not need a new link.

No. A dynamic watermark does not prevent a screenshot from being taken; it makes the result traceable. Each viewer sees their own identifying mark tiled across every page, so if a captured image leaks, it can be matched back to the person who opened the document. It is a deterrent and an accountability tool rather than a block.

Yes, the older HTML package still works and existing files are unaffected, but it is no longer recommended for new documents. It bundles a protected PDF into a self-contained HTML file that you send yourself. Because it is still a browser-based viewer, it has the same screenshot limitation as Online Sharing while also requiring you to send a file. Use Online Sharing if you want to send nothing but a link, or App DRM if the file itself needs to stay protected.