| Generate from text | Control format, themes, images, headers/footers, and sharing. | Generate from text |
| Generate from a template | Adapt an existing Gamma — swap content, change the audience, transform the subject, or restructure cards. | Generate from template |
| Connect integrations | Use Gamma with AI assistants and automation platforms — some require no API key. | Connect integrations |
| Set up the MCP server | Let AI tools create new gammas and read existing ones via OAuth. | Set up the MCP server |
Settings > API Keys
Settings > Billing
Copy the theme ID from the app
Copy the folder ID from the app
Copy the template Gamma ID from the app before you make the request.
Create from Template works best when the source Gamma has exactly one page.
Copy the theme ID from the app
Copy the folder ID from the app
` | HTML tags — use the raw URL instead |
| `` | Already-wrapped markdown is skipped by the preprocessor |
### Placement in your input
Image URLs can appear **inline with your text or on their own line** — both work. Gamma scans for any whitespace-separated URL matching the requirements above.
{% code title="Inline with text" %}
```
"inputText": "Our headquarters https://cdn.example.com/office.jpg is located in San Francisco."
```
{% endcode %}
{% code title="On its own line" %}
```
"inputText": "Our headquarters\nhttps://cdn.example.com/office.jpg\nis located in San Francisco."
```
{% endcode %}
{% code title="Multiple images" %}
```
"inputText": "Product lineup:\nhttps://cdn.example.com/product-a.jpg\nhttps://cdn.example.com/product-b.png\nhttps://cdn.example.com/product-c.webp"
```
{% endcode %}
### Use `noImages` to prevent extra images
If you want **only** your provided images (no AI-generated or stock images added by Gamma), set `imageOptions.source` to `noImages`:
```json
{
"inputText": "...",
"textMode": "preserve",
"imageOptions": {
"source": "noImages"
}
}
```
Without this, Gamma may add additional images from the selected source alongside yours.
### Hosting recommendations
Since Gamma fetches and re-hosts your images during generation, the URLs only need to be accessible at generation time. However, using reliable hosting avoids intermittent failures.
| URL type | Recommended | Notes |
| ------------------------------------------- | ----------- | ------------------------------------------------------- |
| Public CDN (Cloudflare, CloudFront, Fastly) | ✅ Yes | Permanent, fast, reliable |
| Direct image hosting (Imgur, Unsplash) | ✅ Yes | Generally permanent |
| S3/GCS signed URL (7+ day expiry) | ✅ Yes | Works if expiration is long enough |
| S3/GCS signed URL (< 24 hours) | ❌ No | May expire before Gamma fetches it |
| Google Drive / Dropbox share links | ⚠️ Maybe | Can break if permissions change; not a direct image URL |
| URLs behind CDN hotlink protection | ❌ No | Gamma's servers will be blocked |
| Localhost / private network IPs | ❌ No | Not accessible to Gamma's servers |
{% hint style="success" %}
**Quick test:** Open your image URL in an incognito browser window. If you can see the image without logging in, Gamma can access it too.
{% endhint %}
### Troubleshooting
#### Images appear during generation but disappear on refresh
Your URLs were accessible when Gamma first rendered the content, but the re-hosting step failed — usually because of hotlink protection, rate limiting, or signed URLs that expired between the initial render and the background upload. Use permanent, publicly accessible URLs.
#### Images don't appear at all
Check that your URLs meet all three requirements (HTTPS, recognized extension, publicly accessible). Also check that you're not wrapping them in HTML `