Can you export a Gamma website to HTML?

No. Gamma has no HTML export for presentations or websites: its export menu produces PDF, PNG and PowerPoint files (plus a Google Slides option and posting to LinkedIn), and its API offers PDF, PNG and PowerPoint. You can put a Gamma site on your own domain from the Pro plan up, but Gamma still hosts it, so running the site on your own server means capturing the published pages as static HTML or rebuilding them in another tool.

Gamma presentations and Gamma sites are different things

Everything you make in Gamma starts as a "gamma": a deck, a document or a site. Gamma's site guide defines a site as "a published version of a gamma doc or deck" that lives on a gamma.site subdomain or on a custom domain you own. You get one in two ways: open a deck and choose Publish to Site → Convert to Site, or start from the Sites tab on the dashboard.

The difference matters for exporting:

• Presentations and docs have a share link, Present Mode and speaker notes. Gamma's embedding article says they can be embedded in another website with an iframe, on every plan.
• Sites get a navigation bar, multiple pages with their own URL paths, a title and description per page, a favicon and a Google Tag Manager field. The same embedding article says sites "cannot be embedded into other websites."
• Conversion is one-way. Gamma's article on reverting a site says turning a deck into a site removes speaker notes and presenter view, and it can't be undone. The workaround is copying the slides into a new presentation by hand.

Gamma hosts every site ("No, Gamma handles all hosting," says Gamma's site guide), and sites don't support e-commerce or blogging.

What Gamma can export, and what it can't

Gamma's export guide applies to docs, decks and sites alike. Open Share → Export, pick a format, and choose all cards or only the current one. Exports follow Present Mode, not the editing view. The full set, as of October 2026:

Export format	What you get	Good for
PDF	A static file with the theme fonts embedded. Form fields and interactive elements are left out.	Sending, printing, keeping a record of the site
PNG	Flat images of your cards, page backgrounds included	Social posts, thumbnails, mockups
PowerPoint (PPTX)	Slides with editable tables, speaker notes and embedded theme fonts. The slide master comes out blank.	Presenting offline, editing in PowerPoint
Google Slides	Listed as an export on Gamma's pricing page; the export guide's route is uploading the PPTX, where Google Slides substitutes its own fonts	Teams working in Google Workspace
LinkedIn	A post on your personal profile (company pages aren't supported)	Sharing a deck
API export	PDF, PNG or PPTX from POST /v1.0/gammas/{gammaId}/export; API keys come with Pro and above, and Gamma's MCP server exports the same formats on every plan	Automating exports
Word (.docx)	Not supported on any plan	Nothing
HTML or a site bundle	Not offered in the app or the API	Nothing

Some styling can change on the way out: gradient headings can flatten to one color, and frosted backgrounds may fall back to simpler styles. Very long gammas, typically 150 slides or more, can fail to export, per Gamma's troubleshooting article.

The Free plan can export too: Gamma's pricing page lists "Export to PDF, PPTX, PNG & Google Slides" under Free. Its plan guide lists "unlimited exports" among paid features without naming a Free limit, and a Free workspace stamps a "Made by Gamma" badge on PDF and PPTX files. A paid plan (Plus, Pro or Ultra) removes the badge from later exports, not from files you already made.

Users have asked for HTML. A request on Gamma's feedback board titled "Export site or website to html, wordpress, squarespace, elementor, wix, figma, webflow etc)" had 213 votes on October 22, 2026; its author wanted the export "So we can put on our own servers." No HTML option has shipped.

Your own domain, still on Gamma's servers

If you want a branded address and don't mind Gamma running the site, connect a custom domain. Gamma's custom domain guide sets the rules, as of October 2026:

• You need a Pro plan or above, and the site must sit in your paid workspace.
• In Site settings → Publishing & domains, enter the domain under Connect an existing domain and choose Automatic or Manual setup. Buy new domain in the same panel registers one through IONOS (Gamma's domain purchase article) and connects it for you.
• Pro and Team workspaces can connect 10 domains; Ultra, Business and Enterprise can connect 100. Subdomains and failed or pending domains count toward the limit.

For Manual setup, Gamma gives these DNS records:

Record	Name	Value
A	@	3.136.232.26
A	@	3.137.108.170
CNAME	www	sites.gamma.app
CNAME (subdomain setup only)	the subdomain, e.g. site	sites.gamma.app

Both A records are required, and any other A or AAAA records on @ or www, such as ones left from a previous host, have to be deleted or the domain may not verify. Leave MX and TXT records alone so email keeps working. A www-only domain isn't supported, and on Cloudflare the records have to be DNS only, not proxied. Verification usually takes minutes but can take up to 24 hours, and the SSL certificate can take up to 24 hours after that.

Per Gamma's plan guide, Plus removes the "Made with Gamma" badge from shared and exported content. Pro adds custom domains (up to 10 multi-page sites), plus password protection and detailed analytics, though neither reaches a published site: Gamma sites can't be password protected, and Gamma's analytics don't count site visits. Search indexing is Pro and up too: Gamma's indexing article says "Free and Plus users cannot have their Gamma sites indexed at this time," and new sites stay unindexed until you switch on Make discoverable on the web. As of October 2026, Business is $40 per member per month, billed annually, according to Gamma's Business article; individual plan prices are on Gamma's pricing page.

The domain is yours, but the hosting is rented. Gamma's downgrade article says that when you move to a lower plan, features it doesn't include stop at the end of the billing period. Your content is kept.

What a published Gamma site is made of

A copy can only keep what the page contains. The source of a published Gamma site, Gamma's own design-team page at design.gamma.site (checked October 22, 2026), shows how one is put together:

• The text is in the HTML. Headings and copy arrive server-rendered, so a capture gets real text.
• Styles and scripts come from Gamma. The stylesheets and JavaScript bundles load from assets.gammahosted.com.
• Images pass through Gamma's image service. Image URLs point at imgproxy.gamma.app, which resizes originals stored on cdn.gamma.app.
• Fonts load from Google Fonts and from Gamma. The theme's font stylesheet comes from assets.api.gamma.app.
• Embeds load from other services. That page has no embedded players (its SoundCloud mention is a plain link), but the videos and forms Gamma does embed come from providers such as YouTube and Typeform, covered below.

That means a static copy can hold the layout, text, images, links and each page's title and description. Parts that move or open on a click, such as transitions and Gamma's toggles, footnotes and nested slides, may still need Gamma's scripts. Embeds keep working only while the service behind them serves them.

What you give up by leaving Gamma

• Hosting, SSL and the domain connection. You'll need a new host and new DNS records.
• The editor and its AI. The Gamma agent, AI edits and your credits stay in Gamma. Changes you make in Gamma after the capture won't reach your copy, and edits to your HTML won't flow back.
• Gamma's built-in analytics, which don't count site visits. Gamma's analytics article says views on your published site "aren't included". If you track the site, that runs through a Google Tag Manager container in your own Google account, so keep using that container on the new pages.
• Not password protection. Gamma's password option (Pro and up) covers docs and decks only; its sharing guide says "Gamma sites cannot be password protected at this time." If the new copy needs a password, your static host has to provide it.
• Not your forms or videos. Gamma has no native forms: its form guide covers embeds from Google Forms, Tally, Typeform and Jotform, with responses saved at the provider. Videos mostly work the same way: Gamma embeds them from YouTube, Vimeo, Loom, Wistia or TikTok and doesn't host video files uploaded from a computer. The exception is a video added from a phone's camera roll in the Gamma mobile app, which Gamma hosts itself, so check that it plays in your copy. Embeds like these can move with the page.

Route 1: capture the published site as static HTML

This keeps the design you already have.

1. Publish every page you want. A capture only sees public pages, so unpublished pages and private decks are out of reach. If all you have is a deck, keep a copy as a presentation before converting it, because the conversion is permanent.
2. Open the site while signed out, on its gamma.site address or your custom domain, and list every page. The navigation holds at most five links and two buttons, so check the Pages panel in the editor for pages it doesn't show.
3. Capture it. For one or two pages, you can save each page from your browser. For a multi-page site, FNJ's Gamma to HTML converter captures the public published pages as static HTML.
4. Check the copy before trusting it. Search the files for noindex: Gamma's indexing article says pages on plans below Pro show as "Excluded by 'noindex' tag," and a capture copies that tag. Click every toggle, footnote, nested slide, embed and button. Compare phone and desktop widths with the live site. Look for links that still point at gamma.site.
5. Host it and reconnect services. Upload the files to any static host. Search the files for your GTM- container ID and add the Google Tag Manager snippet only where it's missing, so visits aren't counted twice. Send a test entry through each form.
6. Move the domain. Remove it in Gamma's Publishing & domains panel (if Remove is greyed out, make the gamma.site address your preferred domain first). At your DNS host, delete Gamma's records (the two A records and the www CNAME, or the single CNAME for a subdomain) and add your new host's records. DNS changes can take up to 24 hours to reach everyone. Gamma notes that it "can't change or release your DNS records." If any URL path changes, add redirects; the redirect map guide shows how.
7. Turn off the Gamma site last. When the new version passes your checks, switch Site Enabled off in Site settings. Gamma's publishing article says this removes public access without deleting your content.

FNJ's Gamma to HTML export guide repeats the embed and transition checks and adds the deployment and redirect steps.

Route 2: rebuild the site in another tool

Rebuild instead of capturing when:

• you'll edit the site often and don't want to maintain captured markup;
• you need what Gamma sites don't offer, like a blog or a store;
• too much of the captured page depends on Gamma's scripts.

Gamma sites are simple structures: card-based pages under a navigation bar capped at five links and two buttons, per Gamma's site setup article. That makes the rebuild mostly a content move. Export a PDF to use as a visual reference, copy the text from the editor, save the images from the published pages, and recreate the layout in the builder or framework you plan to keep. Each page's title, description and URL path sit in Gamma's page settings; reuse them so search engines find the same pages at the same addresses.

Which route fits

• A branded address, and Gamma hosting is fine: stay on Gamma with Pro or above and connect your domain.
• The current design on your own host, with few changes planned: capture the published pages and fix whatever the checks turn up.
• A site you'll keep growing: rebuild it and treat the Gamma site as the spec.
• A file rather than a website: export PDF or PowerPoint.

If you take the capture route, FNJ's Gamma converter turns the public pages into static HTML (Next.js output for Gamma is still in development). Download the files, push them to your own GitHub repository, or deploy them to your own Cloudflare Pages or Vercel account; FNJ doesn't host sites. Forms, logins and other hosted services aren't captured, and converting needs a paid plan (pricing).

Frequently asked questions

Can I export a Gamma website as HTML?

No. Gamma exports PDF, PNG, PowerPoint and Google Slides, and its API exports PDF, PNG and PowerPoint. For HTML, capture the published site's public pages or rebuild the site elsewhere.

Can I host a Gamma site on my own domain?

Yes, on a Pro plan or above. Connect the domain under Site settings → Publishing & domains, or buy one there through IONOS. Gamma still hosts the site; your domain points at Gamma's servers through two A records and a www CNAME to sites.gamma.app, or a single CNAME if you use a subdomain.

How do I remove the "Made with Gamma" badge?

Subscribe to a paid plan: Plus, Pro or Ultra. Gamma's plan guide says Plus removes the badge from shared and exported content. Files you exported on the Free plan keep it, and printing from your browser while signed in never adds it. If a shared link still shows the badge after you upgrade, Gamma's sharing guide says to turn on Hide 'Made by Gamma' under Share → Advanced Settings.

Can I embed a Gamma site in another website?

No. Gamma says sites can't be embedded into other websites. Gamma docs and presentations can be, using the iframe code from Share → Embed, on every plan.

Why isn't my Gamma site showing up on Google?

Google indexing only works on Pro, Ultra and Business plans, and new sites stay unindexed until you turn on Make discoverable on the web and publish again. Below Pro, pages carry a noindex tag. Even with indexing on, Gamma says pages can take several days to appear.

Can I turn a Gamma presentation into a website?

Yes. Open the deck, choose Publish to Site → Convert to Site, then publish. The change is permanent and removes speaker notes and presenter view, so keep a copy as a presentation if you still need to present it.