If you have spoken at a conference or meetup, you have probably received the email a week before the event: "Please send your slides as a PowerPoint file by Friday." For speakers who build talks in HTML, using reveal.js, Slidev, Marp or a custom setup, this request can feel a little old-fashioned. Yet organisers have good reasons for asking, and with a bit of preparation it is easy to give them what they need without abandoning your preferred tools.
Why organisers want a PowerPoint file
From the organiser's side, every talk needs to run smoothly on a shared machine in a room they may not control. A few practical concerns drive the request:
- Venue laptops. Many venues provide a single presentation PC with PowerPoint installed and limited internet. A local file is far less risky than a URL.
- Quick switching. In tightly scheduled tracks, the AV team needs to load the next speaker's deck in seconds.
- Archiving. Conferences often publish slides afterwards on their website or share them with sponsors. A single file per talk is easy to store, review and upload.
- Review. Some events check slides for code of conduct issues or sponsor logos before the day.
None of these needs requires the file to be heavily editable. Organisers mostly want something that opens reliably and looks the way you intended.
Plan for the conversion early
HTML decks can do things a PowerPoint file cannot easily reproduce: live code demos, embedded iframes, interactive charts and smooth fragment animations. Before the deadline, go through your talk and mark slides that depend on these features. For each one, decide on a static fallback:
- Replace a live demo with a screenshot plus a short note of what happens.
- Split fragment animations into a series of slides that show each step.
- Turn an embedded web page into an image with its URL written underneath.
- Export interactive charts as a clean static chart at the size you want.
This work also protects you on stage. If the Wi-Fi fails, your fallback slides keep the talk moving.
Fix the slide size
Most venues use 16:9 projectors. Set your HTML deck to a fixed 1920 by 1080 or 1280 by 720 layout before converting. Responsive layouts that change at different widths may produce surprises once captured as fixed slides.
Convert and review
Once the deck is ready, run it through a converter. Browser-based tools such as HTML to PPTX capture each slide's appearance into a PowerPoint file you can hand straight to the organiser. Because the focus is on visual fidelity, your typography, colours and layout look the way they did in the browser, which is usually exactly what an archive needs.
After converting, open the file on a machine without your custom fonts or development setup and click through every slide. Check that code blocks are legible from the back of a room, that no slide is cut off and that the order matches your talk.
Add speaker notes and links
A file without notes can be hard to follow for someone reading it later. Add a sentence or two of speaker notes to key slides, and include a final slide with your contact details and links to the live HTML version and any code repository. People who want the interactive experience can visit the original, while the PowerPoint serves as a reliable snapshot.
Name and size the file sensibly
Organisers handle dozens of files. Use a clear name such as "2026-11-Conference-Lee-Accessible-Animations.pptx". If the file is very large because of high-resolution captures, check the event's upload limit and compress images if needed.
Keep both versions
The HTML deck remains your source of truth for future edits and reuse. The PowerPoint file is the portable copy for organisers, archives and colleagues who just want to flip through. Treating them as two outputs with different jobs takes the friction out of the request and lets you keep building talks the way you like.
The next time that "please send PPTX" email arrives, you will already have a routine: fallback slides, fixed size, convert, review, add notes and send. It takes less than an hour and saves a lot of stress on the day.
Top comments (0)