Gamma

Gamma is a visual communication platform for creating presentations, documents and other content with AI assistance. It combines conversation, structure and design to support the creation and revision of materials.

In brief

Documents and presentations

Official website

Contents
  1. What Gamma is and the problem it addresses
  2. Origins, company and development
  3. From source material to outlines and cards
  4. Presentations, documents and visual assets
  5. Exporting and output fidelity
  6. Websites and publishing
  7. Collaboration, permissions and analytics
  8. Integrations, API and generation capacity
  9. Plans, access and privacy
  10. Accessibility of the editor and finished material
  11. Documented abuse and link security
  12. Practical applications in OSH
  13. Worked example and result checks
  14. Limitations and conditions of use
  15. When to choose it and how to complement it
  16. Frequently asked questions
  17. Related profiles
  18. On the Sabentis blog
  19. Sources and documentation

Back to Tools

What Gamma is and the problem it addresses

Gamma is a visual communication platform for creating presentations, documents, websites and graphics. It combines AI-assisted generation and editing with tools for organisation and design. The approach starts with an idea, outline or existing material and turns it into a visual structure that can then be reviewed, presented, shared or exported.

Its characteristic unit is the card, which groups content into blocks. This encourages work on the sequence of ideas before the delivery format. The result may serve a meeting or independent reading, but these uses require different densities and explanations. A projected card must be understood quickly; a document read without a speaker needs sufficient context, definitions and accessible references. Deciding which experience matters most helps determine the format before a large amount of content is generated.

Reference documentation: Gamma product overview.

Origins, company and development

Grant Lee, Jon Noronha and James Fox started Gamma in 2020. The company aimed to simplify creating and communicating ideas through a visual format for the web. In Lee’s account published in November 2025, the team decided to refocus the product on AI in late 2022, rebuilding parts of its infrastructure and creation experience.

In November 2025 it announced a $68 million Series B round at a reported $2.1 billion valuation, led by Andreessen Horowitz. The investor’s announcement describes expansion beyond presentations into documents, websites and integration with other workflows. These are dated corporate milestones. To understand the tool itself, the more useful development is how generation, revision and distribution became parts of one process. This also explains why older descriptions of Gamma as a conventional slide editor omit a substantial part of its present scope.

Reference documentation: Gamma founders · How we built Gamma differently, November 2025 · Investing in Gamma, November 2025.

From source material to outlines and cards

Work can start by generating from instructions, pasting text, importing material or building manually. The assistant proposes a structure and supports conversational revision; the editor combines automatic layouts with freeform editing. Importing and rewriting are different operations: placing content should not be confused with authorising changes to its meaning.

A useful brief specifies the audience, purpose, source material and intended outcome. For example: explain three decisions from a report, retain the original figures and identify unresolved questions. Review the outline before developing every card. If a conclusion is missing, return to the source instead of filling the gap with a persuasive sentence. Manual editing is particularly important for headings, units, notes and exceptions that require precision. Keeping a source beside each key claim also makes subsequent revisions easier to check.

Reference documentation: Gamma — Create an ebook · Gamma product overview.

Presentations, documents and visual assets

Gamma distinguishes presentation format from Document format, which is intended for vertical reading. Guides can use chapters and a table of contents; page size can be fixed, such as A4, or fluid for screen reading. Social assets and other visual material are also supported. The same information can be adapted into several formats, although an entire report should not simply become a succession of crowded slides.

In a presentation, each card should support one step of the argument. In a guide, it should help readers locate and understand a question independently. In a carousel, the sequence should retain meaning even if a single piece is shared. These conditions determine text density, hierarchy, dimensions, sources and relationships between elements. An attractive template is a starting point for those decisions, rather than evidence that the communication is already suitable for its audience.

Reference documentation: Gamma — Create an ebook · Gamma API product.

Exporting and output fidelity

Outputs include PDF, PNG and PowerPoint, with a route into Google Slides. Current documentation states that tables can remain editable in PPTX. Exports reflect presentation view; fonts, effects and scaling can behave differently in the receiving application. The mobile application also supports exporting, although its options are not identical to those on the web.

For professional delivery, test a representative card before producing the complete set: a table, chart, image, note and corporate font. Open the result in its actual destination and inspect figures, breaks, margins and contrast. A web link preserves a different experience from a static PDF. If an explanation depends on video, interaction or external content, provide an understandable alternative for someone receiving only the file. Record which exported version was reviewed so later edits are not mistaken for the approved deliverable.

Reference documentation: Exporting a Gamma · Gamma — Export differences.

Websites and publishing

The website builder supports multiple pages, navigation and editing of page titles, descriptions and paths. Compatible plans allow a custom domain. Saving an edit and publishing it are separate steps: content or navigation changes must be published before they appear in the visible version.

This can suit microsites, informational resources and campaign pages with a bounded structure. Before choosing it for a larger project, test navigation and integration requirements. The documentation reviewed lists specific limitations, including the absence of native dropdown menus. A page should make its owner, review date and link destinations clear. A title and description help identify it, while its practical value depends on answering the visitor’s question. For a resource collection, test whether someone unfamiliar with the material can find the relevant item without help.

Reference documentation: Gamma site setup.

Collaboration, permissions and analytics

Gamma distinguishes viewing, commenting and editing permissions. Workspace settings can override document settings; password protection available for documents does not automatically apply to a published website. Checking access through an account representative of the recipient is a practical way to establish what has actually been shared.

Analytics provides views and card-level activity on suitable plans. However, an anonymous view may come from an automated link preview, and published website traffic is measured separately. These data can help explore how material is consulted, but should not serve as attendance records or evidence of comprehension. If a card receives little attention, investigate its position, clarity and relevance before attributing the pattern to audience disinterest. A short discussion or task-based question provides different evidence from an open browser tab.

Reference documentation: Gamma sharing and collaboration · Gamma analytics.

Integrations, API and generation capacity

Gamma offers connectors for retrieving content and integrations for creating from other environments. Its developer documentation distinguishes the REST API from the MCP server, with generation, reading, editing and export operations. It also supports generating variants from an approved template, retaining a common starting point.

Tokens describe how much text can be processed in a generation; credits represent consumption of AI capabilities. These are different limits. An automated workflow should record the source used, the template version and the output requiring review. A monthly report, for example, can reuse structure and branding while changing its period and figures. Checks should detect missing data or mixed reporting periods before design turns them into a seemingly coherent narrative. Repeated production is most useful when the repeated checks are as clearly defined as the repeated layout.

Reference documentation: Gamma developer documentation · Gamma integrations · Gamma tokens.

Plans, access and privacy

As of 8 November 2026, the individual offering includes Free, Plus, Pro and Ultra. Differences concern AI use, branding, customisation, analytics and domains, among other features. Organisational workspace terms need separate examination. Cost evaluation should cover the complete cycle of generation, correction, export and maintenance, as well as the initial draft.

Content is stored in the cloud, including material supplied through connectors. Current help states that individual workspaces allow data to train AI features by default, with an opt-out; the organisational workspaces identified in the documentation are excluded. Before uploading workplace material, check the workspace type and effective controls. An aggregate presentation can communicate trends without names, identifiable photographs or details from individual case records. Choosing the information needed for the communication is therefore part of preparing the source material, before generation starts.

Reference documentation: Gamma pricing · Gamma AI training controls · Gamma data and privacy.

Accessibility of the editor and finished material

Gamma’s accessibility statement, updated in March 2026, describes contrast adjustments and content reflow in standard cards. It also lists editable alternative text carried into outputs, tagged PDF and aspects of accessible PPTX export as improvements still being explored. A readable-looking editor is therefore insufficient evidence that every deliverable is accessible.

The final format determines the checks required. Review reading order, size, contrast, chart comprehension and alternatives to images or audio. For a guide intended for people with different access needs, prepare a sample and check the experience with representative technologies and devices. If the format does not retain the required structure, the document may need finishing in another tool before distribution. This decision should be made on the sample, before investing in a long guide that will require extensive repair.

Reference documentation: Gamma accessibility statement, March 2026.

Documented abuse and link security

In April 2025, Abnormal researchers published a phishing case that used content hosted on Gamma as an intermediate step towards a fake Microsoft sign-in page. The attack exploited links and the appearance of shared documents. The report describes abuse of hosting and trust in links; it does not establish that Gamma’s infrastructure had been compromised.

The practical lesson is to distinguish the service hosting a page from the destination of its buttons. A familiar brand or professional design does not authenticate a request for credentials. Corporate material should identify access links clearly and avoid ambiguous messages such as “secure document” without explaining their origin. If a recipient needs to sign in, they should be able to recognise the expected service and verify the address through a known channel. This makes legitimate communications easier to distinguish from imitations.

Reference documentation: Abnormal: multi-stage phishing using Gamma, April 2025.

Practical applications in OSH

Its potential occupational safety and health application is preparing visual drafts from approved safety information. It can help structure a briefing, present review findings or turn a long document into a sequence of messages for a particular audience. The underlying technical decisions and evidence must still come from the responsible team.

A team can use it to structure an explanatory report, prepare an awareness session or turn reviewed conclusions into a sequence for discussion. Separate data, interpretation and proposed decisions. This prevents generated wording from turning an association between indicators into a demonstrated cause.

In OSH, a useful card answers a specific question and lets readers return to the source. Figures without a period, population or definition can produce misleading conclusions despite an attractive chart. Keep methodological notes close to the figures they qualify.

Worked example and result checks

Example: draft a presentation for the safety and health committee using indicators that have already been calculated and conclusions that have been reviewed. The owner confirms each figure, adds sources and decides which explanations the audience needs.

  1. Gather a validated table with indicator definitions, period and source. Exclude individual information that is unnecessary.
  2. Write down the decision to be discussed and remaining uncertainties first. Request a structure that preserves these limits without adding figures or causal claims.
  3. Review each card against the input material. Check numbers, units, denominators and chart labels.
  4. Separate facts and proposals through clear headings. Add the questions requiring a committee decision.
  5. Export to the actual meeting format and inspect page breaks, sizing and notes. Open it on the device or application that will be used.

This is an illustrative workflow. A finished presentation is not the meeting minutes and does not prove that its measures have been approved.

Limitations and conditions of use

AI may fill gaps with statements or charts absent from the original material. Check data, denominators, references and conclusions, and review the readability of exported files. A persuasive presentation is not a risk assessment or evidence of improved safety outcomes.

Generation or rewriting can oversimplify an exception. When wording must remain exact, check that it has not changed. Embedded elements also need testing: something interactive in a web link may become static in an export. Do not make a conclusion depend on content the recipient cannot open.

Keep a source-to-card checklist when several contributors supply material. It helps identify which figures need updating and prevents an older number surviving on an introductory card.

Reference documentation: Gamma — Create an ebook · Gamma — Export differences.

When to choose it and how to complement it

Gamma fits rapid construction and reorganisation of a visual narrative from verified material. Power BI may provide an analysis, but its filters and reporting period must remain visible in the presentation. Check PowerPoint as a destination when local editing or an existing corporate template is required.

Test a difficult card containing a table and methodological note before converting the entire document. Include the person responsible for the final presentation in that check.

Frequently asked questions

Does Gamma automatically verify report data?

Do not assume so. Verification requires comparison with controlled sources and calculations.

Why can an exported PowerPoint look different?

The destination format and fonts can introduce changes. Inspect the final file rather than only the editor.

Can it produce a guide read without a presenter?

It can structure one, but the guide needs sufficient context, definitions and references to be understood without oral explanation.

Request a Demo

Discover all that Sabentis can do for your organization.

Try Sabentis

request a demo
stars 5
GetApp Software Advice Capterra