Stripe Climate Partner
1% of your Bannerbear purchase will contribute to removing CO₂ from the atmosphere
Start a free trial with 30 API Credits — no credit card required
1% of your Bannerbear purchase will contribute to removing CO₂ from the atmosphere
Browse the help docs or get in touch with our customer support team anytime
How credits are counted, and what a trial account can do.
The unit everything is billed in. One image render is one credit; heavier work costs more. Credits come out of a single allowance shared by images, animations, tools and workflows.
One, multiplied by the number of formats you ask for and by the scale. A jpg at scale 1 is one credit; jpg and png at scale 2 is four.
Yes, one credit each, per layer that uses them — face or subject detection, background removal, and AI background generation. They are added to the render’s own cost.
Because the AI features are charged per layer that actually uses them on that request. A request that supplies an image to a background-removal layer costs one more than the same request without it.
Two per second of output, rounded up to the next whole second, with a minimum of one. A 4.2 second animation costs 10.
Yes. Rendering at 60fps doubles the cost. 24 and 30fps are charged the same as each other.
You are refunded for the portion that had not started rendering, not the whole job.
Between one and four, depending on how much work it does. Trimming a video, adding cover art and building a PDF are one. Adding audio, removing a background and generating a voiceover are two. Most video operations — resize, crop, join, overlay, colour filter, soften, slideshow, GIF preview — are three. Burning subtitles is four, because it transcribes the audio as well as re-encoding.
Because of what they have to do to the file. Adding cover art writes a thumbnail without touching the video. Joining clips re-encodes every frame of every input. Subtitling does that and transcribes the audio first.
As the sum of its steps. A workflow is not charged for itself — each render and each tool inside it costs what it would cost on its own.
One credit per run. It is charged whether or not you keep the result, because the work has been done — though the version saved beforehand lets you undo it.
Renders are charged when they are created, so a failure after that point has already been counted. Cancelling an animation refunds the part that had not rendered.
Requests are refused with a message saying how many credits the request needed and how many remain, rather than running and billing you into a negative balance.
Everything, at a smaller scale: one workspace, three image templates, three animation templates, three workflows and three instant URLs. The APIs, tools and integrations all work as they do on a paid plan.
Yes. They are enforced the same way whether you are clicking in the dashboard or calling the API, so an integration cannot quietly exceed them.
Yes, so you can generate real output while evaluating. Credits are counted the same way as on a paid plan.
To keep projects or clients apart. API keys are scoped to a workspace, so a separate workspace is how you isolate a set of templates from another integration’s key.
The usage view in the dashboard shows credits consumed, and the logs show every request with the credits it cost, so an unexpected total can be traced to the requests that caused it.