An AI slides generator
that looks at the slides before handing them over.
Most AI deck tools compose in their own viewer and translate on the way out. That translation is where the fonts change, the text overflows its box and the chart labels land on top of each other — and you find out in PowerPoint, not in the tool. Orkas writes native PowerPoint objects from the first slide, then renders every page and reads the picture rather than trusting the code.
Four passes, and the last one is the one most tools skip
Decide the route
Build a new deck, or edit one you already have. Orkas also settles what the deck rests on — a topic, an outline, your documents, a dataset, or an existing file.
Plan the deck, not just the text
Outline first, then an art direction led by the audience and the content. Hand it a reference deck and it follows the traits you mark keep or adapt instead of inventing its own.
Write native PowerPoint objects
Text runs, shapes, tables and charts, built as the real thing rather than composed elsewhere and converted. There is no export step to lose anything in.
Render it, then look at it
Every slide is validated and rendered to an image, and the image is what gets reviewed. Invalid structure is a blocker, not a warning, and a repair is only claimed when the rerender proves it.
The checklist runs against the render, not the intent
Each slide is marked PASS, WARNING or BLOCKER with a concrete observation from the current render. A tool returning success is not accepted as evidence that a slide reads well.
Typography and wrapping
Type scale, line length, density and CJK rendering have to be legible at presentation size — the check that catches text spilling out of its box.
- overflow
- CJK
Chart labels, one per point
Every visible value label must map to one data point, appear exactly once, and not collide with another label, an axis or a series mark. Duplicated manual and native labels count as a defect even when the underlying numbers are right.
- charts
- collision
The deck as a sequence
A slide can be individually tidy while the deck still fails, because every page repeats the same card grid or the visual language drifts halfway through. That pass runs separately.
- rhythm
- consistency
What it will not claim
If rendering is unavailable, visual checks are marked not run — never inferred as a pass from valid structure. If an edit was supposed to fix a visible defect but the page renders identically, the finding stays open.
- not_run
- unresolved
Three things people actually hand it
A deck out of documents and data
Point it at reports, spreadsheets or a research folder. Facts you supply come back with a compact source ledger — units, periods, and what is estimated rather than measured.
- reports
- source ledger
A pitch deck from an outline
Give it the argument and the audience. Cover, opening, evidence, decision and close get designed for their roles instead of all landing as the same card grid.
- pitch
- narrative
Repairing a deck you already have
Edits in place and preserves the source rather than rebuilding it, then rerenders the changed slides plus the cover and anything sharing a theme or master.
- edit
- source-preserving
AI slides generator questions
Does it export to PowerPoint, or only to its own format?
There is no export step. Orkas writes a PPTX file directly, as native slide objects — text runs, shapes, tables and charts you can select and edit in PowerPoint, Keynote or Google Slides. Nothing is flattened to an image, and nothing gets translated out of a web viewer on the way, which is where most AI decks lose their fonts and layout.
What does “reviewed slide by slide” actually mean?
After every build or edit, Orkas validates the OpenXML and renders the slides to images, then reads the images. Each slide is marked PASS, WARNING or BLOCKER against reading order, composition, typography and wrapping, colour contrast, and whether a chart or diagram explains anything. Invalid structure is a blocker, not a warning. A tool reporting success is not accepted as evidence that a slide looks right.
Can it start from a deck or template I already have?
Yes, in both directions. Give it an existing deck and it edits in place, preserving the source rather than rebuilding it, and rerenders the changed slides plus anything sharing a theme or master. Give it a reference deck and it follows the traits you mark as keep or adapt instead of inventing its own art direction.
Do I need PowerPoint installed?
Not for Orkas to build and render the deck — it ships its own office engine and does that work locally. You will want PowerPoint, Keynote or Google Slides to present or keep editing the file afterwards, since it is an ordinary .pptx.
Is it free?
The app is free and open source under MIT. The model calls are not free for anyone, including us: connect your own OpenAI, Anthropic or Google account and you pay that provider directly at their rates, or use an optional Orkas-managed plan. Nothing about the deck itself is metered.
How long does a deck take?
Longer than a tool that fills a template, because rendering and reviewing every slide is work that a one-pass generator skips. It runs as a background task you can leave and come back to. If a defect cannot be repaired, it is reported as unresolved rather than quietly shipped.
Make a deck that opens correctly in PowerPoint
Free and open source, running on your machine, with optional managed models or your own provider keys.