Ask before you paste.

No. unPaper has no server that receives documents. The template is a file your browser downloads, the prompt is assembled in your browser, and the deck your AI returns is rendered, printed and converted in your browser. There is no upload step to opt out of, because there is no upload. Turn off your Wi-Fi after the page loads and every tool still works — that is the check, and /on-your-device explains how to run it.

Nothing you write. Your company template and your look settings are saved in your own browser's local storage, on your device, and you can clear them at any time. unPaper counts page visits in aggregate to know which pages are worth keeping — no cookies, no accounts, no profile, and nothing that touches the content of a deck. The boundary is written down: the app and anonymous page counts may use the connection, your document content never does.

Not by unPaper — there is no AI inside unPaper and no content reaches us, so there is nothing for us to train on and nothing for us to sell. What your own AI assistant does with what you paste into it is governed by your agreement with that provider, not by us. That is exactly the point of the design: your content goes to one place, the assistant you already chose and your organization already approved, instead of to that assistant plus a slide vendor.

Yes. The templates make no network requests — no external CSS, fonts, scripts or images — so a deck renders and prints identically with no connection. unPaper itself can be saved to your device from the header, after which it opens and runs from the saved copy. The same switch puts it back online.

No, and there is no queue, no render job and no per-export meter. Those limits exist to ration someone else's servers. Nothing here is uploaded, so a sixty-slide deck with embedded images is as fast as a five-slide one and the only ceiling is your own machine.

Yes, for individuals — including for your work. There is no trial period, no credit card, no export limit and no watermark. Organizations pay when they adopt it together: central approval or distribution for more than five people, shared templates, or agent automation. Private deployments on your own infrastructure are licensed separately. /for-institutions sets out the three scopes and the sixty-day evaluation that comes before any licence conversation.

No. There is nothing to sign up for and nothing to sign in to. unPaper does not know who you are, which is why it cannot lose that information.

reHeritage GmbH, a company registered in Berlin (HRB 254687 B). The Impressum carries the full company details, and the Privacy page states the data boundary in legal terms rather than product terms.

Individual use costs almost nothing to serve — the site is static pages and files, and the work happens on your machine, not ours. Revenue comes from organizations that adopt unPaper together and from customer-operated private deployments. There is no usage metering and no phone-home check; the licence is honored, not enforced by the software.

Whichever one you already have. unPaper produces a prompt you paste into ChatGPT, Claude, Gemini, Copilot, Mistral, a self-hosted open-weight model, or the assistant your employer approved. You never give unPaper an API key, because unPaper never calls a model. /leaderboard scores how well specific models follow the format if you want to pick between the ones available to you.

That is the case it was built for. The prompt carries a field-tested slide language, so the model is choosing from named layouts rather than inventing a design. We measured it: every model tested reaches for the layout catalogue in four or five briefs out of five, and the gap between cheap and frontier models was much smaller than we expected. /lab publishes the runs, including the ones that went against us.

One self-contained HTML file — a 16:9 deck at 1280×720 per slide, with its styles, page rules and fonts inside it. It is a strong starting deck you can present as-is when it fits the job, or convert and finish in PowerPoint with your own judgment. The file opens in any browser, presents full-screen and prints to PDF without needing unPaper or an internet connection.

Yes — that handoff is an intended workflow, not a fallback. /convert turns the HTML deck into a .pptx where text is real text in real text boxes, shapes are native movable shapes, and icons are vector objects, not a picture of a slide. Retype a heading, recolour a box, move a chart element and finish the deck in PowerPoint or Keynote. The conversion runs in your browser too.

Paste it into /render. It pulls the deck out of a messy reply, wraps a slides-only answer back in the correct shell, and gives you the finished file to preview, save or convert. This is a normal outcome, not a failure — some assistants cannot attach downloads at all.

/update opens your deck, lets you comment on the specific slides you want changed, and produces a short revision prompt for those slides only. The replacement is spliced back into your file locally, so the rest of the deck is untouched — and you are not paying for a whole deck to fix one number.

Yes. /brand turns your organization's visual language into a reusable local template, either from an existing deck of yours or from a brand brief, and saves it in your browser. Every prompt you build afterwards teaches your AI that format. It can also be exported as a .potx for PowerPoint.

Yes. You write the brief in whatever language you want the deck in, and your AI writes the slides in that language. The template is layout and typography, not text.

Yes, under a separate licence. Because there is no inference and no document processing to host, a private deployment is static files behind your own boundary — which is also why an air-gapped install is a normal configuration rather than a special edition. /for-institutions describes the scope.

Less than usual, and you should verify that rather than take our word for it. There is no account system, no document storage, no sub-processor handling your content and no model call. The templates load no external resources, so a deck opened on an isolated machine behaves identically. Open the network tab, build a deck, and watch what leaves — that check takes a reviewer about five minutes.

Yes. There is a command-line tool and an MCP server that expose the same building, checking and converting steps to an agent or a build pipeline. /agents is the human-readable entry point, and llms.txt is the machine one.

Nothing. The output is standard HTML and standard PowerPoint, both of which open without us, and the format is published at /spec with an open pattern library beside it. There is no hosted document to be stranded in and no proprietary file to convert out of. This is a deliberate structural choice, not a promise about our longevity.