Skip to content
Server-sideDeleted in 30 minutes

Convert ODP to HTML

Sharing an Impress deck with people who do not run LibreOffice usually ends in a format argument. A web page ends it instead: the reader needs a browser and nothing else, every slide is there, and the text stays real text that can be searched and read aloud rather than becoming a picture.

Use this without the search next time. Prathom Workbench puts Prathom's tools in your toolbar.

Add to Chrome — free
ODPHTML

Drop your ODP file here, or click to browse

Up to 50 MB. Deleted automatically after 30 minutes.

What it does

  • All slides are included, in order
  • Text remains selectable, searchable and readable by assistive software
  • Animations, transitions and timing are not carried

How to use ODP to HTML

  1. 1

    Upload the .odp

    An Impress presentation. Every slide will appear in the output.

  2. 2

    Slides become sections of a page

    Each slide is emitted as markup with its text and images, so the deck reads top to bottom in a browser.

  3. 3

    Check the speaker notes

    Decide whether they belong in a published page before you upload it anywhere public.

How it works

The ODP is unzipped and each slide is read from the content XML in order. Text boxes become text, images are extracted and referenced, and shapes are rendered or approximated. The output is a document that continues down the page rather than a slideshow with navigation.

What a browser gives you that a deck does not

Search, without opening an application. Selection and copying, without extraction. Indexing, so the content can be found by someone who was not at the talk. And screen reader access, which a slide image cannot provide at all.

For a published reference version of a talk, these four properties are the entire argument for choosing a page over an attachment.

What is left behind

The performance. Transitions, builds, timings and click-triggered effects belong to a running slideshow and mean nothing in a static document, so each slide arrives with all of its content visible.

For most published decks this is an improvement, because a reader is scanning rather than watching. Where the sequence carries meaning, keep the ODP for presenting.

The speaker notes check

Worth naming separately because it is the mistake people actually make. Notes are often candid, and a converted page can carry them into public view. Look at the output before it goes anywhere.

Styling

The deck's own formatting is carried into the markup, which suits a bare page and fights a site with its own design. Stripping it afterwards is straightforward and leaves clean structure that inherits your stylesheet.

What a web version gains, and what it cannot have

Publishing a deck as a page makes it readable by anyone with a browser, and it makes the text real text — searchable by a search engine, selectable by a reader, and available to a screen reader. A slide deck sitting behind a download link is none of those things.

What it cannot have is the presentation. Transitions, builds, timings and presenter notes have no equivalent in a page, and a deck designed as a performance — one word per slide, revealed in sequence — reads oddly as a document. Decks written to be read afterwards convert far better than decks written to be spoken over.

Examples

A public talk published after the event

talk.odp - 26 slides
talk.html - 26 sections, searchable text

Attendees who want to find one figure can use the browser's find rather than paging through a download. Search engines can index it, which a downloadable deck never allows.

A deck that relied on staged reveals

method.odp - each slide builds in three steps
method.html - each slide complete at once

The page has no playback, so all three steps show together. As a reference document that reads better; as a substitute for the talk it does not.

Frequently asked questions

Are all the slides included?

Yes, in order. A page has no length limit, so the whole deck is emitted. This is the main practical difference between converting to HTML and converting to an image: the single-image targets, PNG and JPG, can only hold the first slide, because one image file contains one image.

Why publish as a web page rather than a PDF?

Because of what a browser can do with it. The text can be searched with the browser's own find, copied without extraction, indexed by a search engine and read aloud by assistive software. A PDF supports some of that less well and requires the reader to download something first. Choose PDF when the appearance must be fixed for printing or signing.

Do the speaker notes appear?

Check the output before publishing. Notes in a deck are frequently written for the presenter rather than the audience, and a page that includes them can expose things you did not intend to share. It takes a moment to scan the result and is the one review step worth doing every time you publish a deck.