Limits
View as MarkdownThe hard limits of Blitframe, grouped by what they apply to. Your plan can set lower limits on render length and size, and on how large a project can be (plan limits). Need more? Contact us.
Compositions
| Limit | Value |
|---|---|
| Size | 1 to 16384 pixels per side (16K), written as whole numbers such as 1920, not 1920.0. Your plan may allow less. |
| Duration | Up to 3,600 seconds. Your plan may allow less. |
| Frame rate | 1 to 120 fps |
data.json complexity |
5,000,000 JSON tokens (each key and value counts once, each object or array twice), nested at most 255 levels deep |
| Precompositions | 180 precomposition layers that are not collapsed per render, counting every use inside another precomposition again. At most 10,000 precomposition copies in all. |
| Video layers | 100 per render, counting hidden layers, layers outside their time and every copy of a precomposition. An animated GIF or WebP on a layer counts too. A composition with more is reported in the version's problems, and a render that needs more fails. |
| Textures | 484 per render, 482 on a plan with the watermark. The version's problems report a composition whose image assets and 3D models need more than 484. Each image asset id counts once, whether a layer shows it or not. GIF and WebP files don't count there, nor does an asset with a data: p or a w or h over 4096. Each 3D model a layer uses adds the textures its materials draw with, and any model adds 3 for 3D lighting. Animated GIF and WebP layers, video layers, precompositions that are not collapsed, some masked layers (adjustment layers, and image, solid, precomposition and video layers with static masks and no effects) and fonts take textures too. Those are not checked, and a render that needs more fails (what takes a texture). |
| Text layers and 3D models | 199 meshes per render: one for each text layer, two for a stroked one, and one for each 3D model asset a model layer uses, however many layers or copies show it. Hidden text layers and every copy of a precomposition count. A composition over it is reported in the version's problems. |
| Vector shapes | 2,000 paths per render: shape paths, masks, and fills cut by Trim Paths. Shape paths and masks count in hidden layers too, and fills cut by Trim Paths only on layers that show. Every copy of a precomposition counts (details). A version over it is reported in its problems, and a render that needs more fails. A shape group draws up to 10 paths and 8 fills or strokes, and the rest are not drawn. A gradient takes up to 16 color stops and 16 opacity stops. More is reported in problems. |
| Text | A text layer draws at most 64 lines and its first 16,383 characters (details). |
| Text fitting | Up to 1,000 rules in text_fitting.json, one per text layer; layer names 1 to 200 characters. minSize and maxSize at most 10,000 pixels, and a fitted layer's s and lh at most 10,000 pixels. At most 64 lines and 16,383 characters are measured. The engine fits at most 15 text layers per composition to a layer region, counting inline textFit directives (text fitting). |
Files and versions
| Limit | Value |
|---|---|
| Files per version | 5,000 |
| Project size | Set by your plan: the total size of the files in one version. An upload, edit or ZIP import that would make a version larger, or a copy or variation from a version larger than that and than every head of its project, returns 403 project_too_large. A ZIP is checked when it is imported; its upload is refused only when the ZIP is too large to import over any head of the workspace. |
| Variations | 100 per project, main included. Another returns 409 variation_limit. |
| Names | Projects: 1 to 200 characters. Variations: 1 to 100 characters. The optional name of a version, a render or a download archive: up to 200 characters. File paths: 1 to 512 characters. An upload's fileName: up to 255 characters. |
| Request body | 64 MB for an edit, a render, a batch render or an MCP request. A larger one gets 413 too_large. Files sent inline as base64 fit about 45 MB of binary data. |
| JSON files | 50 MB, including data.json |
| Images | 128 MB, at most 8192 pixels per side and 64 megapixels. An image asset in data.json is declared at most 4096 pixels per side, and renders at its declared size. A file of another size is scaled to it. An image asset without a declared size renders at its file size, scaled to fit 4096. |
| Animated GIF and WebP | 512 frames, up to 3,600 seconds and 120 fps, and 64 megapixels across all frames (width × height × frames) |
| Video files | 4 GB, at most 8192 pixels per side, up to 3,600 seconds. A video asset in data.json is declared at most 4096 pixels per side. A larger file is scaled down to fit 4096. |
| Audio files | 64 MB, up to 3,600 seconds, 1 to 8 channels |
| 3D models | 100 MB per .glb, 8 MB per .gltf (what a model can hold) |
| Fonts | 64 MB per file |
Reading a file as text (the read_file MCP tool) |
JSON files up to 5 MB |
| Render input | 8 GB: the total size of the version's files |
| Render workspace | 40 GB per render. That counts its files as the engine gets them, its images scaled to their declared sizes, and what it renders. A video with transparency or an odd width or height takes many times its file's size. What it renders counts up to 4 bytes a pixel for each frame, or a video at its top bitrate. A render whose output alone is past the limit is refused with version_not_renderable before it is charged. One that is past it only once its files count fails with version_not_renderable. |
Uploads and ZIP imports
| Limit | Value |
|---|---|
| Upload size | 8 GB per file or ZIP. A file other than a ZIP can be no larger than your plan's project size. A ZIP is checked when it is imported; its upload is refused only when the ZIP is too large to import over any head of your workspace. Above 100 MB, upload in 64 MB parts (multipart). |
| Upload lifetime | Single use. 1 hour for a single PUT, and 24 hours for a multipart upload, counted from creation whether or not the upload was completed. Part URLs last 1 hour and can be issued again. A queued ZIP import or render that names the upload extends its life to a day from then, but never past 47 hours after creation. So neither can be queued with an upload created more than 46 hours ago. |
| Uploads per workspace | 100 unexpired, counting completed ones nothing has used yet. Another returns 409 upload_limit. An upload stops counting once an edit or a successful ZIP import uses it, a render's own version is made with it, you delete it, or it expires. So a queued import or render, a failed import, or a render that stopped before its version was made, leaves its upload counting. |
| ZIP contents | 5,000 files, 8 GB uncompressed and no more than your plan's project size unless it replaces a head at least as large (the import checks this), at most 200:1 compression. The ZIP's file list holds at most 20,000 entries (folders and skipped system files included) and 8 MB. |
| ZIP imports in progress | 10 waiting or running per workspace (another returns 409 import_limit), one importing at a time. A finished import's status is kept 7 days. After that, getting its status returns 404. |
Renders
| Limit | Value |
|---|---|
| Video length and size | Set by your plan |
| Render time | 30 minutes per render |
| Render queue | No set number of renders at once. While renders wait, each workspace gets a share of render capacity set by its plan, and on a plan with a priority render queue its renders start ahead (pricing). Every queued render runs. |
| Storage | Set by your plan: your project files, your succeeded renders' outputs, uploads not yet completed (at the size they were created with), and version exports and download archives until they expire, together. While a render is queued or running it holds 1 MiB for each render second it was charged, since its video's size is known only at the end. At the limit, new uploads, versions that add files and new renders return 403 storage_limit. Delete projects or renders you no longer need to free space. |
| Downloads | A monthly fair-use allowance set by your plan. downloadBytes in GET /v1/usage is this calendar month's total, counted a few times an hour. |
| Frames per frame render | 1,000. frames.end is at most the composition's frame count. |
| Batch renders | 1,000 renders per batch, all of one version |
| Bulk status and cancel | 1,000 render ids per call |
| Download archive | 1,000 succeeded videos, 8 GB in total, kept 24 hours. 10 waiting or building per workspace (another returns 409 archive_limit), one building at a time. The 8 GB is checked while the archive is built, so an archive past it ends failed: split it into smaller ones. |
| Version export | 8 GB, kept 24 hours. 10 waiting or building per workspace (another returns 409 export_limit), one building at a time. A larger version is refused with 400 invalid_request: download its files one by one. |
| Replacements | 200 per edit or render, and 128 MB per replacement image. A fitted image's path is at most 512 characters, so keep its folder to 489 characters or fewer (replacement details). |
| HTML5 ad | Under 5 MB in total. For The Trade Desk the video is under 1.1 MB with interaction=video, or at most 2.2 MB with tapToContinue (HTML5 ads). |
API and workspace
| Limit | Value |
|---|---|
| Rate limit | Requests per minute per workspace, set by your plan (pricing), or a limit Blitframe has agreed with you: limits.requestsPerMinute in GET /v1/usage. Shared by all the workspace's API keys and MCP connections; using the console does not count. It refills evenly: a burst up to the limit, then the rest spread over the minute. Over it, you get 429 rate_limited with a Retry-After header. |
| Requests without a valid key or token | 6,000 per minute per IP address (per /64 network for IPv6) |
| Share pages | 60 requests per minute per IP address, all share pages together |
Prefer: wait |
50 seconds per request. Over MCP, waitSeconds on get_render, get_upload, get_zip_import, get_download_archive and get_version_export has the same limit. |
Idempotency-Key |
1 to 200 characters, and a key replays for 24 hours. A render's or batch's key also has no / and does not start with share: (retrying safely). |
| List pages | 1,000 items per page |
| Download links | 1 hour for render outputs, download archives and version exports. Get the render, archive or export again for a fresh link. 15 minutes for single files. |
| API keys | 25 active per workspace |
| Webhook endpoints | 10 per workspace, added or repointed at most 20 times an hour. Deliveries stay in the log 30 days. |
| Share links | 50 per project, on a plan that includes them |
| Problem reports | 10 per hour per workspace, 2,000 characters each |
| Workspaces per person | 50. A person in 50 workspaces must leave one before joining or creating another. |
| Invitations | Valid 7 days, single use. 50 unexpired invitations per workspace. |
| Email address changes | 3 requests a day per person |
| Sign-in lockout | 10 failed sign-in attempts lock password sign-in for 15 minutes |
Plan limits
Your plan sets your workspace's limits and features below the hard limits above. GET /v1/usage shows them under limits. Every member sees them in Console → This workspace → Plan & billing:
"limits": { "maxDurationSeconds": 30, "maxLongEdge": 1280, "maxShortEdge": 720, "watermark": true, "requestsPerMinute": 300, "custom": false, "customUntil": null,
"maxStorageBytes": 1000000000, "maxProjectBytes": 100000000, "monthlyDownloadBytes": 5000000000, "shareLinks": false, "advancedEncoding": false, "priorityRendering": false }
| Field | Meaning |
|---|---|
maxDurationSeconds |
The longest MP4 or HLS video, in seconds. Frame renders have no duration limit. null: up to 3,600 seconds, the longest composition Blitframe accepts. |
maxLongEdge, maxShortEdge |
The largest composition, in pixels on its longest and shortest side, so a 1280×720 limit also allows 720×1280. Applies to every format. null: up to 16384 pixels per side. |
watermark |
Whether every output (MP4, HLS, frames and poster) carries a small "Made with Blitframe" mark in the bottom-left corner, drawn above the whole composition. |
requestsPerMinute |
API requests per minute for the workspace, shared by all its keys and MCP connections: your plan's, unless Blitframe has agreed a different rate with you. See Rate limit. |
maxStorageBytes |
How much the workspace may store: project files, succeeded renders' outputs, uploads not yet completed, and version exports and download archives not yet expired. null: no limit. storageBytes in the balance is what it stores now. |
maxProjectBytes |
The most the files of one version can total, in bytes (100 MB is 100,000,000). An upload larger than this, or an edit or ZIP import that would make a version larger, returns 403 project_too_large. A ZIP is checked when it is imported; its upload is refused only when the ZIP is too large to import over any head of the workspace. A version made larger before your plan changed may stay that size or shrink, and a render's own version may be larger, since its replacements must still render. Such a version still renders and exports, but a copy or variation can start from it only while a head of its project is at least as large. A copy checks the version its text fitting measures against the same way. A larger plan allows larger projects. null: up to the 8 GB render input. |
monthlyDownloadBytes |
The monthly fair-use allowance for downloads of the workspace's files, or null. It is a guide, not a cut-off: downloads keep working past it, and Blitframe gets in touch about steady use well over it. |
shareLinks |
Whether the workspace can create share links, and whether its links play. |
advancedEncoding |
Whether renders can use the H.265 and AV1 codecs and encoding settings. Without it, videos are H.264 at a quality level. |
priorityRendering |
Whether the workspace's renders start ahead of other plans' while renders wait. |
custom, customUntil |
custom is true when Blitframe has agreed custom limits for your workspace. They replace your plan's for the fields they set. customUntil is when they end, or null if they don't. |
The free trial renders videos up to 30 seconds at up to 1280×720, with the watermark, and holds projects up to 100 MB.
A request for a feature your plan does not include (a share link, a codec other than H.264, encoding settings) fails with 403 plan_feature, and nothing is charged.
A render over a limit fails with 403 plan_limit before anything is charged. The message names the limit and where it comes from: your plan, or your workspace when Blitframe has agreed that limit with you. To fit, make the composition smaller or shorter in data.json. If a plan you can choose in Console → This workspace → Plan & billing allows it, the message says so. Otherwise it says how to reach sales.
Balance
GET /v1/usage shows your render-second balance and plan, with the plan limits:
{
"plan": "Pro",
"renderSecondsRemaining": 31840,
"monthlyRenderSeconds": 43200,
"periodEndsAt": "2026-12-08T00:00:00+00:00",
"trial": false,
"planEnded": false,
"noTrial": false,
"limits": { "maxDurationSeconds": 600, "maxLongEdge": 3840, "maxShortEdge": 2160, "watermark": false, "requestsPerMinute": 4800, "custom": false, "customUntil": null,
"maxStorageBytes": 200000000000, "maxProjectBytes": 2000000000, "monthlyDownloadBytes": 400000000000, "shareLinks": true, "advancedEncoding": true, "priorityRendering": true },
"storageBytes": 18460000000,
"downloadBytes": 42100000000
}
| Field | Meaning |
|---|---|
plan |
The plan's name, or "No plan". |
renderSecondsRemaining |
What you can spend now. |
monthlyRenderSeconds |
The plan's monthly allowance, or 0 without a plan. A plan invoiced by sales grants the seconds for its whole period up front. So the balance can be larger, and it does not refill monthly. |
periodEndsAt |
When the current period ends. |
storageBytes |
What the workspace stores now: project files, succeeded renders' outputs, uploads not yet completed, and version exports and download archives not yet expired. |
downloadBytes |
Bytes of the workspace's files downloaded this calendar month (UTC), counted a few times an hour. |
Three flags say whether the workspace can render without a new plan:
trial |
planEnded |
noTrial |
The workspace |
|---|---|---|---|
false |
false |
false |
is on a plan |
true |
false |
false |
is on its free trial |
true |
true |
false |
had a free trial, which has run out |
false |
true |
false |
had a plan, which has run out |
false |
true |
true |
never had a trial (it is one per person, and limited per company and network), and has no render seconds until a plan starts |
While planEnded is true, renderSecondsRemaining is 0 and renders return 402 insufficient_render_seconds until a plan starts. So do new uploads and edits that add files; you can still read, download, export and delete what the workspace holds.
A workspace on a plan can still be refused. While a payment is disputed with the bank, renders return 402 payment_disputed, even with seconds left. When a failed payment is still unpaid 3 days after the period ended, they return 402 insufficient_render_seconds. The message says which, and what to do.
Free trial
The first workspace you create starts with a free trial: no card, a set amount of render seconds, and a time limit. The console shows both. Trial renders are limited to 30 seconds at up to 1280×720, and carry a small "Made with Blitframe" mark (plan limits). The trial is one per person, and limited per company and network, so a workspace you create later has no render seconds until a plan starts. If your workspace started without a trial because of those limits, the console says so: contact us and we'll start it. Joining someone else's workspace does not use up your trial.
If a workspace's trial ends and it never starts a plan, its projects, files and renders are deleted 60 days after the trial ends. The workspace's owners, admins and billing members get an email 30 days and 7 days before that. Starting a plan keeps everything; the workspace, its members and its API keys stay either way.
Plans
To keep rendering after the trial, choose a plan in Console → This workspace → Plan & billing. The page starts a plan sold by card, and gives the address to write to for one that is invoiced. Pricing lists every plan with its price, allowance and limits. A plan replaces the trial's remaining seconds with its own allowance. Your projects are kept either way. A larger plan's limits and seconds apply once its payment goes through; a smaller plan's limits apply as soon as you switch.
If a paid plan ends and the workspace doesn't start another, its projects, files and renders are deleted 90 days after the plan ends. The workspace's owners, admins and billing members get an email 30 days and 7 days before that. Starting a plan keeps everything; the workspace, its members and its API keys stay either way.
Low-balance warning
When fewer than 10% of the period's render seconds are left, Blitframe warns you three ways:
- The workspace's owners, admins and billing members get an email.
- Your webhooks get a
balance.lowevent. - The console's Overview shows what is left.
The warning comes once a period. It comes again after render seconds are added, the allowance changes or you change the threshold. Change the threshold or turn the warning off in Console → This workspace → Plan & billing.
Three days before a trial or plan ends, the same people get an email too, since the remaining render seconds end with it.
Data retention
- Projects, versions and render outputs are kept until you delete them. A render that fails or is cancelled keeps no output. The exception is a workspace without a plan: its projects, files and renders are deleted 60 days after its free trial ends without a plan, or 90 days after its paid plan ends without a new one, after two email warnings.
- Download archives and version exports are deleted 24 hours after you request them. An archive then returns
404. It is kept that long even when a render it contains, or that render's project, was deleted sooner. Deleting a project deletes its versions' exports with it. Requesting an export again afterwards builds a new one. - A ZIP import's status is deleted 7 days after the import finished. The version or project it made is kept.
- Webhook deliveries are kept in the log for 30 days.
- Owners can delete the workspace in Console → This workspace → Members & settings, by typing its name. That cancels its subscription and removes its projects, files, renders, API keys, webhooks and sessions for everyone in it. Stored files are erased within a few hours, and no copy of a deleted file is kept for more than 7 days. IP addresses and event details in the workspace's audit records are erased then. The rest of those records is kept for 400 days, then deleted.