Image Generation API
Generate template-based images for social media, ecommerce and more via API or AI tools
fetch('https://api.bannerbear.com/v5/images', {
method: 'POST',
headers: { 'Authorization': `Bearer ${API_KEY}` },
body: IMAGE_DATA
})
Generate template-based images for social media, ecommerce and more via API or AI tools
fetch('https://api.bannerbear.com/v5/images', {
method: 'POST',
headers: { 'Authorization': `Bearer ${API_KEY}` },
body: IMAGE_DATA
})Fill a template with your own data and get back a finished image in seconds. One design, any format, rendered on demand at whatever volume you need.
Fully documented API with OpenAPI specs. Everything you or your coding agent needs to get up and running fast.
Add template-based image and video generation capability to your Node app. Copy and paste your API key from the dashboard.
Grab an API key from the dashboard and add template-based image and video generation capability to your Python app.
Ruby, PHP, MCP hosted and local. There are many more ways to integrate your tech stack with Bannerbear.
12 month trailing 99.9% uptime. 6 years providing image and video API services. Check our current status.
Return jpg, png, pdf, webp and avif from a single render by asking for them together.
Multiply output dimensions for retina and print without maintaining a second copy of the template.
Pin a request to a saved template version so redesigning it never changes what production returns.
Render without a background, with the alpha channel carried through to PNG and WebP files.
Crop around the clearest face, the largest, or the whole group instead of the centre.
Cut the subject out of an uploaded photo during the render, with no preprocessing step needed.
Submit up to one hundred image requests in a single call and collect them as one batch.
Swap the base host for sync.api.bannerbear.com and the request waits for the finished image, up to ten seconds.
Generating images from templates.
POST to the images endpoint with a template UID and a modifications array. Each modification names a layer and the properties you want to change on it. Everything you do not name keeps its designed value.
On the template’s page in the dashboard, and in the API console on that page, which shows a ready-made request for that exact template.
jpg, png, pdf, webp and avif. Pass formats as an array to get several at once from a single render. It defaults to jpg.
Yes. Credits are counted per format, so asking for jpg and png costs two rather than one.
Yes, by enabling transparency on the template. PNG and WebP carry an alpha channel; JPG does not, so a transparent render must be requested in a format that supports it.
Use scale to multiply the output size. A scale of 2 on a 1200x630 template returns 2400x1260. Credits are multiplied by the scale as well.
Yes. dpi writes DPI metadata into the output so print software interprets the physical size correctly. It does not change the pixel dimensions — use scale for that.
Yes, quality sets the compression level for JPG and WebP output.
Yes. Pass the URL as the image_url of an image layer. If the source is large or slow, proxy fetches and resizes it before rendering.
Turn on AI detect for an image layer and the subject is centred automatically rather than cropped from the middle. Choose whether it focuses on the clearest face, the largest, or the group.
Yes, one credit per layer that uses it, on top of the render itself.
Yes, enable background removal on the image layer and the subject is cut out at render time. It costs one credit per layer.
Yes. A layer with AI background generation enabled will create one from the ai_prompt you send with the request. One credit per generated background.
Yes. Pass version to render against a specific saved version of the template, so a design change does not alter what an existing integration produces.
Yes. metadata accepts an arbitrary string that is stored with the image and returned with it — useful for carrying your own record ID through the request.
It depends on the layer’s text fitting setting: it can shrink to fit, or overflow. Set this in the editor so long values behave predictably before you send them.
As many as the template has. Send one entry per layer you want to change, and omit the rest.
Yes. Each request is a fresh render and is billed as one. If you need the same output again, store and reuse the URL you already have.
Start a free trial with 30 API credits, no credit card required
