Decks that make an argument.
The storyline is settled before a slide is opened, every title is a claim rather than a label, the charts come out of your own model, and the deck is rendered and inspected before you ever see it.
Free to download, free to present. AI features draw on your allowance.
- Builds from
- Your real numbersWorkbooks, PDFs, notes, brand kit
- Hands back
- .pptx · .pdf · linkWith speaker notes
- Building costs
- Nothing, everNo account needed to build
- Runs
- On your machineYour deck stays local
It settles the argument before it opens a slide
A deck fails in the outline, not the layout. The run locks what the room has to believe and gives every beat an action title — a claim someone could disagree with, not a one-word label.
- Audience, length and outcome settled up front
- One action title per beat
- The structure is visible before anything is composed
A theme built from your brand, not a template
Palette, type and spacing are committed to once and obeyed by every slide after it. Generated from your own brand kit, or pulled out of an image you like.
- Themes generated from a brand kit or an image
- Backgrounds and covers made, not stock
- The same system on all fourteen slides
Two covers, judged side by side
For the slides that carry the most weight, it builds genuinely different versions and looks at both before keeping one. Comparing beats iterating when the solution space is wide.
- Real alternatives, not one draft nudged twice
- Judged on rendered pixels
- The runner-up’s better ideas kept
Charts from the model, not from memory
Figures come out of your workbook. Diagrams stay editable. Images are generated or pulled from your library rather than dropped in as filler.
- Charts, tables and editable diagrams
- Icons, graphics and generated imagery
- Live LumenApps embedded in a slide
Polish means rendering it and looking
Overlaps, clipped text, contrast failures and orphaned lines are found by rendering the slide and inspecting the pixels — not by reasoning about the markup that produced them.
- Overlap, spacing and hierarchy fixes
- Contrast checked, not assumed
- A whole-deck audit at the end
check_overlaps4 overlaps · 2 contrast failures · 1 orphaned lineWhat you actually say
Not a transcript of the slide. The notes carry the point of each slide, the number worth repeating, and how you get to the next one.
- Per-slide notes and transitions
- Presenter view with timing
- Export to PowerPoint or PDF
How LumenAgent works in here
Watch it build the deck — and stop to ask you.
A real run across all eight phases: it reads your library, locks the storyline, compares two covers with its own eyes, and waits for you before it clears a slide you made. Decline and it builds around them.
One app, every editor
A deck is the last step, not the only one.
LumenSlides is one editor inside LumenQube. The agent reads your whole library and hands real work to any other editor’s own agent, so the deck, the memo and the model all carry the same numbers.
Chart figures come out of the workbook rather than being retyped from a screenshot.
A 60-page PDF, read for the metrics and the commitments already made.
Storyline, theme, composed slides, rendered checks and speaker notes.
Backup figures built by LumenSheets, so the room can be shown the working.
The full toolkit
Everything LumenSlides does, and all of it free.
Six groups. No slide limits, no watermark, no upsell halfway through a deck.
Storyline
The part that decides whether it lands.
- Action titles — a claim per slide, not a label
- Beats — the argument, ordered, before any layout
- Length — held to the number you asked for
- Templates — start from a structure that fits
Design
One system, obeyed throughout.
- Themes — generated from your brand kit or an image
- Backgrounds & covers — made for this deck
- Brand templates — applied across every slide
- Type & palette — committed to once
Compose
Real slides, real content.
- Layout — composed, not poured into a placeholder
- Charts & tables — from your workbook
- Diagrams — editable, not flattened pictures
- Images, icons & graphics — generated or from your library
Judge
Options beat iterations.
- Explore — genuinely different versions of pivotal slides
- Compare — judged on rendered pixels, side by side
- Smart blocks — browse real composed options
- Keep the best — including ideas from the runner-up
Polish
It looks at what it made.
- Overlaps & clipping — found by rendering the slide
- Contrast — checked, not assumed
- Hierarchy & spacing — fixed after seeing it
- Whole-deck audit — as one artifact, at the end
Present & hand on
Out of the editor.
- Speaker notes — what you say, and the transitions
- Presenter view — with timing
- Export — .pptx and .pdf
- Delegate — an appendix workbook or a written version
LumenSlides · common questions
Does it just fill in a template?
No. It settles the storyline first, then generates a theme from your brand kit and composes each slide's layout for the content on it. Templates are available as a starting structure, but the deck is built rather than poured into placeholders.
Where do the chart numbers come from?
Your own workbook. The agent reads the spreadsheet directly rather than working from a screenshot or a figure quoted in the prompt, so the deck and the model cannot disagree.
Will it delete the slides I already made?
Not without asking. Clearing a deck pauses for approval — that is the gate in the demo above — and declining builds the new slides after yours instead.
Can I export to PowerPoint?
Yes — .pptx and .pdf, with the speaker notes attached.
What does it mean that it 'looks at' the slides?
The deeper engines render each slide and inspect the result, so overlaps, clipped text and contrast failures are caught in the pixels rather than reasoned about in the markup. That pass is what the Polish phase is.
Download
Walk in with the argument made.
One download, every editor, and an agent that asks before it clears anything.
Free to download, free to present. AI features draw on your allowance.