ChatGPT Made You HTML Slides. How to Send Them

You asked ChatGPT, Claude, or Cursor for slides. It gave you HTML: a file, a ZIP, or a folder with index.html inside. The model did its job. Yours is delivery. Emailing that ZIP to a client is how most people stall. Recipients do not know which file to open, and you cannot update what you already sent.

You do not need to rebuild the deck in Google Slides or Canva. You need to share an HTML presentation as a URL. This is the “now what” after the generate step:

• Send it in seconds. Drop the file, copy the link, no rebuild.
• Keep the layout the model made. No re-entering slides by hand.
• Update it later. Upload a new revision to the same link when the story changes.

Prezzly does not generate the slides. Your agent does. Prezzly hosts, versions, and presents the files you already have.

Why people get stuck after the model replies

AI tools are good at emitting a self-contained page. They are not a place to hold a client-facing URL. Typical dead ends:

• You download the artifact and attach it. Mail filters hate HTML.
• You paste the code into a CodePen or gist. Fine for a demo, fragile for a stakeholder.
• You rebuild in an editor so you have a “real” deck. You lose the layout the model already designed.
• You deploy to a random static host, then forget which project is the live one.

The missing product is hosting with a share link, not another prompt.

Fastest path: drop the file, copy the link

If you have index.html or a ZIP:

1. Open Prezzly.
2. Drop the file or folder. No login required.
3. Copy the view URL. Send that.

Guest view links last 72 hours. A secret claim URL lasts 7 days. Sign in (same browser, or via the claim link) to move the deck into your library so it is not deleted. Do not treat a guest link as a permanent client deliverable.

Upload size on this path is 10 MB. That covers typical HTML, CSS, and a handful of images. If the model embedded huge base64 videos, strip them before you upload.

This is the right move when you just need to show someone the output today.

Better path: let the agent publish

If you work in Cursor or Claude, pasting files by hand is the slow version of the same job. Model Context Protocol (MCP) is how the editor talks to Prezzly. MCP for presentations lets the agent call tools on your account: create the deck, add a revision, create a share link.

You connect once on the Connections page:

• Claude in the browser: add Prezzly as a custom connector and sign in.
• Cursor / Claude Desktop / similar tools: generate a key on the same page and paste it into your client.

Then you say something like: “Publish this folder as a presentation titled Q3 review and give me a 7-day view link.” Ask the agent to update the existing deck when there is one, so you keep a single link instead of a pile of duplicates.

Prezzly is not calling ChatGPT on your behalf.

What to ask the model for (so the file actually hosts)

Agents produce cleaner decks when you give them a few constraints:

• One self-contained deck, plus its assets. Not a multi-page site.
• Standard 16:9 slides, with content kept inside the frame.
• Speaker notes included per slide if you will present.
• No reliance on browser features that need to run as a full standalone site.

If you are already on Reveal.js, you can host Reveal.js slides as well. Slide navigation and presenter control work in the browser even when you did not write that part yourself.

If the output is a long report rather than slides, say so. Publish it as a dashboard (kind=dashboard) instead of faking slide breaks.

Do not rebuild in an editor unless you must

The temptation after a good Claude artifact is to “make it official” in Gamma or Slides. That is only worth it when:

• A stakeholder specifically wants a PowerPoint file to edit. Export that from the tool that made the slides, and host the HTML here for everyone who just needs the link.
• You want a shared editing canvas and a teammate who only lives in Canva.

If the HTML already looks like the talk, host it. Re-entering twenty slides by hand is how you lose an afternoon and the original layout.

Sending it to a client, then iterating

A few habits keep the share professional:

• Claim the deck if you uploaded as a guest, then send a link from your account so you can add revisions later.
• Open the link yourself on a phone before you send it.
• Say what the link is. “This is the deck. It works in the browser. We can present from it on the call.”
• Set expectations on the link. Send it to the people who need it; it stays live for the window you choose (free-plan links up to 30 days), and you can issue a fresh link anytime. If it should stay private, share a Claude artifact privately with an email grant instead of a public link.
• Lean on revisions, not filenames. Fixes land on the same URL, so the client always opens the current deck instead of hunting for “v2.”

Paste the URL into the calendar invite. The meeting tool (Meet, Teams, Zoom, Slack) is only the conversation. The deck does not live there.

You will iterate. “Make slide 5 less busy” is a second prompt, then a new file. On a host with revisions, you publish the new version to the same presentation. Recipients keep the URL they already have.

Via MCP, ask the agent to open the current deck, edit it, and publish the update. It should not create a second presentation titled “Q3 review v2” unless you want two links.

Frequently Asked Questions (FAQ)

ChatGPT gave me a single HTML file. Is that enough?

Yes, if it is self-contained or if images are linked in a way that still works after upload. A single .html file is a valid upload. If the model also gave you a CSS file, zip them with index.html at the root.

Can Claude publish to Prezzly without me downloading anything?

Yes, after you connect Claude as an MCP client. The agent uploads files through tools. You still approve the connection once on the Connections page.

Will Prezzly generate the next version of my slides?

No. Your agent generates. Prezzly stores revisions and serves the current one. Ask the agent to edit the existing deck, then publish a revision.

How long does a guest link last?

The view link lasts 72 hours. You have 7 days to claim the deck to an account. After that, unclaimed guest content is deleted.

Can I send this inside Slack or Teams?

Yes. Paste the view URL. Those products do not need a plugin. The recipient clicks the link and the deck opens in the browser.

---

Have the HTML already? Send your AI-made deck as a link in seconds, or connect your editor and let the agent publish the next revision.