How to share a presentation as a link or image — without attachments

An attached deck creates several small jobs:

• someone has to download it;
• someone has to find the right copy;
• the fonts may not match on another machine;
• a large file may be blocked by email;
• the version in the chat may not be the version being presented.

A link removes the transfer problem. There is one deck at one address. If the presenter updates the deck, the link still points to the current result. The audience does not need a copy.

Use a link when the recipient needs to:

• open the full deck;
• present it from their own browser;
• move between slides with the keyboard;
• read the speaker notes;
• forward the deck to someone else without exporting a file.

The link should open in a normal browser without an account. Before you send it, open it in a private window and check that it works without your session. That one check catches more sharing mistakes than a long checklist.

An image is better when the link is likely to be buried: a Slack channel, a text message, a calendar invite or an email preview. A 1200×630 card can show the deck title, a short summary and a QR code that points back to the live deck.

Use the image when:

• people need a visual reference in a chat;
• the meeting invite needs a preview;
• the recipient may open the message on a phone;
• you want a consistent social or email card;
• the deck link is long and easy to lose.

Do not use the image as the only delivery method if the deck contains more than one or two slides. The image is not the presentation; it is the doorway to it.

After a deck is generated, the result panel offers two actions:

1. Copy link — the full browser presentation.
2. Share image card — a 1200×630 PNG with a QR code back to the deck.

On a phone or a supported desktop browser, the image action opens the system share sheet. On a browser that does not support file sharing, the image opens in a new tab so it can be saved or forwarded from there. The presentation itself is never downloaded.

The image card is generated from the deck and cached. It is a snapshot of the title and preview, not a second editable deck.

An image is harder to retract than a link. Do not put customer names, private metrics, medical information or anything else you would not post in a public channel into a preview card. If the deck is sensitive, send the link and confirm who can open it.

Also check the QR code destination before forwarding the image. A preview is only useful if the person who scans it reaches the right deck.

Before you send a deck:

• Open the link on a phone and a desktop browser.
• Check that the first slide makes sense without the presenter.
• Read one speaker note to confirm it matches the slide.
• Copy the link, not the browser's preview URL.
• If you send an image, open it at full size and scan the QR code.
• Tell the recipient whether the link is the current version or a snapshot.

Some organizations require an editable .pptx, a PDF for legal review or a file that can be presented offline. In those cases, a browser link is not a substitute. Use the right tool for that deliverable.

For the internal update, the client working session or the class where the deck is shown on a screen, the link is usually the lower-friction option. The image card is there for the channels where a bare link would disappear.

Generate a free deck in the slide maker, then test both actions from the result panel: copy the link and share the image card. For the broader argument about browser presentations, read presenting without PowerPoint. For the speed side of the workflow, read what 30–60 seconds actually means.