Gamma
Gamma API
MCP server
Checked on 2026-10-10 in the developer documentation.
How to use Gamma
This guide gets you from a blank Gamma account to producing on-brand decks, documents, and pitch pages fast, the kind of polished output that used to mean a designer and half a day in slide software. It is for founders, operators, and growth teams who write a lot, present a lot, and do not want to fight with layout. If you think in outlines and want the design handled for you, Gamma fits the way you already work.
Getting set up
The first decision that matters is your theme, because it sets the visual personality of everything you create afterwards. Build a custom theme that carries your brand: load your fonts, your colour palette, and your logo, and save it as the default. Do this once, properly, before you make a single deck, otherwise you will generate twenty decks in the stock theme and re-skin them by hand later. A theme in Gamma is reusable, so the upfront work pays back every time.
The second decision is your default generation settings. Gamma can turn a prompt or an outline into a full deck, and you control the density (how much text per card), the tone, the image style, and the format (presentation, document, or webpage). Pick sensible defaults that match how you actually present: most people over-stuff slides, so lean towards less text per card and more cards. If you present live, dense slides read as a script and lose the room.
Read the full guideShow less
Set up your workspace structure early. Decide whether you are working solo or with collaborators, and create a folder convention so decks do not pile into one undifferentiated list. If you are on a paid plan, your custom themes, fonts, and shared assets live at the workspace level, which is what makes Gamma worth standardising across a team rather than treating as a personal toy.
How to actually use it
The core workflow is outline first, generate second, refine third, and doing it in that order is what separates a clean result from a mess.
Start with the outline, not a one-line prompt. Gamma will happily expand "a pitch for my SaaS" into something generic, but if you feed it a structured outline (your actual sections, in your actual order), you get a deck shaped like your argument instead of a template. Write the outline the way you would brief a junior: section headings, the point each section makes, any specific numbers or claims. Then let Gamma generate the cards from that.
Once it generates, treat the output as a strong first draft, never the finished thing. Go card by card. Tighten the copy, because AI-generated slide text trends wordy and hedged. Swap any image that is decorative-but-meaningless for one that actually carries the point. Reorder cards by dragging them; Gamma keeps the layout intact when you move things, which is the whole reason it is faster than slide software.
Use the card-level editing rather than fighting the global layout. Each card has layout options (split, full-bleed, columns, embedded media), and choosing the right layout per card does more for the result than any amount of copy polishing. When a card feels flat, change its layout before you change its words.
Finish by choosing the right output surface. The same Gamma deck can present full-screen, export to PDF, or publish as a shareable web link. Decide this before you finalise, because a deck built to present live and a document built to be read alone want different densities of text.
Power moves
Build a reusable template deck for the things you make repeatedly (a sales pitch, a client kickoff, a monthly report) and duplicate it rather than generating fresh each time. Generation is great for net-new, but for recurring formats a locked template gives you consistency and speed that re-generating never will.
Lean on the embed and live-content features. Gamma can embed live media, links, and interactive content directly in a card, which turns a static slide into something closer to a microsite. For a sales or onboarding deck that lives as a web link, this is the difference between a PDF people skim once and a page they actually interact with.
Use analytics on published decks. When you share a deck as a link, Gamma can show you engagement, which slides people read, where they drop off. For anything you send to prospects or clients, that signal is worth more than the deck itself, because it tells you what to cut next time.
Write your prompts and outlines in your own voice and feed Gamma examples of your phrasing. The more you steer tone explicitly, the less it defaults to the flat, corporate register that gives AI-generated decks away. Treat the AI as a layout engine you are directing, not an author you are trusting.
Where it fits your stack
Gamma sits at the output end of your stack, where research and data become something a human looks at. It connects upstream to wherever your content lives: pull your structured notes or briefs out of your docs tool, shape them into an outline, and Gamma turns them into the visual artefact. It exports cleanly to PDF for anything that needs to travel as a file, and publishes to a web link for anything that should stay live.
For a growth team, the natural pattern is research and positioning happening in your writing and data tools, then Gamma producing the pitch, the one-pager, or the report at the end. It replaces the slow "now make it look good" step that usually bottlenecks on whoever owns the brand template. Keep the brand theme in Gamma as the single source of visual truth so every output lands on-brand without a manual pass.
Pitfalls to avoid
The biggest mistake is shipping the first generation. Gamma's output is good enough to look finished while still being generically worded, so people present a deck they never actually read. Always do the card-by-card pass.
The second is over-stuffing cards. Because generation fills space, decks drift towards dense, text-heavy slides that work as documents but die in a live presentation. Strip text out; add cards instead.
The third is skipping the theme and re-skinning by hand later. If you generate before your brand theme exists, you inherit the stock look and spend more time fixing it than the theme would have taken to build.
The fourth is treating Gamma as a full design tool. It is excellent at fast, on-brand, structured output, and it is not the place for pixel-precise custom layouts. Know which job you are doing, and do not fight the tool when the job is the other kind.
How to automate Gamma
API and webhooks
Gamma has a public API at developers.gamma.app, and it needs a Pro plan or higher. A practical use is generating a client deck from structured input: when a deal reaches proposal stage in HubSpot, send the deal notes to the API and attach the resulting link to the record.
MCP server
Gamma has an official hosted MCP server that uses OAuth. Access may need a request form. Connect it to an assistant such as Claude and ask it to turn a meeting summary or a document into a deck without leaving the chat.