What comes out
Semantic markup with nothing styled inline. Each slide becomes a
<section> with an id you can link to, the title
becomes an <h2>, indented bullets become a
<ul> with a level class on the nested items, and
speaker notes — if you include them — go into an
<aside>.
Because nothing carries inline styles, the result inherits whatever your site already looks like rather than fighting it. That is the difference between markup you can use and markup you have to clean up first.
Fragment or full page
Leave the full-page option on and you get a standalone file: a
doctype, a charset, a viewport tag and a small stylesheet, ready to
open in a browser. Turn it off and you get just the sections, which
is what you want when pasting into a CMS, a blog editor or an
existing template — nesting a second
<html> element inside a page is a reliable way to
break it.
The Copy button puts the markup straight on your clipboard, which is usually quicker than downloading a file in order to open it and copy out of it.
Everything is escaped
Every character taken from the deck is HTML-escaped before it reaches the output. A slide containing angle brackets, an ampersand, or something that looks like a tag comes out as visible text rather than as markup — so nothing in the file you converted can turn into executable code on the page you paste it into.
This matters more than it sounds. A converter that passes slide text through unescaped hands whoever wrote the deck a way to inject markup into your site, and it is exactly the kind of thing that goes unnoticed until it does not.
Styling what you paste
The markup carries class names so you can target it without touching
the content. Each slide is section.slide with an
id of slide-1, slide-2 and so
on, which means you can link straight to a particular slide from
elsewhere on the page. Nested bullets carry lvl-2 and
lvl-3, and speaker notes sit in
aside.notes.
Four rules are usually enough: something to separate the sections, an indent for the nested levels, a quieter treatment for the notes, and whatever your headings already look like. If you turned the full-page option on, that file ships with exactly those four so you can see the shape before deciding what to keep.
How a slide becomes a section
The title comes from whichever shape PowerPoint marks as the title placeholder, not just the biggest piece of text on the slide — so a caption that happens to be in a large font is not mistaken for a heading. Everything else on the slide becomes body text, split into paragraphs by the outline level PowerPoint stored with each one. Only that first title placeholder is used; a second text box that also happens to hold a heading-looking line stays in the bullet list.
Speaker notes are matched to their slide through the file's own relationship records, not by counting — PowerPoint only creates a notes part for a slide that actually has notes, so the numbers drift apart the moment one slide lacks them, and matching by position would quietly attach the wrong notes to the wrong slide.
For example, a slide titled "Q3 results" with three
indented bullets underneath produces an <h2>
reading "Q3 results" followed by a <ul>
of three <li> items, each carrying a
lvl-2 class if it was indented one level in. A
top-level line with no indentation becomes an ordinary
<li> with no level class at all.
Only the text is read
A .pptx is a ZIP archive, and this reads two folders out
of it — the slides and the speaker notes — and ignores the rest.
Images, embedded fonts, charts and the theme are never opened, which
is why a fifty-megabyte deck full of photographs converts about as
fast as a five-megabyte one: the part that makes the file large is
never touched.
The check for a legacy .ppt file does not rely on the
file extension either. It looks at the first bytes of the file
itself — a real .pptx starts with the two-byte
signature every ZIP archive uses, while the old binary format
starts with a different signature entirely. Rename a
.ppt to .pptx and it is still rejected,
correctly, because the file itself has not changed.
What does not come across
Layout, images, charts, tables, colours, fonts and animation. This converts the text and its structure, not the design of the slides — there is no honest way to turn a deck's visual arrangement into readable web content, and pretending otherwise produces a page full of absolutely-positioned boxes that nobody wants.
Slides with no text at all — a full-page photograph, a diagram — come through as an empty section, and the preview counts them before you convert so you can see how much of the deck that applies to.
Formats and privacy
.pptx only, up to fifty megabytes. The old binary
.ppt is a different format and is refused by name;
re-save it as .pptx from any presentation program.
Everything happens in your browser — the deck is read there, the
HTML is generated there, and this page has no upload endpoint. Only
the text parts of the archive are read, so the images in your deck
are never even decoded.
If you want a Word document instead of markup — handouts or revision notes rather than something to paste into a page — the PPT to Word converter reads the same kind of file and keeps the same preview-before-download approach. Starting from a photo instead of a deck? The JPG to Word converter and the Text to HTML converter cover the other two directions this page does not.