Skip to main content
Common questions about credits, billing cycles, and what your plan includes.
Unused credits expire when your billing cycle resets. Credits are not carried over to the next month — your balance refreshes to your plan’s monthly allowance on your renewal date.
If Extensy encounters a server-side error and no ZIP is produced, your credit is automatically returned to your balance. Credits are only deducted for successful, downloadable outputs. You will never be charged for a generation that fails on our end.
No. Credits are tied to individual accounts and cannot be transferred. Make sure you’re logged into the correct account before generating. For team-based credit sharing, contact teams@extensy.dev to ask about enterprise options.
When you upgrade mid-month, any remaining credits from your current plan are added to your new plan’s balance. You won’t lose credits you’ve already earned in the current cycle.
Commercial rights mean you can sell, distribute, or monetize the extensions you build with Extensy. The Free plan is limited to personal use — you cannot publish or sell extensions built on it. Pro and Max plans include full commercial rights for all generated extensions.
Not currently. The best way to increase your monthly credit allowance is to upgrade to a higher plan. Pay-as-you-go credit packs are being evaluated for a future release.
If you downgrade, your remaining credits from your active Pro or Max plan stay available until the end of your current billing period. After that, your balance resets to the Free plan limit of 5 credits per month.
No. Unused credits at the end of a billing cycle are not refunded. We recommend planning your generation work to use your monthly allowance before it resets.
Yes. Every account receives 5 free credits on a monthly basis, starting from the day you sign up. The reset date is the same day each month as your original signup date.
If you’re building as a team, consider using a single Pro account for the lead developer to handle core generation and iteration, then distribute the resulting ZIP for manual refinement by other developers.