Claude HTML to PPT has no direct conversion. You either rebuild the slides as text, or carry each slide across as a picture.

The reason is structural. HTML lays out with CSS, which reflows. PowerPoint places shapes and text boxes at coordinates on a fixed canvas. Nothing maps one to one between them.
That leaves four routes, and picking one is a question about what happens to the deck next.
Claude HTML to PPT: the four routes
| Route | Text editable in PowerPoint | Design survives | Effort |
|---|---|---|---|
| Rebuild from an outline | Yes | No, your template replaces it | Medium |
| One picture per slide | No | Yes | Low |
| Print to PDF, then insert pages as pictures | No | Yes | Low |
| Do not convert, send the link | Not applicable | Yes | Lowest |
The last row is not avoidance. If the deck is being sent rather than co-edited, converting is work that buys nothing.
Route one: rebuild from an outline
Use this when someone else will edit the deck, or when your organisation's template is mandatory.
- Ask for the deck content as a plain outline: one slide title per top level line, bullets indented beneath it, no styling.
- Open PowerPoint, switch to outline view, and paste. Each top level line becomes a slide.
- Apply your template so the slides take the corporate design.
- Rebuild charts natively, since a chart drawn by a script has no text form to carry over.
You lose the design the model produced and keep everything editable. For decks that go into a shared drive and get changed by three people, that is the right trade.
Route two: one picture per slide
Use this when the content is final and the design is the point.

Capture each slide as an image with HTML to image, then insert the images into PowerPoint one per slide, sized to fill the slide area.
Two details make the difference between this looking right and looking amateur.
Fix the slide size first. Each slide section needs a fixed 16 by 9 area. If the page grows with its content, your captures arrive at mixed proportions and the deck looks uneven.
Put the slide title in the notes field. Pictures are not searchable, and a deck nobody can search is a deck nobody finds later.
Route three: print to PDF first
The browser print dialogue produces a PDF, and with one slide per page that PDF is already a usable handout.
PowerPoint does not import PDF pages as slides. You still insert them as pictures, which makes this route equivalent to route two with an extra step, unless you wanted the PDF anyway.
The step is worth it when the deck is also being emailed, since a PDF opens everywhere. AI HTML to PDF covers the print setup, including how to stop page breaks landing in the middle of a slide.
Route four: leave it as a page
Ask what PowerPoint is actually for in this case.
- Presenting: a browser in full screen presents an HTML deck perfectly well, including animation and charts.
- Sending: a link opens on a phone. A pptx file does not, reliably.
- Archiving: an address that stays current beats a file that gets copied and diverges.
- Co-editing: this is the real case for PowerPoint, and the only one.

Pasting the deck HTML into a NOS document renders it exactly as written, including dark theme, charts and scripts. Share, then Share link, then Create link gives it an address, unlisted by default, and the address stays the same after every edit.
That means a wrong figure on slide four is fixed by clicking the text and typing over it. The link you sent yesterday already points at the corrected version. Sending a slide deck as a link covers this route on its own.
Before you convert, fix the source deck
Conversion multiplies whatever is wrong with the HTML, so it is worth one pass first.
- Slide size. Fixed 16 by 9 sections, not a page that scrolls.
- Overflow. Text that runs past the bottom of a slide is invisible in a capture and obvious on screen.
- Fonts. A font loaded from the network may not be there at capture time. Embedding or substituting a system font avoids a deck of fallback type.
- Charts. Confirm they have finished drawing before capturing, since a script driven chart can capture blank.
AI generated slides HTML covers how to ask for a deck that behaves this way from the start, which is cheaper than correcting one.
Choosing, in one pass
| If the deck | Do this |
|---|---|
| Will be edited by colleagues in PowerPoint | Rebuild from an outline |
| Is final and the design matters | One picture per slide |
| Is also being emailed as a handout | Print to PDF, then insert pages |
| Is being sent for people to read | Send the link, skip PowerPoint |
| Has live charts or interaction | Send the link, since pictures kill both |
If you need a real pptx file rather than a deck of pictures, the details differ enough to be worth their own page. Claude HTML presentation to pptx covers what a genuine file conversion involves and what it costs.