Credits
How render credits and AI credits work, what costs a credit and what is free, when credits reset, and what happens when you run out.
JamFrame counts what you use in credits. This page explains the two kinds, what uses them, when they come back, and how to see what you have left.
Two kinds of credits
- Render credits pay for the files JamFrame makes: images and PDF pages.
- AI credits pay for AI features, such as writing text, making pictures and designing with AI.
They are two separate pools. AI never uses render credits, and rendering never uses AI credits. Both belong to your organization, and all its workspaces share them.
What costs a render credit
| What you make | Render credits |
|---|---|
| One image (PNG, JPEG or WebP) | 1 |
| A carousel (a template with several pages, as images) | 1 per page |
| A PDF | 1 per page |
| Extra sizes with Smart Resize | 1 per page, for each size |
For example, a 5-page carousel in 3 sizes uses 15 credits.
It costs the same whichever way you render: a test render in the editor, the API, a dynamic URL, a form or a workflow. JamFrame charges only after the file is made.
What is free
- Failed renders. If a render fails, nothing is charged. The Renders page says “No credits were charged for this render.”
- Repeats on links. When a dynamic URL or signed URL is asked for the same image again within its cache time, JamFrame sends the stored image for free.
- Repeats on forms. The same answers on the same form within an hour get the earlier file for free.
- Working in the editor. What you see on the canvas while you design is free. A Test render does use credits.
- Reading. Listing and opening templates and renders, checking a render job, and setting up webhooks and receiving their events.
Credits pay for making a file, not for keeping it, so deleting a file doesn’t give credits back.
When credits reset
Credits are counted per billing period. At the start of each period your count goes back to 0. Credits you didn’t use don’t carry over.
- Free plan: every month, on the day of the month your organization was created. For most people that is the day they signed up.
- Paid plans: on each renewal date. With yearly billing you get the whole year’s credits at the start, and they reset once a year.
AI credits reset at the same time as render credits. The Resets date on the Renders page shows when your next period starts.
See what you have left
- Sidebar. The card at the bottom shows your plan, and how many render credits you used out of your plan’s total this month. Owners and admins can click it to open Billing.
- Renders page. The top shows Credits this period, Remaining, This workspace (what the current workspace used) and Resets.
- AI credits. AI dialogs and the editor’s AI panel show how many AI credits are left this period. Owners and admins see both pools on the Billing page.
Credits per plan
| Plan | Render credits | AI credits |
|---|---|---|
| Free | 100 a month | 50 a month |
| Starter | 1,200 a month, or 12,000 a year with yearly billing | 500 a month, or 6,000 a year with yearly billing |
| Plus | 10,000 a month, or 100,000 a year with yearly billing | 2,000 a month, or 24,000 a year with yearly billing |
| Professional | 30,000 a month, or 300,000 a year with yearly billing | 5,000 a month, or 60,000 a year with yearly billing |
See pricing for everything else each plan includes.
Limit one workspace
Owners and admins can cap how many render credits one workspace may use in each billing period, so one team or client can’t use up everyone’s credits. See Cap a workspace’s render credits.
When you run out
JamFrame checks your credits before it renders. A render you can’t pay for is refused, and nothing is charged.
| Where | What you see |
|---|---|
| Test render in the editor | “Out of render credits.” with the details |
| API | 402 QUOTA_EXCEEDED. detail.periodEnd says when your credits reset. |
| A workspace that reached its cap | 402 WORKSPACE_QUOTA_EXCEEDED in the API, and “Out of render credits.” in a test render |
| Dynamic URLs, signed URLs and forms | 402 CREDITS_EXHAUSTED. Visitors see that the image can’t be made right now, without any details about your plan. |
| Workflows | The run stops, and the rows that are left are skipped. |
| AI features | 402 AI_CREDITS_EXCEEDED, or “Your AI credits for this period are used up.” in the app |
402 PLAN_LIMIT_EXCEEDED is a different thing: it means you reached another limit of your plan, such as the
number of workspaces, seats, forms or workflow runs. It has nothing to do with credits.
What AI features cost
| AI feature | AI credits |
|---|---|
| Text that AI writes for a layer, in a render or with Preview in the editor (AI layers) | 1 per 500 words written |
| Translating a render’s text | 1 per 500 words written |
| ✨ Build with AI for a workflow | 1 per 500 words written (usually 1) |
| Design with AI: each request to the AI designer | 5 |
| An AI picture: Generate image, Edit with AI, or an AI image layer | 4 per picture at Standard (1K), 8 at Large (2K) |
| Remove background | 1 per image (4 when an AI image model does the cut-out) |
- Every use costs at least one block. For example, a 20-word headline costs 1 credit, and 501 words cost 2.
- If an AI call fails, its AI credits are given back. A render that fails charges no AI credits either.
- When a render reuses an AI result JamFrame already made for the same prompt, that result costs nothing.
- Dynamic URLs, signed URLs and forms never run AI. They show the layer’s saved text or picture, so they never use AI credits.
For the AI picture tools, see AI images.
Related
Last updated
Still stuck?
Email [email protected] and a real person will reply. Tell us the template you were using and what you expected to happen.