Presentations as code
The deck is a set of files the agent writes and the browser compiles. You talk to it the way you talk to a coding agent. Word and PowerPoint are outputs for other people, not the source of truth.
Get started freeWhat “code” means here
- 01
Each slide is a file
Slide stores the deck as React/TSX plus metadata. Compile happens in the browser. There is no second engine hiding behind a .pptx.
- 02
Chat and Computer share those files
Text and images go through Chat. PDFs, spreadsheets, and PowerPoint go through Computer. Follow-ups stay on the same deck.
- 03
Export is a snapshot
PDF, PPTX, and PNG are downloads from the live preview. If you need Office tomorrow, export. If you need to change slide 4 tonight, chat.
Why this is closer to Claude Code than to PowerPoint
Coding agents already treat software as files you can read, patch, and run. Presentations were stuck as opaque Office blobs. Slide puts the deck on the same side of that line.
Edits are surgical
Change one slide without restyling the whole theme by accident, the way a code patch changes one function.
Tools can connect
Research, scrape, image search, and file parsers feed the same files. That is the “we connect the tools” part, not a Zapier directory.
You still leave with a PPT
The industry still emails .pptx. Slide does not pretend otherwise. It just refuses to make that file the place you think.
FAQ
Do I have to write code?
No. You write a brief. The agent writes the files. Developers who want to inspect them can; everyone else just chats.
Is this Gamma with extra steps?
Gamma authors cards in its own format. Slide authors slide code you compile and export. Different source of truth.
Why would Hebrew users care about “code”?
They might not search that word. They still get a מחולל מצגות that does not trap the deck inside an English-first canvas.
Author the deck as files, not as a blob
Sign up and describe what you need. The agent writes the slides.
Get started free