How to present from the browser (no install, no app, just a link)

You are about to present, and the laptop in front of you does not have PowerPoint. Or it is not your laptop. Or it is a conference machine, a borrowed monitor, a tablet someone handed you. The old reflex is panic: find the app, install it, hope your file opens without mangling the fonts. The better answer is that you don't need the app at all. If your deck is a web page, the browser already on that machine is your presentation software.

This post is about presenting from the browser: how a browser-based slideshow actually works, the specific problems it removes, the few it doesn't, and how to decide when a link beats a file. No product pitch up front, just the mechanics.

What "present from the browser" actually means

A normal presentation is a desktop file (.pptx, .key) that needs a matching app to open. A browser-based slideshow is different: the slides are HTML and CSS, and the browser renders them directly. There is no app layer in between. The deck is a web page that happens to look and behave like slides.

That single change has consequences. A web page opens from a URL, so the deck travels as a link instead of an attachment. It runs on anything with a browser, which is every laptop, phone, and tablet made in the last fifteen years. And because it is a web page, it can do things a static slide file cannot: hold a live chart that updates, embed a video that actually plays, or link out to the source data. The browser is a far more capable canvas than a fixed-page file format.

The four problems it removes

1. The install.No PowerPoint, no Keynote, no "download our app to view." Your audience clicks a link and it opens. This matters most in the exact moment presentations go wrong: a borrowed machine, a client's locked-down laptop, a conference podium with mystery software.

2. The font and layout drift. When you email a .pptx and it opens on a machine missing your fonts, the layout reflows and your careful spacing breaks. A web page carries its own fonts and renders the same in any modern browser, so what you built is what they see.

3. The version sprawl. A file emailed around becomes deck_v2_final_REALLY_final.pptx in seven inboxes, each slightly different. A link is always the current version. You update the source, and everyone who opens the link sees the update. There is one canonical thing, not seven copies.

4. The device lottery. The same link presents from a laptop at the podium, a phone passed around a meeting, or a screen-share on a video call. You are not converting formats or praying the mobile viewer renders your file. It is a web page; web pages are device-agnostic by default.

How to actually do it

The mechanics are simple once the deck is a web page. Here is the whole flow:

1. Open the deck's link in any browser.
2. Enter full-screen:
   - The tool's "Present" / full-screen button, or the F key.
   - Universal fallback (the browser's own full-screen):
       Windows / Linux:  F11
       macOS:            Control + Command + F
3. Advance slides with the arrow keys or space bar.
4. Press Escape to exit full-screen.

That is the entire learning curve. Anyone who can open a link and press an arrow key can run the presentation, which is the point: the friction that used to live in software now lives nowhere.

A practical tip for live talks: open the link a minute early and enter full-screen before you start, so the address bar and tabs are gone when the room is watching. If you are screen-sharing on a call, share the specific browser tab rather than the whole screen, so your notifications stay private.

The honest limitations

Browser-based presenting is not magic, and pretending otherwise helps no one. Two real caveats:

Connectivity. A hosted link needs the network to load the first time. If you might lose Wi-Fi mid-talk, that is a risk. The fix is to keep an offline copy: export the deck as a self-contained HTML file or a PDF, download it before the talk, and open it locally if the connection drops. A self-contained HTML file runs from disk with no server at all. Treat the export as a parachute, not the main plan. We wrote more about why export formats are a fallback, not the default.

Receiver expectations. Some people genuinely need the file: a brand team that only edits in PowerPoint, a submission portal that demands an uploaded .pptx. A link does not replace that. It coexists with it. You present and share from the link, and you export a file the specific moment one is required.

When a link beats a file (and when it doesn't)

The decision is really about what the receiver does next. Two cases:

They need to view or present it. This is most of the time. Open in a meeting, read on a phone, click through on a call. A link wins outright here. It keeps the live charts and embeds, opens with no install, and stays one version.

They need to edit it in PowerPoint specifically, or guarantee offline access. Then make the file. Export the .pptx or PDF and hand it over. The link can still be your source of truth; the file is just a snapshot you generated for that need. This is the same logic behind treating the document as a link — the URL is the canonical artifact, and the file is a derivative you produce on demand.

Where Plain fits

This is the model Plain is built around: a deck is a web page from the moment it exists, not a file you later try to convert. You write the deck as Markdown, or describe it to the AI and let it draft the structure, and it renders a real web deck. Presenting is just opening that link and going full-screen — nothing to install for you, nothing to install for your audience.

Because the deck is a web page, it carries the things a slide file drops: a live chart that reflects current numbers, an embedded demo that plays inline, a long scrolling section for the parts that want more than a 16:9 box. And because the source stays plain text, the deck diffs cleanlywhen you revise, so next quarter's update is an edit, not a rebuild. When a receiver truly needs a file, Plain exports .pptx or PDF as a downgrade, and the live link stays the version everyone points at.

The short version

To present from the browser: open the deck's link, go full-screen (the tool's present button, the F key, or F11 / Control-Command-F), and advance with the arrow keys. No PowerPoint, no install, works on any device. Keep an exported HTML or PDF copy as an offline parachute, and export a .pptx only when a receiver specifically needs the file.

The shift is small to describe and large in practice: the presentation stops being a file you carry and becomes a link you send. The software you used to need is already on every machine in the room. You just have to stop attaching the file and start sharing the link.