Office files belong in the safety net, not the workflow

Every time we tell someone Plain's primary output is a link, not a file, the next question is the same: "But what if the client needs a .pptx?"

Of course they sometimes do. We export to .pptx, .docx, and .xlsx with care. We test the round-trip on real fonts and real layouts. We accept the degradation losses that come with any format conversion. We're not pretending Office goes away.

We're saying it shouldn't be the default.

What "default" costs you

When the default is "send a file," every recipient interaction becomes a small drag:

• They download. (~10 seconds.)
• They open. Wait for the app to start. (~15 seconds.)
• They scroll. Sometimes the layout looks wrong on their machine.
• They want to forward. They re-attach the file to a new email.
• You make a change. You re-export. You re-send.
• Now two versions exist in their inbox. They may open the wrong one.

Each step is small. Together they add up to a workflow that's five times slower than it needs to be.

What "default" costs your AI

AI agents can't open files cleanly. Send a .pptx and ask "what's the deck about" — the agent has to parse binary, often loses layout context, sometimes gets text wrong. Send a link and the agent fetches the source. It sees structure. It can answer precisely.

If you want AI to be useful in the loop with your work, the artifact has to be in a form AI reads natively. That form is text or a web page, not a file.

The flip: link first, file when asked

In Plain, the default share button copies a URL. That's the artifact's primary identity. Anyone you send it to opens it in a browser. Updates are live. Comments are inline. Versions are tracked.

Then, in the menu, there's "Export." One click and you get a clean .pptx, .docx, or .xlsx. We've spent real engineering time on this export — the fonts survive, the tables are still tables, the charts are still editable. When you need to email a file, you have a good file to email.

The mental model: the link is the artifact, the file is a printable copy of the artifact.

The honesty about export degradation

We've been blunt with users about what doesn't survive export. Scroll-based motion in a deck becomes static slides. Embedded videos become links. Real-time collaboration goes offline. The source dashboard's SQL becomes a frozen data table.

These are real losses. They're acceptable losses, because the export's job is "get this in a format the receiver expects" — not "preserve every browser-native feature." The link still exists; it always has the full version.

This applies to more than Office

We think the same logic applies whenever you have a primary medium that's better than its fallback. Web pages are better than .pdf. Real markdown is better than a screenshot of markdown. Database queries are better than ranged screenshots from a dashboard.

In each case: build for the better medium, fall back gracefully when the situation demands. The fallback is a safety net, not a strategy.