You have a long document — a report, a brief, a project write-up — and you need it as a presentation someone can open in PowerPoint or WPS and actually edit. Not a PDF of pretty pages. An editable deck, with real text boxes, real fonts, real charts.
Here's the workflow that works, learned from a real project: a 15-page school science-fair report that became a 14-slide competition deck. The pitfalls at the end are the ones that actually bite.
Step 1 — Feed the source, say the goal
Upload the Word document (PDF, Markdown, and plain text all work — even screenshots of the original). Then say two things in one sentence each:
- Who it's for and where it's shown. "Judges at a school science fair, projected then possibly skimmed on a laptop" produces a different deck than "investors skimming on phones."
- What shape you want. "About 10 slides" or "keep it under 8" is enough — the agent picks the cuts. If you know you want an editable file rather than a polished-but-flat export, say so up front.
You can run this right now at Document to Slides — drop the file, describe the audience, get a watermarked preview free.
Step 2 — Read the preview like an editor, not a proofreader
The first pass is about structure, not polish. Check the spine: does the deck tell the same story as your document? Are the numbers on the right slides? Anything invented that shouldn't be there? Fix the outline in words — "move the cost comparison before the benefits," "slide 4 has too much, split it" — before touching fonts and colors.
Step 3 — Iterate in the workspace, not from scratch
The conversation stays open: every follow-up ("make the title shorter," "swap the diagram on slide 6 for a table") is an edit, not a regeneration. This is where having the agent inside a persistent workspace pays off — it remembers your files, your corrections, and the version it already produced.
Step 4 — Download the right kind of file
Two deliverables, different machinery:
- Rendered/polished PPTX — a flattened, presentation-ready file. Great when the deck is final and the only thing left is showing it.
- Editable PPTX — real text boxes and shapes a student or colleague can edit in PowerPoint or WPS. Ask for this when the deck still needs a human's last pass.
The pitfalls that actually break
- Blank images after download. If the deck references images by file path instead of embedding them, they render in preview and vanish in your downloads folder. A good pipeline embeds everything — verify by opening the downloaded file offline.
- Charts that only exist online. Interactive chart libraries draw to a live canvas — dead in preview clones and offline. For a projected or shared deck, charts should be pre-rendered images.
- Fonts that look right on your screen only. Editable decks opened in a different office suite reflow if glyphs measure differently. Robust builds stack text vertically rather than side-by-side at fixed offsets, and check every shape stays inside the slide bounds.
- "Editable" exports that aren't. Some export paths flatten everything into a single image per slide — looks identical, edits nothing. If you'll need to change text later, say "editable" explicitly and open the result in PowerPoint to confirm real text boxes.
One sentence for next time
Upload the document, name the audience and the slide count, say "editable," then read the preview for structure before polish — and always open the downloaded file before you call it done.
Try it free at Document to Slides — the preview is watermarked, the clean file is $2.99. Or keep going in the workspace, where the same agent remembers everything.