Discover public pages from site links and the sitemap.
Example: https://your-site.gamma.site
External Gamma scripts may still be needed for interactions. Next.js export is in development; HTML is available now.
What a Gamma HTML export includes
Paste a published Gamma site URL to capture the pages visitors can see. FNJ saves the returned markup and accessible assets as editable static files. It does not open your Gamma workspace or export private decks.
How to convert a Gamma site to HTML
- 01 / Paste a public URL
Use a published Gamma page you own or are allowed to convert. A private project link cannot be captured.
- 02 / Choose the scope
Capture one page, or discover linked public pages and pages exposed in the site's sitemap. Review the capture report for omissions.
- 03 / Preview and export
Check the HTML preview, then edit, download or deploy the captured files according to your FNJ access.
What FNJ captures
FNJ saves public page markup and accessible styles, images and other assets. You can capture one page or let it discover linked public pages. Uncopied assets and external scripts may still load from the original service.
Before you publish
Use the public site address and inspect the result at desktop and phone widths. Slides, embeds and transitions can depend on Gamma scripts that remain on Gamma's servers, so test those interactions before moving the page to another host.
Gamma migration checks
A static export captures public pages, not the builder account or its hosted workflows. Check these before directing visitors to the new host:
- Use the published Gamma site URL, not a private presentation or workspace link.
- Open every embedded video or document in the exported preview and note any Gamma-hosted dependency.
- Compare transitions and mobile layouts with the live Gamma page before replacing it.
Keep your pages findable after the move
Keep important URLs and page titles where possible. If a path changes, redirect its old URL to the matching new page. Review canonical URLs and your sitemap on the final domain, then check indexing and crawl errors in Search Console. The export cannot guarantee that a search ranking will stay the same.
Follow the edit and deployment guide →Gamma to HTML: export and hosting FAQ
- Can I convert a private Gamma document?
- No. FNJ reads public pages from the URL you provide; it cannot access an unpublished document or your Gamma account.
- Will Gamma animations work offline?
- Some may still depend on external scripts. The HTML export is a page snapshot, so preview it and replace any interaction that does not work without Gamma.
- Can I export a Gamma presentation as a standalone website?
- This converter targets public Gamma website pages. A private deck, workspace document or presentation export is not the same input; slides and embedded controls may still rely on Gamma.
- Can I edit the Gamma HTML and CSS after downloading?
- Yes. The captured HTML, CSS and accessible assets are editable files. Work in your code editor or use supported FNJ MCP tools with a connected agent. The export is a snapshot; changes made later in Gamma do not automatically sync.
- Can I host the Gamma HTML export on Cloudflare?
- You can deploy the static files to your own Cloudflare account or another compatible static host. Preview every page and reconnect hosted forms, payments and other services first. A GitHub repository can hold the source files; pushing code is separate from configuring its hosting.
- Is the Gamma converter free or does it need an account?
- Converting requires a signed-in FNJ account and the access shown in current FNJ pricing. You can read this guide without signing in. Check the pricing page for current purchase terms; no builder subscription or private account access is used to fetch public pages.
Need the next step? Connect your agent through MCP, copy a site editing prompt, or check current FNJ pricing.
Where to take your Gamma HTML
Host your Gamma HTML export on Cloudflare
Deploy Gamma HTML to your own Cloudflare Pages account. Review the captured pages, upload assets, test dependencies and connect your domain.
Follow the workflow →Export your Gamma HTML code to GitHub
Put your Gamma HTML export in your own GitHub repository. Choose the right files, review the fnj-export branch and plan updates and hosting.
Follow the workflow →Make your Gamma export work for you
Practical guides for editing the captured HTML, reconnecting services and checking the result before launch.
Edit with MCP →
Connect an agent to FNJ MCP, inspect the correct route, change content and review the draft before publishing.
Reconnect forms →
Audit form actions, connect your own submission service and verify delivery, validation and error feedback after moving hosts.
CMS & content →
Separate captured article pages from the original CMS, inventory content and choose a tested publishing workflow for future updates.
URLs & SEO →
Map old and new routes, check canonical tags and metadata, test redirects and review indexability on the final domain.
Mobile layout →
Compare narrow and wide previews, fix overflow and navigation, and verify touch, keyboard and reduced-motion behavior.
Images & fonts →
Find failed asset requests, correct relative paths, inspect external dependencies and preserve typography on the new host.
Export troubleshooting →
Separate URL access errors, capture limits, missing content and deployment problems using a small reproducible conversion.
Explore related converters