Templates in.
Images out.
An open-source image API that runs on your own server. Send the data, get the picture.
Send JSON. Get an image.
Pick a city. The request changes, and so does the picture.
POST /api/v1/snaps
Authorization: Bearer YOUR_API_TOKEN
{
"template_id": "TEMPLATE_UUID",
"variants": [
{ "layer": "city", "text": "TokyoPeruNew YorkRomeParis" },
{ "layer": "photo",
"image_url": "https://example.com/tokyoperunyromeparis.jpg" }
]
}201 Created
"media_url": "https://snapsbrew.example/storage/snaps/9f1c2d3e.png"





The rendered image
Real renders of one template. Snapsbrew also makes the images of Legendsverse, Comicade and BYOMailer.
One template. A whole set of images.
Change the city and the photo. The design stays the same.
Render from your code, a URL, a form or an agent
Same templates, same layer keys. Pick the way that fits.
Call the API from your backend
For long jobs, add "async": true and a webhook URL.
curl https://snapsbrew.example/api/v1/snaps \
-H "Authorization: Bearer YOUR_API_TOKEN" \
-H "Content-Type: application/json" \
-d '{
"template_id": "TEMPLATE_UUID",
"variants": [
{"layer": "headline", "text": "Summer sale"}
]
}'Put a signed URL in your og:image tag
Your server signs the link. A page that nobody shares never renders an image.
<meta property="og:image"
content="https://snapsbrew.example/signed-url/image.jpg
?template_id=TEMPLATE_UUID
&variants=BASE64_VARIANTS
&signature=HMAC_SHA256">Let people make their own images
Embed a form for one template. Nobody writes code.
<iframe
src="https://snapsbrew.example/embedded-form/FORM_ID?signature=SIG"
width="100%" height="640"></iframe>Let your AI agent make the image
The agent lists your templates and previews the render. Then it makes the final image.
claude mcp add --transport http snapsbrew \
https://snapsbrew.example/mcp \
--header "Authorization: Bearer YOUR_API_TOKEN"Everything is in the open-source app
Every feature is in the code. Nothing is held back for a hosted version.
- Template editor
- Text, image, shape, SVG pattern and QR code layers.
- Batches
- Up to 100 renders in one request.
- Spreadsheet import
- One image for each row of a CSV or XLSX file.
- PDF output
- Certificates, invoices and tickets, ready to print.
- Screenshots
- Send a URL. Get an image of the page.
- Async and webhooks
- Long jobs go to the queue. A webhook says when they are done.
- Your fonts
- Upload your own fonts and use them in any template.
- Any HTTP client
- The SDKs are not ready yet. curl works today.
Self-hosted or hosted? The honest trade.
A hosted image API is a good choice when you do not want to run servers.
| Topic | Snapsbrew | Hosted image APIs |
|---|---|---|
| Where the renders run | On your server | On the servers of the vendor |
| Cost | Your server. No fee for each image | A monthly fee that grows with the number of images |
| Templates and images | In your database and on your disk | Stored by the vendor |
| Source code | Open. Read it, change it, audit it | Closed |
| Uptime and support | Your job. One maintainer answers issues | The vendor runs it, with a support team |
Up and running with Docker Compose
- 1Clone the repository.
- 2Copy .env.docker.example to .env and fill it in.
- 3Start the stack with Docker Compose.
- 4Open the setup URL from the log and create your account.
git clone https://github.com/amedina068/snapsbrew.git
cd snapsbrew
cp .env.docker.example .env # then fill in .env
docker compose up -d --build
docker compose logs web # shows the setup URLYour server. Your images.
Open source, on GitHub. Read the code, run it, change it.







