Limits & Usage
What are limits in ReelBot?
Limits define how much of the system you can use within a given period.
They exist to:
- keep the platform fair
- align cost with usage
- ensure predictable performance
Limits are transparent, enforced gracefully, and always visible.
Where to view usage
You can see your usage in multiple places:
- Dashboard (high-level overview)
- Subscription & Usage page (full breakdown)
- contextual indicators inside workflows
- live counters in the Settings Sidebar
ReelBot never hides consumption.
Types of limits
ReelBot enforces several independent limits.
Each limit operates separately.
AI credits
AI credits are consumed by AI-powered actions.
Examples include:
- topic generation
- script generation
- voiceover generation
- image animation
- AI-powered regeneration
How AI credits work
- credits reset daily
- usage is tracked in real time
- an animation appears when credits are consumed
- credits are not shared across days
If you run out of AI credits:
- AI actions are temporarily blocked
- non-AI actions remain available
- access resumes automatically after reset
Video generation limits
Video generation limits control how many final videos you can generate.
Key points:
- limits are typically monthly
- each completed generation counts once
- regeneration creates a new project and counts again
- failed generations do not consume quota
Drafts and previews do not count.
Publishing (post) limits
Post limits define how many posts you can publish per period.
Important details:
- limits are monthly
- drafts do not consume quota
- quota is consumed only when publishing succeeds
- publishing failures do not consume quota
You can prepare unlimited drafts even when out of quota.
Connected channel limits
Channel limits define how many social accounts you can connect.
Notes:
- enforced at connection time
- vary by plan
- removing a channel frees a slot immediately
Channels are required for publishing but do not consume quota on their own.
Storage limits
Storage limits define how much media you can store.
Storage is consumed by:
- uploaded video assets
- uploaded music assets
- AI-generated animated videos
Storage is not consumed by:
- shared assets
- generated projects
- drafts
- templates
Deleting assets frees storage instantly.
Usage behavior at limits
When you hit a limit:
- the affected action is blocked
- existing content remains accessible
- nothing is deleted automatically
- clear messaging explains what happened
ReelBot never fails silently.
Usage resets
Different limits reset on different schedules:
| Limit Type | Reset Frequency |
|---|---|
| AI credits | Daily |
| Video generation | Monthly |
| Publishing | Monthly |
| Storage | Does not reset |
| Channels | Static (plan-based) |
Reset timing is shown in-app where relevant.
Upgrading to remove limits
If you hit a limit frequently:
- upgrading your plan takes effect immediately
- higher limits unlock instantly
- no work is lost
Upgrades are the fastest way to remove friction.
Downgrading and limits
When downgrading:
- existing usage is preserved
- limits apply at the next billing cycle
- actions may be restricted if usage exceeds new limits
Nothing is deleted automatically.
Common misconceptions
- Running out of AI credits does not block publishing
- Running out of video generations does not block drafts
- Storage does not reset monthly
- Deleting projects does not free storage
Each limit applies only to its scope.
Best practices for managing usage
For smooth workflows:
- monitor usage before batching
- use drafts when near limits
- reuse assets instead of uploading duplicates
- upgrade when limits become friction
Limits should guide scale — not block progress.
The CreatorOps perspective
In CreatorOps, limits define throughput boundaries.
By making limits visible and predictable:
- planning becomes easier
- workflows stay intentional
- scaling decisions become obvious
ReelBot treats limits as signals — not punishments.
Related topics
- Plans Overview
- Manage Your Plan
- AI Credits
- Storage Limits
Know your limits — then design around them.