A .pptx is two problems at once: it's heavy enough to bounce off inbox limits, and it renders against whatever fonts and PowerPoint version the recipient happens to have, so your spacing drifts on their screen. We don't ingest .pptx itself, and we'd rather say so on the way in than after you've uploaded — but the gap is one menu item wide. PowerPoint exports a PDF from its own File menu, and a PDF drops straight in here: no converter, no install, layout and fonts exactly as you authored them. You get a private link that opens in any browser with nothing to download and no PowerPoint on their side. Reach for self-contained HTML instead when the deck's point is animation or interactivity, which a PDF flattens — we take that too, and a ZIP if it came out as a folder. The link is unguessable and never indexed, so only the people you send it to can open it.
Try it now
Drop a file — get a private link in seconds. No sign-up.
Drop an HTML, ZIP, PDF, PNG or JPEG file, or click to choose.
One file, or a ZIP bundle. Max 3 MB.
Up to 3 MB, link self-destructs after 7 days. Sign up free to keep links forever, password-protect them, and store more.
First decide what the deck should become, and the answer is usually PDF. If the deck is content — a board update, a proposal, a research readout — use PowerPoint's own Save as or Export to produce a PDF. One menu item, nothing installed, layout and fonts preserved as authored. That is the whole of step one for most decks, and it is the step people lose an afternoon to because most guides still assume the HTML route.
Go the HTML route instead when the deck depends on movement — builds, timed reveals, anything interactive — because a PDF flattens all of it. Know going in that PowerPoint itself stopped offering this: the Web Page (.htm) and Single File Web Page (.mht) save options disappeared from the Save As dialog in PowerPoint 2010 and never came back; Microsoft's own documented workaround is a one-line VBA command in the Immediate window (ActivePresentation.SaveAs "…\deck.htm", ppSaveAsHTML). Any guide telling you File → Export → HTML is describing a 2007 menu. The routes that work today: author the deck in an HTML-native slide tool so it never has to be converted, use a design or AI deck tool that exports self-contained HTML directly, or run a third-party converter and check the output before you rely on it. If your deck comes out as a folder of assets, just zip it.
Then drop the file in — PDF, HTML, or ZIP — and miinideck publishes it to a 32-character link in seconds. Your file is stored exactly as you uploaded it; for a PDF we draw the pages in the reader's own browser rather than converting anything, so the deck looks the same on their machine as it does on yours.
The link is private by default — it carries a no-index tag and a URL long enough that nobody guesses their way in — and it opens as a live web page, not a file. Send it the way you'd send any link: email, chat, a message. None of the size ceilings that bounce a fat attachment apply, and the recipient never sees a download prompt or a 'file too large' wall.
When the deck is sensitive — pricing, a board update, an unreleased pitch — switch on a password or set an expiry date so access ends on your terms. On paid tiers the page is clean and unbranded with a “created by you” credit, and you can replace the exported file later without changing the link, so the recipient's bookmark always opens the current slides.
Export the deck to PDF from PowerPoint's own File menu, then drop that PDF into miinideck. You get a private URL the recipient opens in their browser — no attachment hitting their inbox limit, no “file too large” bounce, and no need for them to have PowerPoint installed. If the deck depends on animation, export self-contained HTML instead and drop that; see below for why PowerPoint no longer makes that part easy.
Not the .pptx itself — rendering a PowerPoint document faithfully would mean being PowerPoint, so we don't try. What we take is PDF, self-contained HTML, and ZIP bundles, and PowerPoint hands you the first of those natively: Save as or Export, choose PDF, drop it here. So in practice the answer is yes in two steps, and the first step is a menu item rather than a converter you have to go find. If what you actually want is for them to open the editable .pptx and work on it, that's a different job — send the file, or use a cloud-office tool.
It isn't there, and hasn't been for a long time. Microsoft's own support documentation records that Web Page (.htm) and Single File Web Page (.mht) stopped appearing in PowerPoint's Save As dialog as of PowerPoint 2010; the workaround Microsoft publishes is a VBA command — press Alt+F11, Ctrl+G, and run ActivePresentation.SaveAs with the ppSaveAsHTML file type. If a guide tells you File → Export → HTML, it is describing PowerPoint 2007. In practice most people skip the conversion entirely: build the deck in an HTML-native slide tool, or use a design or AI deck tool that exports self-contained HTML, and there is nothing to convert. (Microsoft's limits and menus are theirs to change — checked against their documentation on 4 September 2026.)
A .pptx renders against whatever fonts, PowerPoint version, and screen the recipient happens to have, so spacing and typefaces drift. Exporting fixes that by baking the layout in: a PDF carries the fonts and positioning as you authored them, and a self-contained HTML file does the same for a deck that needs to move. Either way the link looks the same on every machine and opens in any browser — no app to install, no version mismatch.
Yes. Every link is unguessable and carries a no-index tag, so it never appears in search results and only the people you send the URL to can open it. For tighter control, add a password so even someone holding the link needs the passphrase, and set an expiry date so access ends after your pitch or review window.
Yes. Turn on Review and anyone with the link can pin a comment to the exact element they're reacting to — no account needed — and you resolve each note from your dashboard. Collecting and resolving feedback is free on every plan; exporting the whole thread as a prompt for Claude or Codex is a Studio feature.
Movement, and only movement. Animations, transitions and builds are flattened; embedded video and audio won't play; anything interactive stops being interactive; and speaker notes don't come along unless you deliberately export a layout that includes them. What survives is what most decks are actually made of — layout, typography, images, charts as drawn, and page order. If the deck argues through motion, that is exactly the case for taking the HTML route instead.
No — miinideck serves a static snapshot of your exported slides, not a live presentation server. If you need real-time co-editing, a backend, or data that changes on every load, a platform like Vercel or Netlify is the right tool for the dynamic part. What miinideck does well is the front-end slice: take a finished deck and put it behind a private link, fast. You can always replace the exported file to push an update, and the link stays the same.
No card to try, no sign-up to get a link. Sign up free to keep links forever, password-protect them, and store more.