Share a PDF privately, or embed the viewer

Share PDF stores the file and gives you a link instead of an attachment. The link can expire, it can be revoked, and downloads can be switched off so the file is view-only. A file up to 100 MB can be shared this way.

Creating links has its own daily allowance rather than eating your tool jobs: 10 link creates a day on Free, 100 on Pro.

Private links expire after 1, 7 or 30 days. Pick the shortest period that covers the job — a link to a landlord or an employer rarely needs thirty days, and an expired link cannot leak later.

Embeds are longer-lived on purpose, because a viewer sits on a page: 7, 30 or 90 days. When the embed expires the page shows the fallback instead of the document.

Downloads are off unless you allow them. With downloads off, a visitor can read the document in the viewer but the download control does nothing — the check is enforced when the file is requested, not just hidden in the interface.

• Sending a document for review: view-only, 7 days.
• Sending a document someone must keep: downloads on, 30 days.
• Embedding on a site you control: allowlist your domains, 30 or 90 days.

Embed PDF gives you an iframe snippet plus a height between 240 and 1200 pixels. You can allowlist up to 20 domains, and an allowlisted apex also covers its subdomains — everything else is refused at the frame level, so a copied snippet does not work on another site.

Shared and embedded documents are not meant to be indexed by search engines. The link is the access control.

Revoke it. The stored file plus its metadata is the unit of revocation — once the record is gone the link stops resolving, which is faster and more reliable than waiting for expiry. Then share a fresh link with the right people.

If the original file contained something you cannot take back, treat it as disclosed: revoking stops future access, it does not unsee what was already opened.