SHARE PRESENTATION LINK

Send slides as a link that works in email, Slack, SMS.

30MB decks break email. Slack squeezes them. Google Slides links hit access walls. A Nanopage URL works in every channel without a sign-in.

Build mine now How it works

A 30MB deck does not fit in most email systems, gets re-encoded by Slack, and fails entirely over SMS. Sharing a Google Slides link requires the recipient to be signed in to the right account, and forwarding it to a chain of contacts almost always lands at least one person on a "request access" wall. A Nanopage URL bypasses all of it: paste the link anywhere, the recipient taps it, and the deck opens without auth.

In and out

What you bring, what you get.

What you upload

Presentation file (PPT, PPTX, ODP, or slide PDF)
Recipient context (clients? investors? team?)
Optional: a reply CTA so the link can convert, not just deliver

What you get

Public URL that works without sign-in
Link-preview metadata for clean unfurls in Slack / iMessage
Download button for people who want the file
Optional reply CTA (book a call, send a question)
Custom domain so the link looks like yours, not a generic host

Just say this

“Make this presentation easy to share as a link. No access wall.”

Then chat with the AI to change anything — copy, colors, sections, photos.

Questions

Frequently asked.

Will the link work if I send it outside my company?

Yes. Unlike Google Slides links scoped to a specific organization, Nanopage URLs are public — anyone with the URL can open the page without signing in.

Can I send this in an SMS or WhatsApp?

Yes. The Nanopage URL is short enough for SMS and unfurls into a card preview in WhatsApp and iMessage instead of plain text.

How do I know who opened the link?

Nanopage does not include built-in per-recipient tracking. For DocSend-style analytics, generate a separate Nanopage URL per recipient or layer on an external analytics tool.

What if I need to revoke access later?

Delete or unpublish the underlying site from your dashboard. Links pointing at the URL return a 404 from that moment forward.

Also good for

All use cases